Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
QtWorkbench plugin
yop:
I 'm sorry but I can't reproduce these problems. I started off with a new project and my all time favorite victim (the Qt examples) and I selected a "Debug" project then switched to Release from Qt Project options and got a Release build. Then vice versa and it worked again.
Then I added another target and it also worked as expected.
Then I started removing Makefiles (all of them, some of them whatever I could think of) and only the appropriate Makefiles were generated.
I did find a problem in the naming of the output caused because in the .pro I use a += operator for the output but this is fixed in the upcoming release.
I used rev 4263 build of Code::Blocks and QtWorkbench 0.5.0
AnTeevY:
Okay, sorry.
I've just tried a lot an finally found out my fault... I changed the "Make" Commands for the project itself but of course they got overwritten by those of the build target, which I didn't change. That's why the compiler did not find the makefile, so I changed it in the dialog where I selected "This is a custom Makefile". I think this caused all those strange bugs. Sorry again.
But one more question: is it possible to build both release and debug at once? Ok, in the Qt Project Options you can choose them both, but of course this does not work, because in both the makefile.targetname.release and makefile.targetname.debug it says:
TARGET = targetname.exe
DESTDIR_TARGET = bin\targetname\targetname.exe
If I create a empty project with Release and Debug targets, then run "qmake -project" and "qmake projectname", in C::B I can choose between both targets and when compiling the exe's are created in Debug\ resp. Release\ folders. Is this possible with the plugin? I think, you need 2 build targets, but then the plugin creates two project files, and then there are 6 makefiles... is there an easier way?
yop:
Don't apologize, I already mentioned that it's quite difficult to remember to make all those little tweakings (I wonder if such a word exists) here and there to prepare your project and targets. When I release 0.5.1 (it's necessary to fix this bug with the operators in the .pro files) I will prepare wizards for project and target generation so it's (hopefully) trivial to prepare them.
As for your question no there isn't an easier way or at least I can't think of something, except if C::B itself has some kind of magic under the hood (which frankly happens quite often).
Mayler:
I cannot compile even the TexMaker... I made exactly what the wiki is saying... What's Wrong?
My error in my project ( equal the texmaker )
g++: Raiox.Debug: No such file or directory
mingw32-make.exe[1]: Leaving directory `C:/Documents and Settings/Mayler/Desktop/rx'
mingw32-make.exe[1]: *** [bin\RaioX.exe] Error 1
mingw32-make.exe: *** [debug] Error 2
Process terminated with status 2 (1 minutes, 4 seconds)
Using gcc 3.4.5, Qt 4.3, CB 4285 and QtWorkbench 0.5.0
yop:
What is "Raiox" ? Have you setup a target named like that?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version