guenthk Messages: 3 Registered: April 2006 Location: Germany
Junior Member
luzr wrote on Sat, 29 April 2006 06:09
"non-U++" applications here means applications not using U++ library.
Actually, situation here is the same as with e.g. MS Visual Studion - its native build system does not use makefiles as well..
Mirek
We use VC++ Express 2005 for the VC++ version of our software. So we could also use the U++ build system, if we didn't need to change our principle structure of sub-directories/sub-projects and if we could stay with Qt instead of using the U++ libraries.
For us, the main problem seems to be the very rudimentary state of the U++ documentation and the fact that Qt and Qt applications make heavy use of macros in C++, which might disturb the U++ code analyzer.
I haven't been able so far to jump from the implementation of a class method to its declaration: This always brings me just to the beginning of some arbitrary header file that is completely unrelated to the class/method in question. Will this problem disappear when using the U++ build system?
In order to make use of the U++ build system: Would I have to make U++ packages from our existing sub-projects? Will this work without also using U++ built-in packages and libraries?
Is it possible to use the same U++ configuration (*.upp) files on Windows as well as Linux?
When using the U++ build system: Does U++ provide an easy way to jump from the compiler's error output to the respective erroneous source line by a single (or double) click?