User forums > General (but related to Code::Blocks)
building wxWidget on Kubuntu
devguy:
--- Quote from: oBFusCATed on April 17, 2011, 07:55:31 pm ---Yes, you can create "Custom makefile projects".
Search the forum, wiki and docs for details...
--- End quote ---
i googled, 'site:forums.codeblocks.org importing makefile'
i am not finding a solution? i am seeing posts that claim it is not possible??
i am talking about importing a makefile project, not creating one? netbeans does this effortlessly, no settings to tweaks, or going into project settings and adding variables, etc.
this is pretty much what I am expecting from C::B, it would be nice to if there is a simple way to set up a makefile project so i can build and step through the code
devguy:
--- Quote ---Hi, you may find http://arnholm.org/cpde/cpde_20101120.pdf to be of some help.
--- End quote ---
Thanks for the document, I'll have to read through it, as well as google on wx-config.
--- Quote ---If you have installed a special version of wxWidgets, in my experience you need to take special care in using the correct "wx-config" when compiling and linking, or else you can get the wrong public one. I have wxwidgets installed under /usr/local, and the way I have been able to make 100% sure I am using the right one, is with the follwing compiler setting (notice the backticks)
--- Code: ---´/usr/local/bin/wx-config --version=2.8 --toolkit=gtk2 --cxxflags´
--- End code ---
and in linker options
--- Code: ---´/usr/local/bin/wx-config --version=2.8 --toolkit=gtk2 --static=yes --libs´
--- End code ---
--- End quote ---
As for the placement of the wx-config command, where would I put it in C::B ? Is that outlined in the document, thanks!
Jenna:
* Create an empty project with the wizard,
* right click the project in the management pane,
* chose "Properties",
* check "This is a custom makefile",
* adjust the makefiles-name and probably its path (if needed, default path is the projects bas path),
* close the "Properties" dialog,
* right click the project in the management pane,
* chose "Build options"
* open the "Make commands" tab (rightmost),
* fix the make commands (most likely needed),
* close the dialog
* right click the project in the management pane,
* click "Add files" or "Add files recursively",
* add the files you want to your project,
* save your project (via menu, context menu or ALT+SHIFT+S)This works flawlessly for the wxWidgets samples on linux, on windows, I sometimes (always?, do not remember exactly, I use linux almost every time) have to add the options used to build wxWidgets to the makefile-call.
Jenna:
--- Quote from: devguy on April 17, 2011, 08:30:15 pm ---As for the placement of the wx-config command, where would I put it in C::B ? Is that outlined in the document, thanks!
--- End quote ---
If you use existing makefiles, you don't use C::B's build-system (obviously) and the call to wx-config has to be inside the makefile, you might need to fix it manually if you are forced to use special wx-config versions, or link the default wx-config to the one you want to use (either manually or with "update-alternatives").
For other cases, it's the easiest way to create a wizard-based wxWidgets-project and look how it is done there.
devguy:
Jens, it's seems a lot involved than it needs to be vs NB IDE. For someone new to the Linux open source world, there is just too much to learn just to get going with a simple project imho!
Jens for someone like yourself it might not seem like a big deal to go through the steps you outlined, but where I stand now, it just too much tinkering which I am trying to make sense of.
CodeBlocks needs a painless makefile project importer, I think I am going to stick with NB where I need to import a project using only a makefile. C::B could learn something from NB!
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version