![]() To get the location of the qmake that is accessed via your $PATH (it will most likely be /usr/bin/qmake). Make sure you don't have any older qt package is right, qt-4.8.86_64 is Qt 4.8.5. ![]() This will give you the list of Qt packages actually installed on your system (and the ones available for installation). You should check what Qt packages are installed with: (modifications to sources, project files, etc.) # no need to call qmake directly from this point onwards ![]() To recap, for any given project, you'd do: set CPUS=$(grep -c ^processor /proc/cpuinfo) I personally find no need for qmake in the PATH at all - it's too easy to run wrong one by mistake. Subsequent invocations are done via make qmake_all. The version of qmake present in your PATH is of no consequence, generally speaking, since for any given project you only need to invoke qmake directly once - you do so by giving the full path to the qmake in the install of Qt you're using in the build. To find all qmake binaries on your system, you can e.g. There's a 1:1 mapping between a qmake binary and a Qt installation. It's on you to select the version of qmake that represents the Qt installation you're wishing to use. I usually have dozens on my systems - multiple versions, targets, configurations. Qt is designed to support multiple parallel installations.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |