User forums > Help
QT and C::B problem - header files not found
mandrav:
--- Quote from: Michael on March 31, 2006, 11:18:41 am ---
--- Quote from: yop on March 31, 2006, 11:11:03 am ---Meta compilation is the major issue.
--- End quote ---
Would not be possible to use some kind of pre-build step in C::B for meta-compilation?
Best wishes,
Michael
--- End quote ---
I 'm sure it is.
Yop, have you tried changing the build command for each .ui file? I 'm talking about right-clicking on a .ui file and selecting "Properties". Yes, it would be a manual procedure for every .ui file you add to the project but maybe it would work and take full advantage of the existing build system...
yop:
It's not only that I'm afraid, it's also header files that contain the Q_OBJECT macro that must pass through the meta object compiler generating some indermediate code in a different .cpp file that must also participate in the build process. Exactly the things you suggest were my thoughts back in beta 4 (or 5? it was the same time you won that gfx card and I noticed your signature ;)) but I didn't have any luck with it. I 'll give it another try as it seems a cleaner solution (and the feature requests for Qt support keep coming in).
mandrav:
--- Quote from: yop on March 31, 2006, 12:03:54 pm ---I 'll give it another try as it seems a cleaner solution (and the feature requests for Qt support keep coming in).
--- End quote ---
Well, don't sweat over this too much. The new compiler definition framework is planned before the next release so it would then be possible to support QT natively :)
EDIT: If I remember well, back from my QT days, moc (for headers) and uic (for .ui files) are the only extra needed programs/steps. Right?
Michael:
--- Quote from: yop on March 31, 2006, 12:03:54 pm ---It's not only that I'm afraid, it's also header files that contain the Q_OBJECT macro that must pass through the meta object compiler generating some indermediate code in a different .cpp file that must also participate in the build process. Exactly the things you suggest were my thoughts back in beta 4 (or 5? it was the same time you won that gfx card and I noticed your signature ;)) but I didn't have any luck with it. I 'll give it another try as it seems a cleaner solution (and the feature requests for Qt support keep coming in).
--- End quote ---
For my project, I use Qt and Visual Studio .NET 2003 (:roll:). With Qt 3 it was possible to integrate it into VS, but it is not necessary (even if comfortable :)). As alternative, it is possible is to use VS "Custom Build" for .ui and the files containing the macro Q_OBJECT. Then during the building, the required Qt tools were called. I am not sure, but may be such a custom build could be used within the pre-build step of C::B.
Best wishes,
Michael
Michael:
--- Quote from: mandrav on March 31, 2006, 11:41:26 am ---
--- Quote from: Michael on March 31, 2006, 11:18:41 am ---
--- Quote from: yop on March 31, 2006, 11:11:03 am ---Meta compilation is the major issue.
--- End quote ---
Would not be possible to use some kind of pre-build step in C::B for meta-compilation?
Best wishes,
Michael
--- End quote ---
I 'm sure it is.
Yop, have you tried changing the build command for each .ui file? I 'm talking about right-clicking on a .ui file and selecting "Properties". Yes, it would be a manual procedure for every .ui file you add to the project but maybe it would work and take full advantage of the existing build system...
--- End quote ---
I have had a look at file property. I would like to ask if under Properties-->Advanced tab the custom build needs to be related to a C::B compiler (e.g., GCC) or if an external tool can be called. Just for info, VS in its "Custom Build" has 4 parts: Command line, Description, Outputs and Additional Dependencies. This makes relatively easy to manage Qt special files.
Best wishes,
Michael
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version