Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
wxSmith development
tiwag:
--- Quote from: rickg22 ---Dunno, we need some brave warrior who dares compile C::B CVS with wx2.6. Thou shalt slay the red bug dragon! :P
--- End quote ---
hi rick,
do you want a compiled version of C::B using wx2.6 ?
i can upload it somewhere for you if you want.
but you also can easily build it yourself, following the readme-wx2.6.0,
i've done it and found no serious problems.
i'm using several installed versions of wx in parallel, and should finally update the wiki-section regarding this, as you requested from me.
sorry, but i didn't find time till now, but i promise it for the week-end.
-tiwag
[addendum]
i've just read:
--- Code: ---wxWidgets v2.6.1 has been released
--- End code ---
This release is a major bug-fix release. Many bugs in almost every port have been fixed, including compilation and GUI drawing problems.[/list:u]http://www.solidsteel.nl/users/wxwidgets/viewtopic.php?p=10367#10367
rickg22:
YAY! :D 'Bout time! Well the problem is that my mingw directory tree has the wx2.4 files... i have to see how to adapt it to compile with wx2.6.1. Maybe this weekend i'll have time to test (ugh, more hours of meddling with the settings and compiling).
tiwag:
--- Quote from: rickg22 ---..Well the problem is that my mingw directory tree has the wx2.4 files...
--- End quote ---
i know that troubles, had the same in the past :( .
That was the reason, why i figured out how to avoid this. :D
i will prepare the description how you can easy have multiple wxwidgets-versions and/or several different setups in parallel 8)
if you want to have a quick solution, here
Build CodeBlocks wxmsw261
you can download the wxwidgets-build-batchfile
and an updated codeblocks project file for wxmsw 2.6.1.
for this config i've used : set WXDIR=D:\wx261
steps:
download wxmsw-2.6.1 and unzip it to WXDIR
copy the batchfile wxwidgets-build-batchfile to WXDIR
(update the pathes if necessary)
run the wxwidgets-build-batchfile
check out a clean version of codeblocks from cvs
copy the codeblocks project file
(update the include / lib pathes if necessary)
open the project and build codeblocks
run the update.bat
copy these files to your codeblocks "output" directory
"D:\wx261\lib\gcc_dll\wxmsw26_gcc_cb.dll"
"D:\wx261\lib\gcc_dll\wxmsw26_stc_gcc_cb.dll"
now you can run "output\codeblocks.exe"[/list:u]
--- Quote from: [edit] ---for the unlikely case, that the above is too much for you,
you can download my binary version too
--- Quote ---sorry, removed from web
--- End quote ---
--- End quote ---
enjoy
-tiwag
cyberkoa:
--- Quote from: byo ---
Hmm, Waiting for Your job :). But must say that some parts of code are not finished yet (f.ex. events sytem) and update of this code will be needed soon :).
Thx for Your interesting. Hmm, One of my idedas was to create RAD tyool which could be easily extended with new sets of widgets :).
--- End quote ---
It is my pleasure, in fact I learned a lot from reading your code :D . I have to admit that I am not able to write it from scratch but I try my best to add in some codes with my weak C++.
--- Quote from: byo ---
http://www.geocities.com/jmsalli/propertygrid/ - it has already been done i think :). But need to wait for compatibility with wx 2.6. Hmm, maybe it has already been done, haven't read forum for some time :oops:
--- End quote ---
Unfortunately, I tried to compile in wx-2.4.2 but failed. I did go in further to check the problem.
I already almost understand how to add in new code to support new widget , I shall start with
1. XML load
2. XML save
Still planning on writing the code for keeping the selection list for combobox. Hope that I can at least load a combo box :oops:
DreadNot:
I have also compiled with wx2.6 (actually, the only compile). I have a separate project dir for wx outside mingw so that I can switch (if needed, as necessary). The compile is much like tiwag describes. Updating to 2.6.1 now...
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version