Greets,
This may be an existing feature that I have overlooked (with the exception of the macros since I cheated and looked at the code!
however, I've recently started working with Trolltech's QT package and was hoping for a way to integrate their UI compiler with Code::Blocks.
While I understand there is a default QT project configuration, I have set up the QT designer as an external tool. Also, I've configured the UIC.EXE (QT UI Compiler) as an external tool as well; I've configured the following command line:
${ACTIVE_EDITOR_FILENAME} -o ${ACTIVE_EDITOR_FILENAME}.h
While it accomplishes what I want to do, it would be nice to provide an "ACTIVE_EDITOR_FILENAME_PREFIX" and "ACTIVE_EDITOR_FILENAME_SUFFIX" macro --the first gives you all characters up to, but not including the last dot '.'; and the second gives you all characters after the last dot. That way, I could name my files "SomeDialog.h" instead of "SomeDialog.ui.h".
Alternatively, it would be nice (and it may exist, I just haven't found it yet) a provision in which a new 'program' can be added to the "Global Compiler Settings" area, most specifically the 'Programs' outer tab and the 'Program Files' inner tab which: a) associates a file extension for a file in the project to a command line program outside of those which already exist (perhaps this is configurable?); b) allows the command line to use macro expansion when those files are being 'built' (or perhaps adds that to its internal 'make' facility); and c) allows for the output extension to be provided to note the build target in any generated makefiles.
I noticed there was a "file extension handling" area of configuration, but it wasn't apparent if that was tied to a build. Ideally though, it would be more ideal to go with the second suggestion and allow it to be configured as an actual program used at compile-time instead of going the external tool route.
One more note: I did notice the post/build steps, but I don't know if they are easily adapted to running the command line tool against items that are included in the project. With regards to build targets added to a project and having the ability to add a new program and command line specification, I think the variables for macro expansion for the currently processed file which would be most useful are: project directly, currently processed filename (as well as its prefix/suffix).
If I'm missing something here (or there's a better way to do this I haven't yet found) please correct my ignorance.
Regards,
Falcon