Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Qt Creator and other tools
  4. Editing a project consisting of multiple libraries and executables
Forum Updated to NodeBB v4.3 + New Features

Editing a project consisting of multiple libraries and executables

Scheduled Pinned Locked Moved Qt Creator and other tools
8 Posts 2 Posters 2.9k Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • B Offline
    B Offline
    bamberg
    wrote on last edited by
    #1

    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

    1 Reply Last reply
    0
    • A Offline
      A Offline
      andre
      wrote on last edited by
      #2

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

      1 Reply Last reply
      0
      • B Offline
        B Offline
        bamberg
        wrote on last edited by
        #3

        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.

        1 Reply Last reply
        0
        • A Offline
          A Offline
          andre
          wrote on last edited by
          #4

          Well, they can be ordered...

          @
          CONFIG += ordered
          @

          They will not be 'merged' together.

          1 Reply Last reply
          0
          • B Offline
            B Offline
            bamberg
            wrote on last edited by
            #5

            Dear Andre,

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

            Brian

            1 Reply Last reply
            0
            • A Offline
              A Offline
              andre
              wrote on last edited by
              #6

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

              1 Reply Last reply
              0
              • B Offline
                B Offline
                bamberg
                wrote on last edited by
                #7

                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

                1 Reply Last reply
                0
                • A Offline
                  A Offline
                  andre
                  wrote on last edited by
                  #8

                  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?

                  1 Reply Last reply
                  0

                  • Login

                  • Login or register to search.
                  • First post
                    Last post
                  0
                  • Categories
                  • Recent
                  • Tags
                  • Popular
                  • Users
                  • Groups
                  • Search
                  • Get Qt Extensions
                  • Unsolved