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. what is auto generating LIBS path in makefile "qt creator"
Forum Updated to NodeBB v4.3 + New Features

what is auto generating LIBS path in makefile "qt creator"

Scheduled Pinned Locked Moved Unsolved General and Desktop
22 Posts 3 Posters 1.8k 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.
  • M micha_eleric

    @ChrisW67 if i dont specify which folder libs are in, then then when executable goes to another computer, or as i found out, my computer gets os reinstalled, executable can not find a lib

    C Offline
    C Offline
    ChrisW67
    wrote on last edited by
    #9

    @micha_eleric said in what is auto generating LIBS path in makefile "qt creator":

    if i dont specify which folder libs are in, then then when executable goes to another computer, or as i found out, my computer gets os reinstalled, executable can not find a lib

    You need to deploy your application properly. This is not a function of the build and link issue you are having.

    Regarding libQt5SerialPort

    that is because it is at
    -L/home/micha_eleric/ProjectGUI/lib

    Why?

    M 1 Reply Last reply
    1
    • C ChrisW67

      @micha_eleric said in what is auto generating LIBS path in makefile "qt creator":

      if i dont specify which folder libs are in, then then when executable goes to another computer, or as i found out, my computer gets os reinstalled, executable can not find a lib

      You need to deploy your application properly. This is not a function of the build and link issue you are having.

      Regarding libQt5SerialPort

      that is because it is at
      -L/home/micha_eleric/ProjectGUI/lib

      Why?

      M Offline
      M Offline
      micha_eleric
      wrote on last edited by
      #10

      @ChrisW67 said in what is auto generating LIBS path in makefile "qt creator":

      @micha_eleric said in what is auto generating LIBS path in makefile "qt creator":

      if i dont specify which folder libs are in, then then when executable goes to another computer, or as i found out, my computer gets os reinstalled, executable can not find a lib

      You need to deploy your application properly. This is not a function of the build and link issue you are having.

      Regarding libQt5SerialPort

      that is because it is at
      -L/home/micha_eleric/ProjectGUI/lib

      Why?

      so i dont send the entire Qt folder, just the libs that project uses

      C 1 Reply Last reply
      0
      • M micha_eleric

        @ChrisW67 said in what is auto generating LIBS path in makefile "qt creator":

        @micha_eleric said in what is auto generating LIBS path in makefile "qt creator":

        if i dont specify which folder libs are in, then then when executable goes to another computer, or as i found out, my computer gets os reinstalled, executable can not find a lib

        You need to deploy your application properly. This is not a function of the build and link issue you are having.

        Regarding libQt5SerialPort

        that is because it is at
        -L/home/micha_eleric/ProjectGUI/lib

        Why?

        so i dont send the entire Qt folder, just the libs that project uses

        C Offline
        C Offline
        ChrisW67
        wrote on last edited by
        #11

        @micha_eleric said in what is auto generating LIBS path in makefile "qt creator":

        so i dont send the entire Qt folder, just the libs that project uses

        Put the libraries back where they belong on your development machine. They are not part of your project's build products.

        When you go to build a deployment package, then you make a copy to deploy.

        M 1 Reply Last reply
        3
        • C ChrisW67

          @micha_eleric said in what is auto generating LIBS path in makefile "qt creator":

          so i dont send the entire Qt folder, just the libs that project uses

          Put the libraries back where they belong on your development machine. They are not part of your project's build products.

          When you go to build a deployment package, then you make a copy to deploy.

          M Offline
          M Offline
          micha_eleric
          wrote on last edited by
          #12

          @ChrisW67 said in what is auto generating LIBS path in makefile "qt creator":

          @micha_eleric said in what is auto generating LIBS path in makefile "qt creator":

          so i dont send the entire Qt folder, just the libs that project uses

          Put the libraries back where they belong on your development machine. They are not part of your project's build products.

          When you go to build a deployment package, then you make a copy to deploy.

          did, put copy of libs in folder, and executable does not work if qt is not in home folder.

          jsulmJ C 2 Replies Last reply
          0
          • M micha_eleric

            @ChrisW67 said in what is auto generating LIBS path in makefile "qt creator":

            @micha_eleric said in what is auto generating LIBS path in makefile "qt creator":

            so i dont send the entire Qt folder, just the libs that project uses

            Put the libraries back where they belong on your development machine. They are not part of your project's build products.

            When you go to build a deployment package, then you make a copy to deploy.

            did, put copy of libs in folder, and executable does not work if qt is not in home folder.

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

            @micha_eleric Probably still something is missing. Any errors if you start the app in a terminal?
            You also should take a look at https://doc.qt.io/qt-6/deployment.html

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

            M 1 Reply Last reply
            0
            • M micha_eleric

              @ChrisW67 said in what is auto generating LIBS path in makefile "qt creator":

              @micha_eleric said in what is auto generating LIBS path in makefile "qt creator":

              so i dont send the entire Qt folder, just the libs that project uses

              Put the libraries back where they belong on your development machine. They are not part of your project's build products.

              When you go to build a deployment package, then you make a copy to deploy.

              did, put copy of libs in folder, and executable does not work if qt is not in home folder.

              C Offline
              C Offline
              ChrisW67
              wrote on last edited by
              #14

              @micha_eleric said in what is auto generating LIBS path in makefile "qt creator":

              did, put copy of libs in folder, and executable does not work if qt is not in home folder.

              Install the Qt library version, including optional components, you wish to build with. Nothing in this directory tree needs to be changed or moved. Then the process goes:

              • Build application in your development environment using the qmake from intact Qt library you installed. No part of the Qt libraries are in your build directory.
              • Test application in your development environment. Everything is exactly where it was at build time and the run time environment matches the build time environment.
              • Rinse and repeat steps above until the application works.
              • Only then do you consider what has to be deployed in order to test the application away from the development environment before releasing it in the wild.

              It is hard to help if you cannot tell the difference between building the application (which is what is failing here) and deploying the application (which is what you seem to think you are doing). If you mangle your Qt installation, or mix and match several versions, or remove files that are expected in certain places then you get to keep the broken pieces.

              1 Reply Last reply
              1
              • jsulmJ jsulm

                @micha_eleric Probably still something is missing. Any errors if you start the app in a terminal?
                You also should take a look at https://doc.qt.io/qt-6/deployment.html

                M Offline
                M Offline
                micha_eleric
                wrote on last edited by micha_eleric
                #15

                @jsulm said in what is auto generating LIBS path in makefile "qt creator":

                @micha_eleric Probably still something is missing. Any errors if you start the app in a terminal?
                You also should take a look at https://doc.qt.io/qt-6/deployment.html

                if i move Qt5.12.12 into a different folder, i get:
                error while loading shared libraries: libQt5SerialPort.so.5: cannot open shared object file: No such file or directory

                even after i installed qt-everywhere-src-5.15.13, then deployed

                maybe i have to many qt installed

                5.15.13 is not showing up for build. was it not properly installed?

                M 1 Reply Last reply
                0
                • M micha_eleric

                  @jsulm said in what is auto generating LIBS path in makefile "qt creator":

                  @micha_eleric Probably still something is missing. Any errors if you start the app in a terminal?
                  You also should take a look at https://doc.qt.io/qt-6/deployment.html

                  if i move Qt5.12.12 into a different folder, i get:
                  error while loading shared libraries: libQt5SerialPort.so.5: cannot open shared object file: No such file or directory

                  even after i installed qt-everywhere-src-5.15.13, then deployed

                  maybe i have to many qt installed

                  5.15.13 is not showing up for build. was it not properly installed?

                  M Offline
                  M Offline
                  micha_eleric
                  wrote on last edited by micha_eleric
                  #16

                  i /tmp/qt-everywhere-src-5.15.13/configure -static, gmake, sudo gmake install, but did not show up in qt creator project, which explains why deploy did not work.
                  i then /tmp/qt-everywhere-src-5.15.13/configure -static again, uninstalled, reinstalled, and still does not show up in qt creator projects as an option for build.

                  jsulmJ 1 Reply Last reply
                  0
                  • M micha_eleric

                    i /tmp/qt-everywhere-src-5.15.13/configure -static, gmake, sudo gmake install, but did not show up in qt creator project, which explains why deploy did not work.
                    i then /tmp/qt-everywhere-src-5.15.13/configure -static again, uninstalled, reinstalled, and still does not show up in qt creator projects as an option for build.

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

                    @micha_eleric said in what is auto generating LIBS path in makefile "qt creator":

                    and still does not show up in qt creator projects as an option for build

                    Then create a Kit in QtCreator pointing to this Qt build...
                    And as already suggested take a look at https://doc.qt.io/qt-6/deployment.html to learn how to deploy a Qt application.

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

                    M 2 Replies Last reply
                    2
                    • jsulmJ jsulm

                      @micha_eleric said in what is auto generating LIBS path in makefile "qt creator":

                      and still does not show up in qt creator projects as an option for build

                      Then create a Kit in QtCreator pointing to this Qt build...
                      And as already suggested take a look at https://doc.qt.io/qt-6/deployment.html to learn how to deploy a Qt application.

                      M Offline
                      M Offline
                      micha_eleric
                      wrote on last edited by micha_eleric
                      #18

                      @jsulm said in what is auto generating LIBS path in makefile "qt creator":

                      And as already suggested take a look at https://doc.qt.io/qt-6/deployment.html to learn how to deploy a Qt application.

                      have been

                      1 Reply Last reply
                      0
                      • jsulmJ jsulm

                        @micha_eleric said in what is auto generating LIBS path in makefile "qt creator":

                        and still does not show up in qt creator projects as an option for build

                        Then create a Kit in QtCreator pointing to this Qt build...
                        And as already suggested take a look at https://doc.qt.io/qt-6/deployment.html to learn how to deploy a Qt application.

                        M Offline
                        M Offline
                        micha_eleric
                        wrote on last edited by micha_eleric
                        #19

                        @jsulm said in what is auto generating LIBS path in makefile "qt creator":

                        @micha_eleric said in what is auto generating LIBS path in makefile "qt creator":

                        Then create a Kit in QtCreator pointing to this Qt build...
                        And as already suggested take a look at https://doc.qt.io/qt-6/deployment.html to learn how to deploy a Qt application.

                        Set up new Qt versions

                        To add a Qt version:

                        Select Preferences > Kits > Qt Versions > Add.    [done]
                        Select the qmake executable for the Qt version to add.    [[nothing, and no clue where qmake(qmake**) is, what it looks like, nor what folder it might be in]
                        

                        [ did a search for "qmake", it gave .h .cpp .pro .pri .qdoc Makefile .conf , all i would guess is not close to the qmake that it is looking for. ]
                        [ i found /usr/bin/qmake, which list as an executable, but when selected and Open, it says The qmake executable /usr/lib/qt5/bin/qmake could not be added: qmake "/usr/lib/qt5/bin/qmake" is not an executable.]
                        [well, i found /usr/local/Qt-5.15.13/bin/qmake, compiled, but gave:
                        name
                        qt.qpa.plugin: Could not find the Qt platform plugin "xcb" in ""
                        This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. ]
                        [ well, found:
                        "Set the environment variable QT_DEBUG_PLUGINS=1 and then run your application. This should give more detailed information on why it failed." results in:
                        name
                        QFactoryLoader::QFactoryLoader() ignoring "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3" since plugins are disabled in static builds
                        qt.qpa.plugin: Could not find the Qt platform plugin "xcb" in ""
                        This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. ]

                        Select the Qt version to view and edit it.
                        In the Name field, edit the name that Qt Creator suggests for the Qt version.
                        In the qmake path field, you can change the qmake location.
                        If the Qt version is for QNX, enter the path to the QNX SDK in the QNX SDK field.
                        

                        still wander if i found the correct qmake

                        jsulmJ 1 Reply Last reply
                        0
                        • M Offline
                          M Offline
                          micha_eleric
                          wrote on last edited by
                          #20

                          @jsulm said in what is auto generating LIBS path in makefile "qt creator":

                          @micha_eleric said in what is auto generating LIBS path in makefile "qt creator":
                          .>And as already suggested take a look at https://doc.qt.io/qt-6/deployment.html to learn how to deploy a Qt application.

                          according to:
                          https://doc.qt.io/qt-6/linux-building.html

                          Step 4: Using Qt

                          After Qt is installed, you can start building applications with it.

                          If you work from the command line, consider adding the Qt tools to your default PATH. This is done as follows:

                          In .profile (if your shell is bash, ksh, zsh or sh), add the following lines:

                          PATH=/usr/local/Qt-6.6.3/bin:$PATH
                          export PATH

                          changed 6.6.3 to 5.15.13, it errors with:
                          error: Extra characters after test expression.
                          at export PATH

                          1 Reply Last reply
                          0
                          • M micha_eleric

                            @jsulm said in what is auto generating LIBS path in makefile "qt creator":

                            @micha_eleric said in what is auto generating LIBS path in makefile "qt creator":

                            Then create a Kit in QtCreator pointing to this Qt build...
                            And as already suggested take a look at https://doc.qt.io/qt-6/deployment.html to learn how to deploy a Qt application.

                            Set up new Qt versions

                            To add a Qt version:

                            Select Preferences > Kits > Qt Versions > Add.    [done]
                            Select the qmake executable for the Qt version to add.    [[nothing, and no clue where qmake(qmake**) is, what it looks like, nor what folder it might be in]
                            

                            [ did a search for "qmake", it gave .h .cpp .pro .pri .qdoc Makefile .conf , all i would guess is not close to the qmake that it is looking for. ]
                            [ i found /usr/bin/qmake, which list as an executable, but when selected and Open, it says The qmake executable /usr/lib/qt5/bin/qmake could not be added: qmake "/usr/lib/qt5/bin/qmake" is not an executable.]
                            [well, i found /usr/local/Qt-5.15.13/bin/qmake, compiled, but gave:
                            name
                            qt.qpa.plugin: Could not find the Qt platform plugin "xcb" in ""
                            This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. ]
                            [ well, found:
                            "Set the environment variable QT_DEBUG_PLUGINS=1 and then run your application. This should give more detailed information on why it failed." results in:
                            name
                            QFactoryLoader::QFactoryLoader() ignoring "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3" since plugins are disabled in static builds
                            qt.qpa.plugin: Could not find the Qt platform plugin "xcb" in ""
                            This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. ]

                            Select the Qt version to view and edit it.
                            In the Name field, edit the name that Qt Creator suggests for the Qt version.
                            In the qmake path field, you can change the qmake location.
                            If the Qt version is for QNX, enter the path to the QNX SDK in the QNX SDK field.
                            

                            still wander if i found the correct qmake

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

                            @micha_eleric said in what is auto generating LIBS path in makefile "qt creator":

                            i found /usr/local/Qt-5.15.13/bin/qmake

                            Bellow you write something about Qt 6.6.3 - so what Qt version did you actually build and where did you install it?

                            "qt.qpa.plugin: Could not find the Qt platform plugin "xcb" in """ - was XCB plug-in enabled when running configure before building?

                            "[[nothing, and no clue where qmake(qmake**) is" - where you installed your Qt build...

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

                            M 1 Reply Last reply
                            0
                            • jsulmJ jsulm

                              @micha_eleric said in what is auto generating LIBS path in makefile "qt creator":

                              i found /usr/local/Qt-5.15.13/bin/qmake

                              Bellow you write something about Qt 6.6.3 - so what Qt version did you actually build and where did you install it?

                              "qt.qpa.plugin: Could not find the Qt platform plugin "xcb" in """ - was XCB plug-in enabled when running configure before building?

                              "[[nothing, and no clue where qmake(qmake**) is" - where you installed your Qt build...

                              M Offline
                              M Offline
                              micha_eleric
                              wrote on last edited by micha_eleric
                              #22

                              @jsulm said in what is auto generating LIBS path in makefile "qt creator":

                              @micha_eleric said in what is auto generating LIBS path in makefile "qt creator":

                              i found /usr/local/Qt-5.15.13/bin/qmake

                              Bellow you write something about Qt 6.6.3 - so what Qt version did you actually build and where did you install it?

                              "qt.qpa.plugin: Could not find the Qt platform plugin "xcb" in """ - was XCB plug-in enabled when running configure before building?

                              "[[nothing, and no clue where qmake(qmake**) is" - where you installed your Qt build...

                              Qt 5.12.12 build from QT creator offline install, which went to Home and somewheres sudo is needed, but did not have features that online install has
                              Qt 6.6.2 built from Qt Creator online install, which went to Home and somewheres sudo is needed
                              Qt 5.15.13 built from https://download.qt.io/official_releases/qt/5.15/, which has some in Home and somewheres sudo is needed

                              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