Editing a project consisting of multiple libraries and executables

[bamberg]

I have a large project, which consists of multiple libraries and executables. Currently, I am using vim for my development, but I also wanted to try out qtcreator.

My current setup is as follows. Every library has its own .pro file, and I have a central makefile which calls qmake, make, make install on the libraries in the correct order. The libraries and applications then link against the installed versions of the other libraries.

This works beautifully in vim, where I can use quickfix to jump to the errors occuring in any compilation unit easily.

I can't see how I can replicate this behaviour in qtcreator. Also, I am annoyed that qtcreator is creating build directories all over my source code. My current setup has a dedicated build directory where all temporary files are stored. This is nicely supported by qmake. How do I achieve this with the qtcreator?

Thank you for your answers,

Brian

[andre]

Did you look into using a subdirs-type meta .pro file?

[bamberg]

Hello Andre,

thank you for the answer. Yes, I tried that, but as far as I understand, which might not be much, this does not compile and install one subdir after the other, but instead tries to merge everything into one project, and the dependencies get mangled.

[andre]

Well, they can be ordered...

@
CONFIG += ordered
@

They will not be 'merged' together.

[bamberg]

Dear Andre,

thanks a lot. That actually seems to work. And I even figured out how to create a make install deploy setting.

Brian

[andre]

Ok, good to hear your project is working out fine.

[bamberg]

Dear Andre,

it seems I decided too fast that it works. The problem is, that I am trying to link against the installed libraries, but they won't be installed during the compilation. Essentially, it works if I do

in each subdirectory:
make
make install

, but the combined .pro file tries to do

in each subdirectory:
make
then in each subdirectory:
make install

which fails.

Brian

[andre]

I don't see why you'd need to link against installed libraries? The installation location has nothing to do with their location during compilation, right?