Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. Project ERROR: You cannot configure qt separately within a top-level build. ?

Project ERROR: You cannot configure qt separately within a top-level build. ?

Scheduled Pinned Locked Moved Unsolved General and Desktop
configure
10 Posts 3 Posters 8.4k Views
  • 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.
  • R Offline
    R Offline
    RickF
    wrote on last edited by
    #1

    I think I'm doing things correctly, but I get the above error message.

    I have a directory setup
    /home/rickf/projects/qt510
    /home/rickf/projects/qt510/qt5
    /home/rickf/projects/qt510/qt5-build

    I do a git clone an checkout into qt510, which gives me the qt5 folder.
    Then from within the qt5-build folder I use
    ../qt5/configure -force-debug-info -nomake tests -sql-all

    and it goes along and finishes like

    Creating qmake...
    ...........................................................................................Done.
    Project ERROR: You cannot configure qt separately within a top-level build.

    What did I do incorrectly?

    Thanks

    Rick

    1 Reply Last reply
    0
    • sierdzioS Offline
      sierdzioS Offline
      sierdzio
      Moderators
      wrote on last edited by
      #2

      The steps you described and the directory structure is OK.

      Since you're not using a tarball, though, there are additional steps that may need to be taken: namely, running init-repository. Here's a guide for you.

      (Z(:^

      1 Reply Last reply
      2
      • R Offline
        R Offline
        RickF
        wrote on last edited by
        #3

        That’s the guide I was using. I did the Perl init-repository same result.

        Anyone try this lately? I’ve done a clean checkout and build 4 or5 tines now with same results...

        Thanks

        Rick

        jsulmJ sierdzioS 2 Replies Last reply
        0
        • R RickF

          That’s the guide I was using. I did the Perl init-repository same result.

          Anyone try this lately? I’ve done a clean checkout and build 4 or5 tines now with same results...

          Thanks

          Rick

          jsulmJ Offline
          jsulmJ Offline
          jsulm
          Lifetime Qt Champion
          wrote on last edited by
          #4

          @RickF Did you check the link @sierdzio gave you?

          https://forum.qt.io/topic/113070/qt-code-of-conduct

          sierdzioS 1 Reply Last reply
          0
          • jsulmJ jsulm

            @RickF Did you check the link @sierdzio gave you?

            sierdzioS Offline
            sierdzioS Offline
            sierdzio
            Moderators
            wrote on last edited by
            #5

            @jsulm said in Project ERROR: You cannot configure qt separately within a top-level build. ?:

            @RickF Did you check the link @sierdzio gave you?

            he did, he used the same guide

            (Z(:^

            1 Reply Last reply
            0
            • R RickF

              That’s the guide I was using. I did the Perl init-repository same result.

              Anyone try this lately? I’ve done a clean checkout and build 4 or5 tines now with same results...

              Thanks

              Rick

              sierdzioS Offline
              sierdzioS Offline
              sierdzio
              Moderators
              wrote on last edited by
              #6

              @RickF said in Project ERROR: You cannot configure qt separately within a top-level build. ?:

              Anyone try this lately? I’ve done a clean checkout and build 4 or5 tines now with same results...

              I'm compiling Qt fairly often, but not from git - so no. I'm using the tarballs, maybe they'll work better for you: https://download.qt.io/official_releases/qt/5.10/5.10.1/single/

              (Z(:^

              1 Reply Last reply
              0
              • R Offline
                R Offline
                RickF
                wrote on last edited by
                #7

                One thing I notice is that I use the following:

                ../qt-everywhere-src-5.10.1/configure -opensource -confirm-license -force-debug-info -nomake tests -sql-all -sqlite qt

                and it echoes

                • cd qtbase
                • /home/rickf/projects/qt510/qt-everywhere-src-5.10.1/qtbase/configure -top-level -opensource -confirm-license -force-debug-info -nomake tests -sql-all -sqlite qt
                  Preparing build tree...
                  Creating qmake...

                notice it prefixed my options with -top-level

                and the error message appropriately says

                Project ERROR: You cannot configure qt separately within a top-level build.

                so, is there something to turn off -top-level? It does this even when I specify -prefix option.

                1 Reply Last reply
                0
                • sierdzioS Offline
                  sierdzioS Offline
                  sierdzio
                  Moderators
                  wrote on last edited by
                  #8

                  Your flags are OK and this should not be happening... hm. Maybe try removing these flags just to see if one of them is the cause: -force-debug-info -sql-all -sqlite qt.

                  (Z(:^

                  1 Reply Last reply
                  0
                  • R Offline
                    R Offline
                    RickF
                    wrote on last edited by
                    #9

                    seems that it is -force-debug-info

                    R 1 Reply Last reply
                    0
                    • R RickF

                      seems that it is -force-debug-info

                      R Offline
                      R Offline
                      RickF
                      wrote on last edited by
                      #10

                      Ok... well it seems now that the answer is that I need to use -prefix <> option.

                      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