User forums > General (but related to Code::Blocks)
Linking Errors with 'Hello World' program using wxWidgets - HELP! :)
sethjackson:
--- Quote from: Defender on May 19, 2006, 05:10:04 pm ---
--- Quote from: sethjackson on May 19, 2006, 01:40:52 pm ---
--- Quote from: Defender on May 19, 2006, 10:17:50 am ---Yes, if you build wxWidgets correctly, there should be a gcc_dll path with a large DLL called wxmsw26(...).dll and a library called libwxmsw26(u).lib inside.
Good luck :)
--- End quote ---
It really depends on if you build wx with SHARED=1 or not.... SHARED=1 builds a DLL, the default is SHARED=0 wich builds a static lib......
--- End quote ---
I know, but I didn't want to make it so complicated for him :lol:
Ok, Rytz: look for a gcc_lib and a gcc_dll directory, if you can find neither of them, you should build wxW first. 8)
--- End quote ---
Oh. :lol:
Rytz:
Now that you mention the static vs. shared, I think I did the build as static (no DLL's) because I didn't want to rely on DLL's for anything. I'll rebuild wxWidgets tonight.
Also, since I have a thread open, if I use the install package for CodeBlocks instead of compiling my own version, am I at a huge loss? Am I at a huge disadvantage for not compiling my own version? Thanks.
georgie porgie:
No, I wouldn't compile codeblocks unless you plan on doing some development on it. And if and when you do want to do some development on it, i'd worry about compiling it at that time.
thomas:
--- Quote ---Also, since I have a thread open, if I use the install package for CodeBlocks instead of compiling my own version, am I at a huge loss? Am I at a huge disadvantage for not compiling my own version? Thanks.
--- End quote ---
Compiling your own is a little bit of a leap off the Lion's head (was that what they called it in Indiana Jones...?) :)
However, it is nowhere near complicated once you have compiled a monolithic wxWidgets (this is about the hardest part of it).
The disadvantages of building your own are that it is scary if you have never done it (although it is more or less pressing one button ;)), and that it takes 3-4 minutes to finish.
The advantages are (besides that it's cool) that you can update at any time, so you don't have to wait until the next nightly build comes out. Also, you can compile using your own favourite compiler flags (for example, I don't know whether or not Lieven builds his nightlies with the crash handler enabled) and if you have subversion on your PC, you'll get accurate revision times in addition to the revision number.
Also, you can apply a patch from the patch tracker if there is an additional feature that is not in the main codebase yet, and you can make your own modifications if you deem them necessary. The nice thing about it is that as long as there are no conflicts, your changes made to the source tree persist when you update to another revision.
sethjackson:
--- Quote from: thomas on May 19, 2006, 09:52:31 pm ---.....
and if you have subversion on your PC, you'll get accurate revision times in addition to the revision number.
--- End quote ---
The revision time does not show up in the start here page "()" (assuming that is where the time is supposed to go). I get empty parenthesis. Check out the newest nightly to see what I mean.....
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version