User forums > Using Code::Blocks
A little step by step tutorial, please [SOLVED]
thomas:
--- Quote ---wxSmith project wizard works for me out of box. It's just a matter of proper wxWidets compilation.
--- End quote ---
Certainly does. In fact (apart from the one-dialog-per-file bug), wxSmith works a lot better than a wxWidgets design tool that cost 129 Euros per single-user license :)
--- Quote from: byo on March 24, 2006, 11:56:46 am ---We can configure libraries using global variables but there's no standard saying how global variable should describe any library (or maybe I missed something).
--- End quote ---
http://wiki.codeblocks.org/index.php?title=Recommended_global_variables
--- Quote from: byo on March 24, 2006, 11:56:46 am ---My proposition is to extend functionality of global variables...
--- End quote ---
This is in work :)
takeshimiya:
--- Quote from: byo on March 24, 2006, 11:56:46 am ---Project templates won't outdate too often and C::B will get easy to use library managment system. Such solution may also remove incompatibilities between windows / linux projects.
--- End quote ---
I've been thinking how to resolve that, and there are lot's of ways. I'm working on it. :)
nmambre:
Hi guys, first 2 things:
1: thanks for all the info, still have to read and try the stuff out, but the number of answers is overwhelming
2: I took out one of the "please" out of the topic... was a typo... looks too much as if I was "whining" :oops:
Now the problem at hand:
* wxdevcpp comes with "everything" (GUI designer, wxWidgets, Mingw and a little tutorial), just download single package, install and develop. That's why I kind of expected the same of C::B
* I read wxSmith tutorial, but didn't read (completely) the part of compiling wxWidgets, because I (wrongfully) thought it was just needed to compile C::B itself
So I will read both tutorials, this time completely, and see if that solve my problem. If I succeed or fail, you will hear from me.
Have you considered providing a download option with everything included? Or do you prefer to keep C::B separated from wxWidgets all the time? just a thought, would be easier on newbies and people that just wants to tryout.
Thanks again,
Nelson
byo:
--- Quote from: thomas on March 24, 2006, 12:22:00 pm ---
--- Quote ---wxSmith project wizard works for me out of box. It's just a matter of proper wxWidets compilation.
--- End quote ---
Certainly does. In fact (apart from the one-dialog-per-file bug), wxSmith works a lot better than a wxWidgets design tool that cost 129 Euros per single-user license :)
--- End quote ---
And it will work much better :) And that one-dialog-per-file bug shouldn't be hard to eliminate. Some Feature request would be nice since I can forget about it ;)
--- Quote ---
--- Quote from: byo on March 24, 2006, 11:56:46 am ---My proposition is to extend functionality of global variables...
--- End quote ---
This is in work :)
--- End quote ---
Can't wait till it's done :)
To nmambre: I hope c::b will have everything needed in one instalation package. But first we have to create some solid-stable final 1.0 version :) Just a matter of time ;)
thomas:
--- Quote ---Have you considered providing...
--- End quote ---
Bundling everything looks like a good idea at first, but on the long run, it often causes more problems than it is worth. The big advantage of shipping IDE, compiler, and toolkits separately (even if it is more work to set up) is that you can for example upgrade from gcc 3.4.2 to 3.4.5 simply by deleting the whole MinGW folder and unpacking everything from the MinGW website. You don't touch the IDE, and everything works as before. The same is true for wxWidgets.
When Code::Blocks started out, 2.4.2 was the most recent version. At some point in the middle, we had to develop for 2.4.2 and 2.6.1(2.6.1patch, 2.6.2) in parallel.
Now, how do you develop with two different versions of wx? This is a major pain if everything is bundled and all your includes are in C:\codeblocks\include. It will never work. On the other hand, if you install them separately to separate locations, then you just change one project variable... :)
-- So what are you to do now? --
You have wxWidgets on your PC, so far so good. However, the compiler and the linker need to know where you keep your stuff.
Our templates use a global user variable for that purpose. The advantage is that you only need to set it correctly exactly once.
The first thing you need to know is: Where are your headers and libraries?
If wxdevcpp comes with wx bundled and you have that on your PC, most likely the headers will be in C:\wxdevcpp\include\wx and the libs will be in C:\wxdevcpp\lib or a similar place. Don't worry about that "wx" subfolder (all sources use #include <wx/somewxheader.h>, so that is OK -- what matters is only where that folder is found).
If you set the wx global user variable to C:\wxdevcpp, it should work (if the folder layout looks like that).
However, it can happen that your wxdevcpp installation has a different layout (for example, it could put the wx includes into a folder like C:\wxdevcpp\contrib\wx26 or anything. I don't know anything about that, but that will be easy enough for you to find out :)
In any case, usually there is a folder include and a folder lib somewhere, and they are usually together in the same parent directory. Even if they are in different locations, it does not matter, because you can define wx.include and wx.lib separately if needed (see documentation).
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version