Databases
StackOverflow2013
Postsdbo
POHow to include a certain Qt installation using CMake?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to include a certain Qt installation using CMake?
    primarykey
    data
    text
    <p>We have plenty Qt copies on every dev PC - each project has its own Qt copy in the thirdparties directory. That's done due to each project is developed and tested with its own Qt; an often case is that we need a custom build of Qt for some project. So due to mentioned above we have a separate SVN repo for holding various Qt builds and an external in each Qt project, which refers to one among those builds.</p> <p>The problem is, when using CMake we can only select a version of Qt and the Qt4 finder decides what Qt to use by itself. And that's not the correct one. We need to redirect the finder to configure all stuff for a particular Qt copy in project's third parties directory.</p> <p>I've tried to specify the <code>PATHS</code> option for <code>FIND_PACKAGE</code> like that: <code>FIND_PACKAGE( Qt4 REQUIRED PATHS "thirdparty/Qt" )</code> but that didn't help. I have tried to set the <code>QT_QMAKE_EXECUTABLE</code> variable, but that didn't work. I've tried to add the required QMake's path (it's used by the FindQt4.cmake to determine all directories) to the PATH variable before the installed one, but that didn't help too.</p> <p>Is there a way to use all the stuff which the FIND_PACKAGE provides but for a certain Qt copy? I really don't want to implement all Qt wrappers, set all definitions, includes, dirs, etc manually.</p> <p>Here is my CMake project. Maybe that will help:</p> <pre><code>CMAKE_MINIMUM_REQUIRED( VERSION 2.8 ) ############################################################################# MACRO( ADD_FILES_TO_FILTER rootFilterName rootFilterPath files ) FOREACH( curFile ${files} ) FILE( RELATIVE_PATH curFilter "${CMAKE_CURRENT_SOURCE_DIR}/${rootFilterPath}" "${CMAKE_CURRENT_SOURCE_DIR}/${curFile}" ) FILE( RELATIVE_PATH test "${CMAKE_CURRENT_SOURCE_DIR}" "${CMAKE_CURRENT_SOURCE_DIR}/${curFile}" ) GET_FILENAME_COMPONENT( curFilter ${curFilter} PATH ) SET( curFilter "${rootFilterName}/${curFilter}" ) STRING( REPLACE "/" "\\\\" curFilter ${curFilter} ) SOURCE_GROUP( ${curFilter} FILES ${curFile} ) ENDFOREACH( curFile ) ENDMACRO( ADD_FILES_TO_FILTER rootFilterName rootFilterPath files ) MACRO( TO_RELATIVE_PATHS filePaths ) SET( resPaths "" ) FOREACH( curPath ${${filePaths}} ) FILE( RELATIVE_PATH relPath ${CMAKE_CURRENT_SOURCE_DIR} ${curPath} ) SET( resPaths ${resPaths} ${relPath} ) ENDFOREACH( curPath ) SET( ${filePaths} ${resPaths} ) ENDMACRO( TO_RELATIVE_PATHS filePaths ) ###################################################################### # Define project settings PROJECT( RealTimeCapture ) FIND_PACKAGE( Qt4 REQUIRED PATHS "thirdparty/Qt" ) SET( BOOST_ROOT "thirdparty/boost" ) FIND_PACKAGE( Boost REQUIRED ) # Collect all required files for build FILE( GLOB_RECURSE headers RELATIVE ${CMAKE_CURRENT_SOURCE_DIR} "src/RTCF/include/*.h" ) FILE( GLOB_RECURSE sources RELATIVE ${CMAKE_CURRENT_SOURCE_DIR} "src/RTCF/src/*.cpp" ) FILE( GLOB_RECURSE resources RELATIVE ${CMAKE_CURRENT_SOURCE_DIR} "src/*.qrc" ) FILE( GLOB_RECURSE forms RELATIVE ${CMAKE_CURRENT_SOURCE_DIR} "src/*.ui" ) # Preprocess all Qt files QT4_WRAP_CPP( header_mocs ${headers} ) QT4_WRAP_UI( form_headers ${forms} ) QT4_ADD_RESOURCES( resources_rcc ${resources} ) # Convert all generated files paths to relative ones TO_RELATIVE_PATHS( header_mocs ) TO_RELATIVE_PATHS( form_headers ) TO_RELATIVE_PATHS( resources_rcc ) # Create executable ADD_EXECUTABLE( RealTimeCapture ${headers} ${sources} ${header_mocs} ${form_headers} ${resources_rcc} ) SET_TARGET_PROPERTIES( RealTimeCapture PROPERTIES COMPILE_FLAGS "/Zc:wchar_t-" ) # Set filters for project according to its namespaces FILE( RELATIVE_PATH buildDir ${CMAKE_CURRENT_SOURCE_DIR} ${CMAKE_CURRENT_BINARY_DIR} ) ADD_FILES_TO_FILTER( "Headers" "src/RTCF/include" "${headers}" ) ADD_FILES_TO_FILTER( "Sources" "src/RTCF/src" "${sources}" ) ADD_FILES_TO_FILTER( "Generated" "${buildDir}/src/RTCF/include" "${header_mocs}" ) ADD_FILES_TO_FILTER( "Forms" "${buildDir}/src/RTCF/include" "${form_headers}" ) ADD_FILES_TO_FILTER( "Resources" "${buildDir}" "${resources_rcc}" ) # Set additional include directories INCLUDE_DIRECTORIES( ${CMAKE_CURRENT_BINARY_DIR} ) INCLUDE_DIRECTORIES( "src" ) INCLUDE_DIRECTORIES( "src/RTCF/include" ) INCLUDE_DIRECTORIES( "thirdparty" ) # Configure Qt SET( QT_USE_QTNETWORK TRUE ) SET( QT_USE_QTSQL TRUE ) SET( QT_USE_QTSCRIPT TRUE ) SET( QT_USE_QTXML TRUE ) SET( QT_USE_QTWEBKIT TRUE ) INCLUDE( ${QT_USE_FILE} ) ADD_DEFINITIONS( ${QT_DEFINITIONS} ) TARGET_LINK_LIBRARIES( RealTimeCapture ${QT_LIBRARIES} ) # Add boost support INCLUDE_DIRECTORIES( ${Boost_INCLUDE_DIR} ) TARGET_LINK_LIBRARIES( RealTimeCapture ${Boost_LIBRARIES} ) # Add other libs include dirs INCLUDE_DIRECTORIES( "thirdparty/SimpleCrypt" ) INCLUDE_DIRECTORIES( "thirdparty/id3lib/include" ) INCLUDE_DIRECTORIES( "thirdparty/libtwitcurl" ) INCLUDE_DIRECTORIES( "thirdparty/curl-7.24.0/curl/include" ) INCLUDE_DIRECTORIES( "thirdparty/log4qt/include" ) INCLUDE_DIRECTORIES( "thirdparty/fervor-auto" ) # Add defines ADD_DEFINITIONS( RealTimeCapture -DQUAZIP_STATIC ) ADD_DEFINITIONS( RealTimeCapture -DBUILDING_LIBCURL ) ADD_DEFINITIONS( RealTimeCapture -DID3LIB_LINKOPTION=1 ) ADD_DEFINITIONS( -DUNICODE -D_UNICODE ) #enable unicode support </code></pre> <p><strong>UPDATE</strong></p> <p>As it's mentioned in the comments to the accepted answer, I've managed to set a custom qmake.exe (different from the one added to the OS PATH variable) by setting the <code>QT_QMAKE_EXECUTABLE</code> CMake variable. But the problem was, the qmake executable has hardcoded paths to all Qt's modules. So I have solved it by providing a custom <code>qt.conf</code> file (as it's mentioned in the answer). I haven't found any examples of it in the internet, so here it is, maybe it will help someone:</p> <pre><code>[Paths] Prefix=.. Documentation=doc Headers=include Libraries=lib Binaries=bin Plugins=plugins Imports=imports Data= Translations= Settings= Examples= Demos= </code></pre> <p>I used exactly this. You can consider specifying an absolute path to the Qt install in the prefix though. I just didn't want to use an absolute path in a repo, which can be cloned in an arbitrary location. See <a href="http://doc.qt.digia.com/4.7-snapshot/qt-conf.html">this</a> link about details on using <code>qt.conf</code>.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USRoman Kruglov
    1. USRoman Kruglov
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHow to include a certain Qt installation using CMake?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POHow to include a certain Qt installation using CMake?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POHow to include a certain Qt installation using CMake?
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO"PATHES" -- Isn't the right spelling "PATHS"?
      singulars
      1. POHow to include a certain Qt installation using CMake?
      1. USStefan Majewsky
    2. CO@StefanMajewsky yep, sorry
      singulars
      1. POHow to include a certain Qt installation using CMake?
      1. USRoman Kruglov
    3. COThis is why CMake's find_package command is a total piece of junk. Every FindXXX.cmake module is just some inconsistent mess that has little similarity to any other find module. This ruins the usefulness of CMake. To be a consistent find module, simply make your module completely inconsistent to maintain consistency with other modules.
      singulars
      1. POHow to include a certain Qt installation using CMake?
      1. USdoug65536
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload