Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Installation and Deployment
  4. Building an app based on a dev (manual) build of Qt
Forum Updated to NodeBB v4.3 + New Features

Building an app based on a dev (manual) build of Qt

Scheduled Pinned Locked Moved Solved Installation and Deployment
13 Posts 5 Posters 974 Views 2 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.
  • T Offline
    T Offline
    tcee_14007
    wrote on last edited by
    #3

    I ran the command in the build folder itself

    jsulmJ 1 Reply Last reply
    0
    • T tcee_14007

      I ran the command in the build folder itself

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

      @tcee_14007 But where did "make install" install it?

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

      1 Reply Last reply
      0
      • T Offline
        T Offline
        tcee_14007
        wrote on last edited by tcee_14007
        #5

        I'm sorry, but I'm unable to find it.
        However, I have attached the bash output here: https://pastebin.com/Y4ZEVtDr
        could you please take a look at it ?

        1 Reply Last reply
        0
        • KH-219DesignK Offline
          KH-219DesignK Offline
          KH-219Design
          wrote on last edited by
          #6

          It seems like what was pasted into pastebin was from a subsequent (not original) run of "make install". There is a bunch of output like "Nothing to be done", which indicates that things were already installed. During an initial run I would expect to see a bunch of cp action showing things being copied to some destination.

          Unless you, @tcee_14007 explicitly used the -prefix argument when you ran configure, then things probably installed to a system folder.

          If you run ./configure --help you should see what the default prefix is.

          On my system, it shows:

            -prefix <dir> ...... The deployment directory, as seen on the target device.
                                 [/usr/local/Qt-$QT_VERSION; qtbase build directory if
                                 -developer-build]
          

          If you think that the -prefix argument was used, then look at the config.log file (wherever you ran configure & make) and you should be able to retrieve the arguments from config.log (try searching the log for the phrase "Command line")

          www.219design.com
          Software | Electrical | Mechanical | Product Design

          1 Reply Last reply
          1
          • T Offline
            T Offline
            tcee_14007
            wrote on last edited by tcee_14007
            #7

            I had added -developer-build to the configure command, and it said that I shouldn't run make install. I ran it for the first time after @jsulm asked me to, so the problem might be different. And I checked, I didn't add -prefix.

            1 Reply Last reply
            0
            • KH-219DesignK Offline
              KH-219DesignK Offline
              KH-219Design
              wrote on last edited by
              #8

              Interesting!

              I had never paid any attention to that option. (although I now see that in the snippet of help text I posted for prefix earlier, there is a mention of developer-build, too!)

              I found this mailing list entry "What does '-developer-build' actually do":
              https://lists.qt-project.org/pipermail/qt-interest-old/2010-April/021593.html

              As @jsulm has already highlighted, the key thing is still to figure out where on earth your manually-compiled binaries got "installed" to.

              For developer-build they are supposedly in $PWD (of wherever you ran make, I guess)?

              Maybe just try to find where it put qmake:

              cd $WHEREVER_YOU_PUT_YOUR_MANUAL_QT_STUFF
              find  . -type f -name qmake
              

              www.219design.com
              Software | Electrical | Mechanical | Product Design

              1 Reply Last reply
              0
              • KH-219DesignK Offline
                KH-219DesignK Offline
                KH-219Design
                wrote on last edited by
                #9

                When I say that I have never paid attention to developer-build, I suppose I should be explicit about what I normally do do.

                I often build debug versions of Qt, and occasionally even experiment with editing the source and rebuilding with my changes included.

                When I do that I simply run configure with the -prefix argument pointing at some special folder that won't pollute my global /usr/ or /usr/local areas.

                And of course I add the -debug flag so that I get debug symbols.

                Full example here.

                When using -prefix and then make && make install, the ultimate installation location is controlled by whatever I chose to specify as prefix.

                This isn't necessarily better than using developer-build !!

                Just explaining how those of us who were ignorant of developer-build have been doing this ;)

                www.219design.com
                Software | Electrical | Mechanical | Product Design

                1 Reply Last reply
                1
                • T Offline
                  T Offline
                  tcee_14007
                  wrote on last edited by
                  #10

                  Sorry to post it so late, but I built it again without developer-build , and now adding the path to the explicit install directory somewhat solved my problem.

                  KH-219DesignK 1 Reply Last reply
                  1
                  • T tcee_14007

                    Sorry to post it so late, but I built it again without developer-build , and now adding the path to the explicit install directory somewhat solved my problem.

                    KH-219DesignK Offline
                    KH-219DesignK Offline
                    KH-219Design
                    wrote on last edited by
                    #11

                    @tcee_14007 said in Building an app based on a dev (manual) build of Qt:

                    Sorry to post it so late, but I built it again without developer-build , and now adding the path to the explicit install directory somewhat solved my problem.

                    I don't think you are posting late :)

                    There was no deadline. I'm glad to hear back about what worked.

                    Maybe someone who knows more about developer-build can comment about how to successfully use DCMAKE_PREFIX_PATH with a Qt "install" that was created with developer-build.

                    www.219design.com
                    Software | Electrical | Mechanical | Product Design

                    1 Reply Last reply
                    0
                    • SGaistS Offline
                      SGaistS Offline
                      SGaist
                      Lifetime Qt Champion
                      wrote on last edited by
                      #12

                      Hi,

                      The developer-build option is for people wanting to hack on Qt itself so it should not be used for deployment purpose nor development other than Qt itself. IIRC, there are some difference in the set of options and flags used for the compilers.

                      It's an "in-place" build so there's nothing to install.

                      Interested in AI ? www.idiap.ch
                      Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

                      O 1 Reply Last reply
                      1
                      • SGaistS SGaist

                        Hi,

                        The developer-build option is for people wanting to hack on Qt itself so it should not be used for deployment purpose nor development other than Qt itself. IIRC, there are some difference in the set of options and flags used for the compilers.

                        It's an "in-place" build so there's nothing to install.

                        O Offline
                        O Offline
                        OliviaKind22
                        Banned
                        wrote on last edited by
                        #13
                        This post is deleted!
                        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