Version: 3.0.0 (using KDE KDE 3.0.3) Installed from: RedHat RPMs OS: Linux Hello, I can't find any way to specific 'Build Configurations' or 'Build Targets' for Custom Applications. I noticed under a project managed by KDevelop you can specify 'Build Configurations' under the Project menu, and under The Build Menu for our project imported with "Custom Makefiles" there is a blank "Build Targets" sub-menu. (This is probably because our targets (clean, etc) are all listed in a seperate file imported into the Makefile. Anyway, what I would like to be able to do is specify various parameters to the make command, and vary they depending on "Build Configurations". For example, to build our project in debug mode, we run this command: make BUILD_TYPE=debug and to build in release, we do: make BUILD_TYPE=release I just want a way to create 'configurations' for custom makefile projects, and then to specify either the entire command on a per configuration basis, or just the parameters to the program (make or ant). -Thanks.
You do have configuration options in Gideon under: Project > Project Options ... > Configuration Options Aren't these good enough?
I do not see 'Configuration options' under Project->Project Options. On the left hand column, I see 'General, Plugins', Project Documentaiton, New File Wizard, C++ Specific, Run Options, Build Options, Class View, File Groups, Debugger, Doxygen, and CVS. Am I doing something wrong?
It's probably because you use "custom project" :( It works fine with "Auto project". Anyway you should test KDevelop3.0 CVS it probably works fine there. I can not test rigth now because I'm on a windows box :(
>> It works fine with "Auto project". Did you mean "Automake project"? In alpha 6 there still does not seem to be support for different build configurations when using an imported project with custom makefiles.
This wish is granted. Patch sent by Hendrik Kueck. Thanks Hendrik!
In which version of KDevelop will this patch appear? I cannot find it resolved in some current version. (Using FC2 with KDevelop 3.0.3)
Bas, it was resolved in KDevelop 3.0.0 so it should work for you.