Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
CB menu system confusion
Pecan:
--- Quote from: killerbot on January 20, 2007, 06:01:16 pm ---they come from here : http://forums.codeblocks.org/index.php?topic=4809.msg38778#msg38778
--- End quote ---
Oh. So a diff file is not necessary.
How do we plan on handling this situation for SVN users?
I'm re-modifying the wxWidgets263 source to get this all to work.
EDIT: 12:59 PM
It works.
I copied the modfied menu.cpp and ownerdw.cpp built with:
--- Quote from: stahta01 on January 17, 2007, 04:46:30 pm ---I have uploaded my back port of how this problem was fixed in CVS head. The fix is patch 1637808 which updates the file menu.cpp. I would apply the patch 1637804 before doing this patch because menu uses code in the file ownerdrw.cpp.
Tim S
[ 1637808 ] MSW: menu.cpp backport to 2.6_BRANCH from cvs head
http://sourceforge.net/tracker/index.php?func=detail&aid=1637808&group_id=9863&atid=309863
[ 1637804 ] MSW: ownerdrw.cpp backport to 2.6_BRANCH from cvs head
http://sourceforge.net/tracker/index.php?func=detail&aid=1637804&group_id=9863&atid=309863
--- End quote ---
to wxWidget263, re-built wxmsw26u_gcc_custom.dll, then re-built Codeblocks and contribs against it.
With the keybinder fixes (applied svn 3443) the icons are aligned and the "skipping mnemonic" bugs have disappeared.
Still... these sources have to be applied via CB svn somehow.
thanks
killerbot:
no , they are wx sources, not CB sources. Windows people can download are special dll. Linux people need to do it themselves, but they didn't have those problems in the first place (the menu alignment and disabling of icons), so they don't need to do anything.
We don't want people using Cb to build wx themselves.
You don't even have to rebuild CB if you want to use the new dll, since no headers have changed.
Pecan:
--- Quote from: killerbot on January 20, 2007, 10:44:30 pm ---no , they are wx sources, not CB sources. Windows people can download are special dll. Linux people need to do it themselves, but they didn't have those problems in the first place (the menu alignment and disabling of icons), so they don't need to do anything.
We don't want people using Cb to build wx themselves.
You don't even have to rebuild CB if you want to use the new dll, since no headers have changed.
--- End quote ---
Lets say we tell a new user that it's easy to build from SVN. S/he does so and ends up with the same menu problems we've just been through because s/he compiled using the usual wxWidgets.
Where can we tell him/her where to get these patches for wxWidgets?
Shall we say to just search the forum?
Or will we have a common place for the patches, and an explanation of where to apply them.
There are already other patches (Scintilla for example) that we apply to external source. How are they maintained. How does a new svn user handle all this?
Lets say a smart new user wants to debug CB using wxWidgets debug mode. Where would s/he get the patches to make the wxWidgets source mirror the nightly wxLib?
stahta01:
--- Quote from: Pecan on January 21, 2007, 02:03:07 am ---
Lets say a smart new user wants to debug CB using wxWidgets debug mode. Where would s/he get the patches to make the wxWidgets source mirror the nightly wxLib?
--- End quote ---
I am working on a Wiki page for this
http://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.6.3_to_develop_Code::Blocks_%28MSW%29
I still got a long way to go, but I plan to show how to apply patches to wxWidgets source.
Tim S
killerbot:
Pecan, Tim,
good idea.
--- Quote ---There are already other patches (Scintilla for example) that we apply to external source. How are they maintained. How does a new svn user handle all this?
--- End quote ---
The difference here is that those sources are in our svn repo and are built as part of CB when you build CB.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version