Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
QtWorkbench plugin
yop:
Hi, thanks for your support and interest.
Providing a template for creating QtWorkbench projects is on my TODO list (actually it is ready) but unfortunately:
* There is no way to add it to the list of project/target templates in C::B except manually changing a file
* The behavior of C::B when creating the new project using the template was a bit strange (it was signaling more than one times that the new project was created) and it messed up a bit the way the project was setupAnyway this is something that I have on my mind so you 'll eventually get it :-)
The Qt4 project template that is bundled with C::B is insufficient for creating a full blown Qt application and cannot be considered useful. GeeF already mentioned the reasons.
ui_*.h and moc_*.h files have no reason for being included in your project files as they are automatically generated. C::B provides facilities for performing custom compilation steps per file type and include them in your project files in order to participate to the build process. I haven't checked that yet but it seems that this could be another solution for building Qt projects and probably more "native" to the C::B build process. I think that if someone checks it out and proposes things Yiannis will be more than happy to take a look at them. This facility was originally meant for adding support for non C++ files to the build process but it can evolve I guess.
mandrav:
--- Quote from: yop on March 28, 2008, 11:07:54 am ---ui_*.h and moc_*.h files have no reason for being included in your project files as they are automatically generated. C::B provides facilities for performing custom compilation steps per file type and include them in your project files in order to participate to the build process. I haven't checked that yet but it seems that this could be another solution for building Qt projects and probably more "native" to the C::B build process. I think that if someone checks it out and proposes things Yiannis will be more than happy to take a look at them. This facility was originally meant for adding support for non C++ files to the build process but it can evolve I guess.
--- End quote ---
Yes, it will improve. Its current major drawback is that these settings are compiler-global, (i.e. you must manually configure your C::B installation for these) while they should be per-project/target settings.
Omni:
The Code::Blocks project file of the qtWorkbench plugin doesn't correctly use the global variable "cb"
the search paths have the form
$(#cb)/include
$(#cb)/include/wxscintilla/include
but should look like this for greater compatibility
$(#cb.include)
$(#cb.include)/wxscintilla/include
Revvy:
--- Quote from: yop on March 11, 2008, 04:05:48 pm ---
--- Quote from: Revvy on March 08, 2008, 04:17:43 am ---I really like how this plugin is working so well, but I have one problem after following the wiki pages. My project gets this error when I try to build:
make.exe: *** No rule to make target `..\..\Qt\4.3.3\mkspecs\default\qmake.conf', needed by `Makefile.Debug'. Stop.
Process terminated with status 2 (0 minutes, 0 seconds)
0 errors, 0 warnings
--- End quote ---
Can you prepare a minimal project that reproduces this issue and upload it in the bug tracker?
--- End quote ---
Done.
yop:
--- Quote from: Revvy on April 06, 2008, 06:53:39 pm ---Done.
--- End quote ---
Thanks
--- Quote from: Omni on April 06, 2008, 03:12:36 am ---The Code::Blocks project file of the qtWorkbench plugin doesn't correctly use the global variable "cb"
the search paths have the form
$(#cb)/include
$(#cb)/include/wxscintilla/include
but should look like this for greater compatibility
$(#cb.include)
$(#cb.include)/wxscintilla/include
--- End quote ---
Thanks I 'll prepare that
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version