- Forum
- Qt
- Qt Programming
- qmake can’t process project file on windows
-
25th October 2008, 08:18
#1
qmake can’t process project file on windows
Hi
I am experiencing a very strange error: I created a .pro file and a couple of source files on a linux machine, and after generating a Makefile and compiling successfully numerous times, committed them to an SVN repository, and checked out that repository on a windows machine. However, running qmake in the directory with the .pro file gives «Error processing project file: paintingeditor.pro», with no more information. I have tried removing various statements, qmake-ing other .pro files (which worked), changing the name of the directory to paintingeditor, and nothing works — am I missing something totally obvious here? I can’t seem to find any explanation for this problem. Running qmake -Wall prints out something about Operator= (Q_EXT_OBJ) changing previously set values or something like that, but the exact same message was printed with the other, working .pro files.
I am using Qt 4.4.3 on Windows XP Pro. The contents of my .pro file are below.
######################################################################
# Automatically generated by qmake (2.01a) Fri Oct 24 22:10:01 2008
######################################################################
TEMPLATE = app
TARGET =
DEPENDPATH += .
INCLUDEPATH += .
CONFIG += debug
win32 {
CONFIG -= debug
CONFIG += release
}
# Input
FORMS += detailseditor.ui
filechooser.ui
paintingeditor.ui
HEADERS += detailseditor.h
filechooser.h
paintingeditor.h
SOURCES += main.cpp
detailseditor.cpp
filechooser.cpp
paintingeditor.cpp
To copy to clipboard, switch view to plain text mode
-
25th October 2008, 14:00
#2
Re: qmake can’t process project file on windows
weird… I can’t spot any obvious error in this project file so you may try :
- setting a value for the TARGET variable
- changing the line endings of the file (probably not a problem but who knows)
- changing the encoding of the file (same as above)
- regenarating your project using «qmake -project» and then adding statements (and checking after every addition if qmake fails to find the offending statement)
-
25th October 2008, 15:49
#3
Re: qmake can’t process project file on windows
Thanks for the suggestions, I’d tried everything but changing the encoding, however re-generating the file from scratch with qmake -project would cover that as well — no matter what I did, I kept getting the same errors. Very weird, I know.
In case it was some crazy problem with Windows, I also tried again after rebooting (using my original project file and regenerating with -project), which, again, failed. Running qmake -d -d doesn’t seem to show any errors, reading all the default config files (in C:Qt4.4.3) goes fine, the last two messages are: Reading project file «C:pathtopaintingeditor.pro» and «Error processing project file» i.e. the message from the first post.
-
25th October 2008, 15:51
#4
Re: qmake can’t process project file on windows
Good news! I found the problem! There was a single quote in one of the parent directory’s name — renaming that directory did the trick. Now that I think of it, I seem to recall possibly reading about this in the manual. I am a little surprised that I seem to be the only person whose ever had this problem, as multiple Google and forum searches (over different forums) returned absolutely nothing relevent.
Similar Threads
-
Replies: 2
Last Post: 18th August 2008, 15:45
-
Replies: 3
Last Post: 8th July 2008, 20:37
-
Replies: 6
Last Post: 5th May 2008, 21:49
-
Replies: 6
Last Post: 30th January 2008, 07:51
-
Replies: 25
Last Post: 22nd February 2007, 06:57
Bookmarks
Bookmarks
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
- BB code is On
- Smilies are On
- [IMG] code is On
- [VIDEO] code is On
- HTML code is Off
Forum Rules
Digia, Qt and their respective logos are trademarks of Digia Plc in Finland and/or other countries worldwide.
|
|
|
Правила раздела *nix / gcc / Eclipse / Qt / wxWidgets / GTK+
- При создании темы ОБЯЗАТЕЛЬНО указывайте версию тулкита / библиотеки / компилятора.
- Перед тем как задать вопрос, сформулируйте его правильно, чтобы вас могли понять.
- Нарушение Правил может повлечь наказание со стороны модераторов.
Полезные ссылки:
Boost по-русски
Qt по-русски
Создание QT приложения в среде NetBeans
- Подписаться на тему
- Сообщить другу
- Скачать/распечатать тему
|
|
Люди помогите новичку в NetBeans. Проблема вот в чём: хочу создать простейшее QT-приложение в Нетбинсе, но сражу же,при выводе кода, среда ругается и выделяет красными восклицателями строчки: #include <QtGui/QApplication>, QApplication app(argc, argv); ЗЫ. В PATH я прописал путь к QT. Добавлено 23.09.09, 16:16 |
_lcf_ |
|
Русские буквы в путях — не айс |
alienrom |
|
Цитата Русские буквы в путях — не айс Да дело не в пути проета, а в qmake, как я понял |
andyag |
|
Цитата alienrom @ 23.09.09, 15:58 красные восклицатели Это настраивается отдельно от проекта. В настройках самого нетбинса для C++. Там пути к инклюдам. Тебе нужно добавить путь к инклюдам Qt. |
Radagast |
|
alienrom |
alienrom |
|
Цитата красные восклицатели Это настраивается отдельно от проекта. В настройках самого нетбинса для C++. Там пути к инклюдам. Тебе нужно добавить путь к инклюдам Qt. В настройках самого проекта я подключил все инклуды,какие только нашёл в QT. Цитата qmake не любит ни русские буквы, ни пробелы в путях ни проект, ни QT не расположены в путях с русскими буквами и пробелами |
Леголегс |
|
Full Member Рейтинг (т): 21 |
Цитата alienrom @ 24.09.09, 11:09 ни проект, ни QT не расположены в путях с русскими буквами и пробелами O RLY? Цитата alienrom @ 23.09.09, 15:58 make[1]: Entering directory `/c/Documents and Settings/support/Мои документы/NetBeansProjects/QtApplication_1′ |
alienrom |
|
Цитата make[1]: Entering directory `/c/Documents and Settings/support/Мои документы/NetBeansProjects/QtApplication_1′ Сразу после этого сообщения создал другой проект в корне С. Аналогично. |
Леголегс |
|
Full Member Рейтинг (т): 21 |
Цитата alienrom @ 23.09.09, 15:58 ЗЫ. В PATH я прописал путь к QT. В какой PATH? общесистемный? А руками в консоли qmake вызывается нормально? |
Benzin |
|
Добрый вечер, возникла такая же проблема как и у автора, последовал совету выше, добавил инклуды, восклицательные знаки исчезли, но все равно ошибки остались.
/bin/make -f nbproject/Makefile-Debug.mk SUBPROJECTS= .build-conf make[1]: Entering directory `/c/Test/QtApplication_1′ qmake VPATH=. -o qttmp-Debug.mk nbproject/qt-Debug.pro QMAKESPEC has not been set, so configuration cannot be deduced. Error processing project file: nbproject/qt-Debug.pro make[1]: *** [nbproject/qt-Debug.mk] Error 3 make[1]: Leaving directory `/c/Test/QtApplication_1′ make: *** [.build-impl] Error 2 BUILD FAILED (exit value 2, total time: 1s) пошел на поиски проблемы, выяснил, что нужно задать QMAKESPEC для своего компилятора, у меня установлен MinGW, нашел тут http://qtwin.sourceforge.net/qt3-win32/compile-mingw.php , что нужно прописать так set QMAKESPEC=win32-g++ , но это если вручную компилировать, осюда вопрос: где мне вписать эту строку, если у меня Windows и MinGW уже установлен в папку C:MinGW ? p.s. с qt еще никогда дела не имел Сообщение отредактировано: Benzin — 03.10.09, 16:38 |
Benzin |
|
Проблему решил переустановкой всего, просто надо внимательнее быть =) Для тех у кого возникнет такая же проблема: Сообщение отредактировано: Benzin — 03.10.09, 18:02 |
Алиса в Стране Чудес |
|
В Win7 не работает по этой (и другим кстати) инструкциям. Со всеми версиями компилятора minGW… Ошибка все таже, что и в первом посте. Ссылка на эту тему замечательно гуглится. Если у кого-то заработает в Win7 пожалуйста отпишитесь (желательно по пунктам). Добавлено 04.01.10, 19:58 |
niXman |
|
у меня работает. как и всегда. ни в одной версии вендавз + нетбинс не было никогда проблем. так что даже и не знаю что подсказать. |
Алиса в Стране Чудес |
|
Джава проекты и сам нетбинс работают.
/bin/make -f nbproject/Makefile-Debug.mk SUBPROJECTS= .build-conf make[1]: Entering directory `/c/NetBeansProjects/HelloQtWorld_1′ /C/Qt/2009.05/qt/qmake/qmake.exe VPATH=. -o qttmp-Debug.mk nbproject/qt-Debug.pro QMAKESPEC has not been set, so configuration cannot be deduced. Error processing project file: nbproject/qt-Debug.pro make[1]: *** [nbproject/qt-Debug.mk] Error 3 make[1]: Leaving directory `/c/NetBeansProjects/HelloQtWorld_1′ make: *** [.build-impl] Error 2 BUILD FAILED (exit value 2, total time: 3s) Сейчас поставила QtCreator, т.к. работает. Сообщение отредактировано: Алиса в Стране Чудес — 08.01.10, 11:27 |
sfinae |
|
Member Рейтинг (т): 8 |
Цитата Алиса в Стране Чудес @ 05.01.10, 08:21 Сейчас поставила QtCreator, т.к. оно работает. Для того чтобы люди не мучились специально сделано Qt SDK, сразу с MinGW, собранным им Qt и Qt Creator, настроенным на правильные пусти и утилиты. |
0 пользователей читают эту тему (0 гостей и 0 скрытых пользователей)
0 пользователей:
- Предыдущая тема
- Кроссплатформенный C/C++: cl/gcc/Qt/Gtk+/WxWidgets
- Следующая тема
[ Script execution time: 0,0512 ] [ 16 queries used ] [ Generated: 10.02.23, 01:22 GMT ]
Comments
Describe the bug
A clear and concise description of what the bug is.
Environment
- OS: win10
- Compiler: visual studio 2019
`
F:helloqt>»F:vcpkginstalledx86-windowstoolsqt5debugbinqmake.exe» -tp quit.pro
WARNING: Unable to generate output for: F:/helloqt/Makefile.Debug [TEMPLATE quit.proapp]
QIODevice::write: device not open
WARNING: Unable to generate output for: F:/helloqt/Makefile.Release [TEMPLATE quit.proapp]
QIODevice::write: device not open
F:helloqt>»F:vcpkginstalledx86-windowstoolsqt5binqmake.exe» -tp quit.pro
Could not find qmake spec ‘win32-msvc’.
Error processing project file: F:helloqtquit.pro
F:helloqt>»F:vcpkginstalledx86-windowstoolsqt5-basebinqmake.exe» -tp quit.pro
Could not find qmake spec ‘win32-msvc’.
Error processing project file: F:helloqtquit.pro
`
What is the output of qmake -query
?
You might need to add -qtconf qt.conf
with a qt.conf containing the correct paths to the archdatadir.
after investigating:
I think your are using qmake wrong:
"F:vcpkginstalledx86-windowstoolsqt5debugbinqmake.exe" -tp quit.pro
why do you use the -tp switch? the help says:
-tp prefix | Overrides TEMPLATE so that prefix is prefixed into the value
so you are missing a argument and probably want to do:
"F:vcpkginstalledx86-windowstoolsqt5debugbinqmake.exe" quit.pro
without the -tp switch
oh, sorry
i omitted ‘vc’ after -tp
duyanning@EDU-NOTEBOOK F:helloqt
$ «F:vcpkginstalledx86-windowstoolsqt5binqmake.exe» -tp vc quit.pro
Could not find qmake spec ‘win32-msvc’.
Error processing project file: quit.pro
duyanning@EDU-NOTEBOOK F:helloqt
$ «F:vcpkginstalledx86-windowstoolsqt5debugbinqmake.exe» -tp vc quit.pro
duyanning@EDU-NOTEBOOK F:helloqt
$ «F:vcpkginstalledx86-windowstoolsqt5-basebinqmake.exe» -tp vc quit.pro
Could not find qmake spec ‘win32-msvc’.
Error processing project file: quit.pro
It seems qmake can’t find qmake spec, after installed qt-base, it installed mkspec to shareqt5 folder which contains qmake.conf.
Reference find_qt_mkspec.cmake
I still need:
Output of qmake -query
?
If you renamed/moved vcpkg after build the hardcoded paths in qmake are all wrong and you need to use a qt.conf. That is why I need to see the output of qmake -query
I am also not able to reproduce your failure locally.
@PhoebeHui
Reference find_qt_mkspec.cmake
has nothing to do with the problem.
duyanning@EDU-NOTEBOOK C:UsersduyanningDesktop
$ «C:Program Files (x86)Microsoft Visual Studio2019CommunityVCAuxiliaryBuildvcvars32.bat»
** Visual Studio 2019 Developer Command Prompt v16.2.0
** Copyright (c) 2019 Microsoft Corporation
[vcvarsall.bat] Environment initialized for: ‘x86’
duyanning@EDU-NOTEBOOK C:UsersduyanningDesktop
$ «F:vcpkginstalledx86-windowstoolsqt5-basebinqmake.exe» -query
QT_SYSROOT:
QT_INSTALL_PREFIX:F:/vcpkg/installed/x86-windows/tools/qt5-base/bin
QT_INSTALL_ARCHDATA:F:/vcpkg/installed/x86-windows/tools/qt5-base/bin
QT_INSTALL_DATA:F:/vcpkg/installed/x86-windows/tools/qt5-base/bin
QT_INSTALL_DOCS:F:/vcpkg/installed/x86-windows/tools/qt5-base/bin/doc
QT_INSTALL_HEADERS:F:/vcpkg/installed/x86-windows/tools/qt5-base/bin/include
QT_INSTALL_LIBS:F:/vcpkg/installed/x86-windows/tools/qt5-base/bin/lib
QT_INSTALL_LIBEXECS:F:/vcpkg/installed/x86-windows/tools/qt5-base/bin/bin
QT_INSTALL_BINS:F:/vcpkg/installed/x86-windows/tools/qt5-base/bin/bin
QT_INSTALL_TESTS:F:/vcpkg/installed/x86-windows/tools/qt5-base/bin/tests
QT_INSTALL_PLUGINS:F:/vcpkg/installed/x86-windows/tools/qt5-base/bin/plugins
QT_INSTALL_IMPORTS:F:/vcpkg/installed/x86-windows/tools/qt5-base/bin/imports
QT_INSTALL_QML:F:/vcpkg/installed/x86-windows/tools/qt5-base/bin/qml
QT_INSTALL_TRANSLATIONS:F:/vcpkg/installed/x86-windows/tools/qt5-base/bin/translations
QT_INSTALL_CONFIGURATION:
QT_INSTALL_EXAMPLES:F:/vcpkg/installed/x86-windows/tools/qt5-base/bin/examples
QT_INSTALL_DEMOS:F:/vcpkg/installed/x86-windows/tools/qt5-base/bin/examples
QT_HOST_PREFIX:F:/vcpkg/installed/x86-windows/tools/qt5-base/bin
QT_HOST_DATA:F:/vcpkg/installed/x86-windows/tools/qt5-base/bin
QT_HOST_BINS:F:/vcpkg/installed/x86-windows/tools/qt5-base/bin/bin
QT_HOST_LIBS:F:/vcpkg/installed/x86-windows/tools/qt5-base/bin/lib
QMAKE_SPEC:win32-msvc
QMAKE_XSPEC:win32-msvc
QMAKE_VERSION:3.1
QT_VERSION:5.12.4
duyanning@EDU-NOTEBOOK C:UsersduyanningDesktop
$ «F:vcpkginstalledx86-windowstoolsqt5binqmake.exe» -query
QT_SYSROOT:
QT_INSTALL_PREFIX:F:/vcpkg/installed/x86-windows/tools/qt5/bin
QT_INSTALL_ARCHDATA:F:/vcpkg/installed/x86-windows/tools/qt5/bin
QT_INSTALL_DATA:F:/vcpkg/installed/x86-windows/tools/qt5/bin
QT_INSTALL_DOCS:F:/vcpkg/installed/x86-windows/tools/qt5/bin/doc
QT_INSTALL_HEADERS:F:/vcpkg/installed/x86-windows/tools/qt5/bin/include
QT_INSTALL_LIBS:F:/vcpkg/installed/x86-windows/tools/qt5/bin/lib
QT_INSTALL_LIBEXECS:F:/vcpkg/installed/x86-windows/tools/qt5/bin/bin
QT_INSTALL_BINS:F:/vcpkg/installed/x86-windows/tools/qt5/bin/bin
QT_INSTALL_TESTS:F:/vcpkg/installed/x86-windows/tools/qt5/bin/tests
QT_INSTALL_PLUGINS:F:/vcpkg/installed/x86-windows/tools/qt5/bin/plugins
QT_INSTALL_IMPORTS:F:/vcpkg/installed/x86-windows/tools/qt5/bin/imports
QT_INSTALL_QML:F:/vcpkg/installed/x86-windows/tools/qt5/bin/qml
QT_INSTALL_TRANSLATIONS:F:/vcpkg/installed/x86-windows/tools/qt5/bin/translations
QT_INSTALL_CONFIGURATION:
QT_INSTALL_EXAMPLES:F:/vcpkg/installed/x86-windows/tools/qt5/bin/examples
QT_INSTALL_DEMOS:F:/vcpkg/installed/x86-windows/tools/qt5/bin/examples
QT_HOST_PREFIX:F:/vcpkg/installed/x86-windows/tools/qt5/bin
QT_HOST_DATA:F:/vcpkg/installed/x86-windows/tools/qt5/bin
QT_HOST_BINS:F:/vcpkg/installed/x86-windows/tools/qt5/bin/bin
QT_HOST_LIBS:F:/vcpkg/installed/x86-windows/tools/qt5/bin/lib
QMAKE_SPEC:win32-msvc
QMAKE_XSPEC:win32-msvc
QMAKE_VERSION:3.1
QT_VERSION:5.12.4
duyanning@EDU-NOTEBOOK C:UsersduyanningDesktop
$ «F:vcpkginstalledx86-windowstoolsqt5debugbinqmake.exe» -query
QT_SYSROOT:
QT_INSTALL_PREFIX:F:/vcpkg/installed/x86-windows
QT_INSTALL_ARCHDATA:F:/vcpkg/installed/x86-windows/tools/qt5/debug
QT_INSTALL_DATA:F:/vcpkg/installed/x86-windows/share/qt5/debug
QT_INSTALL_DOCS:F:/vcpkg/installed/x86-windows/share/qt5/debug/doc
QT_INSTALL_HEADERS:F:/vcpkg/installed/x86-windows/include
QT_INSTALL_LIBS:F:/vcpkg/installed/x86-windows/debug/lib
QT_INSTALL_LIBEXECS:F:/vcpkg/installed/x86-windows/tools/qt5/debug
QT_INSTALL_BINS:F:/vcpkg/installed/x86-windows/debug/bin
QT_INSTALL_TESTS:F:/vcpkg/installed/x86-windows/tests
QT_INSTALL_PLUGINS:F:/vcpkg/installed/x86-windows/debug/plugins
QT_INSTALL_IMPORTS:F:/vcpkg/installed/x86-windows/tools/qt5/debug/imports
QT_INSTALL_QML:F:/vcpkg/installed/x86-windows/debug/qml
QT_INSTALL_TRANSLATIONS:F:/vcpkg/installed/x86-windows/share/qt5/debug/translations
QT_INSTALL_CONFIGURATION:
QT_INSTALL_EXAMPLES:F:/vcpkg/installed/x86-windows/share/qt5/debug/examples
QT_INSTALL_DEMOS:F:/vcpkg/installed/x86-windows/share/qt5/debug/examples
QT_HOST_PREFIX:F:/vcpkg/installed/x86-windows/tools/qt5/debug
QT_HOST_DATA:F:/vcpkg/installed/x86-windows/tools/qt5/debug
QT_HOST_BINS:F:/vcpkg/installed/x86-windows/tools/qt5/debug/bin
QT_HOST_LIBS:F:/vcpkg/installed/x86-windows/tools/qt5/debug/lib
QMAKE_SPEC:win32-msvc
QMAKE_XSPEC:win32-msvc
QMAKE_VERSION:3.1
QT_VERSION:5.12.4
i use ConEmu
As a workaround use either x64-windows-static
or a qt.conf
file. Qt seems to do something strange with the hardcoded paths in some triplets.
The paths should look like:
$ ./qmake.exe -query QT_SYSROOT:
QT_INSTALL_PREFIX:G:/vcpkg_test/qt_5.12.4/installed/x64-windows-static
QT_INSTALL_ARCHDATA:G:/vcpkg_test/qt_5.12.4/installed/x64-windows-static/tools/qt5
QT_INSTALL_DATA:G:/vcpkg_test/qt_5.12.4/installed/x64-windows-static/share/qt5
QT_INSTALL_DOCS:G:/vcpkg_test/qt_5.12.4/installed/x64-windows-static/share/qt5/doc
QT_INSTALL_HEADERS:G:/vcpkg_test/qt_5.12.4/installed/x64-windows-static/include
QT_INSTALL_LIBS:G:/vcpkg_test/qt_5.12.4/installed/x64-windows-static/lib
QT_INSTALL_LIBEXECS:G:/vcpkg_test/qt_5.12.4/installed/x64-windows-static/tools/qt5
QT_INSTALL_BINS:G:/vcpkg_test/qt_5.12.4/installed/x64-windows-static/bin
QT_INSTALL_TESTS:G:/vcpkg_test/qt_5.12.4/installed/x64-windows-static/tests
QT_INSTALL_PLUGINS:G:/vcpkg_test/qt_5.12.4/installed/x64-windows-static/plugins
QT_INSTALL_IMPORTS:G:/vcpkg_test/qt_5.12.4/installed/x64-windows-static/tools/qt5/imports
QT_INSTALL_QML:G:/vcpkg_test/qt_5.12.4/installed/x64-windows-static/qml
QT_INSTALL_TRANSLATIONS:G:/vcpkg_test/qt_5.12.4/installed/x64-windows-static/share/qt5/translations
QT_INSTALL_CONFIGURATION:
QT_INSTALL_EXAMPLES:G:/vcpkg_test/qt_5.12.4/installed/x64-windows-static/share/qt5/examples
QT_INSTALL_DEMOS:G:/vcpkg_test/qt_5.12.4/installed/x64-windows-static/share/qt5/examples
QT_HOST_PREFIX:G:/vcpkg_test/qt_5.12.4/installed/x64-windows-static/tools/qt5
QT_HOST_DATA:G:/vcpkg_test/qt_5.12.4/installed/x64-windows-static/tools/qt5
QT_HOST_BINS:G:/vcpkg_test/qt_5.12.4/installed/x64-windows-static/tools/qt5/bin
QT_HOST_LIBS:G:/vcpkg_test/qt_5.12.4/installed/x64-windows-static/tools/qt5/lib
QMAKE_SPEC:win32-msvc
QMAKE_XSPEC:win32-msvc
QMAKE_VERSION:3.1
QT_VERSION:5.12.5
I could confirm the strange qt paths with another version of qt (build from git bash; maybe that is one problem?):
$ ./qmake.exe -query QT_SYSROOT:
QT_INSTALL_PREFIX:G:/vcpkg_test/qt_5.12.4/installed/x86-windows/tools/qt5/bin
QT_INSTALL_ARCHDATA:G:/vcpkg_test/qt_5.12.4/installed/x86-windows/tools/qt5/bin
QT_INSTALL_DATA:G:/vcpkg_test/qt_5.12.4/installed/x86-windows/tools/qt5/bin
QT_INSTALL_DOCS:G:/vcpkg_test/qt_5.12.4/installed/x86-windows/tools/qt5/bin/doc
QT_INSTALL_HEADERS:G:/vcpkg_test/qt_5.12.4/installed/x86-windows/tools/qt5/bin/include
QT_INSTALL_LIBS:G:/vcpkg_test/qt_5.12.4/installed/x86-windows/tools/qt5/bin/lib
QT_INSTALL_LIBEXECS:G:/vcpkg_test/qt_5.12.4/installed/x86-windows/tools/qt5/bin/bin
QT_INSTALL_BINS:G:/vcpkg_test/qt_5.12.4/installed/x86-windows/tools/qt5/bin/bin
QT_INSTALL_TESTS:G:/vcpkg_test/qt_5.12.4/installed/x86-windows/tools/qt5/bin/tests
QT_INSTALL_PLUGINS:G:/vcpkg_test/qt_5.12.4/installed/x86-windows/tools/qt5/bin/plugins
QT_INSTALL_IMPORTS:G:/vcpkg_test/qt_5.12.4/installed/x86-windows/tools/qt5/bin/imports
QT_INSTALL_QML:G:/vcpkg_test/qt_5.12.4/installed/x86-windows/tools/qt5/bin/qml
QT_INSTALL_TRANSLATIONS:G:/vcpkg_test/qt_5.12.4/installed/x86-windows/tools/qt5/bin/translations
QT_INSTALL_CONFIGURATION:
QT_INSTALL_EXAMPLES:G:/vcpkg_test/qt_5.12.4/installed/x86-windows/tools/qt5/bin/examples
QT_INSTALL_DEMOS:G:/vcpkg_test/qt_5.12.4/installed/x86-windows/tools/qt5/bin/examples
QT_HOST_PREFIX:G:/vcpkg_test/qt_5.12.4/installed/x86-windows/tools/qt5/bin
QT_HOST_DATA:G:/vcpkg_test/qt_5.12.4/installed/x86-windows/tools/qt5/bin
QT_HOST_BINS:G:/vcpkg_test/qt_5.12.4/installed/x86-windows/tools/qt5/bin/bin
QT_HOST_LIBS:G:/vcpkg_test/qt_5.12.4/installed/x86-windows/tools/qt5/bin/lib
QMAKE_SPEC:win32-msvc
QMAKE_XSPEC:win32-msvc
QMAKE_VERSION:3.1
QT_VERSION:5.13.1
If you need an example for a qt.conf
there is qt_debug.conf
and qt_release.conf
in tools/qt5
. just replace ${CURRENT_INSTALLED_DIR}
with F:vcpkginstalledx86-windows
in your case
From my point of view this looks like a Qt issue since we actually passed all the paths correctly.
A another thing i just saw is that your debug build of qmake actually works as expected.
So it probably happens when the paths are similar to qt5 default installation paths?
The same problem here.
With vcpkg Qt 5.12.5 update, qmake.exe
in the debug directory(%VCPKG_ROOT%installedx64-windowstoolsqt5debugbin
) works fine, but in the default release directory(%VCPKG_ROOT%vcpkginstalledx64-windowstoolsqt5bin
), it’s not working due to wrong paths.
Default(Wrong paths):
Debug(Correct paths):
Envrionment:
OS: Win10 1903
MSVC: 2019 16.2.5
Triplet: x64-windows
Qt: 5.12.5
@Neumann-A
After some investigation, I found the culprit is the nearly empty qt.conf
file installed in %VCPKG_ROOT%vcpkginstalledx64-windowstoolsqt5bin
.
Here the detail:
In %VCPKG_ROOT%buildtreesqt5-basex64-windows-relqmake
directory, here is a file named qmake.exe
with md5 value 6fbecce7bf911b5ec7630ef925a4cb22
and correct paths output when executing qmake.exe -query
:
In %VCPKG_ROOT%installedx64-windowstoolsqt5bin
directory, here is the qmake.exe
file with the exactly same md5 value 6fbecce7bf911b5ec7630ef925a4cb22
but wrong paths output when executing qmake.exe -query
:
Obviously, the problem is nothing to do with the qmake.exe
hardcoded paths, then I found there is a qt.conf
file in %VCPKG_ROOT%installedx64-windowstoolsqt5bin
directory:
And it’s content:
Finally, remove the file or rename it to anything else solved the problem:
@spindensity. Ah this explains why I don’t have the error in x64-windows-static because that file does not exists. It is still qt’s fault since it is installing that file not vcpkg.
The behavior is also unexpected since an empty qt.conf should not override any paths…
but thats means it is easy to fix
Neumann-A
added a commit
to Neumann-A/vcpkg
that referenced
this issue
Sep 17, 2019
Rastaban
pushed a commit
that referenced
this issue
Sep 20, 2019
* forward extra arguments to vcpkg_configure_qmake from submodules
* make image format dependent on tiff and libwebp
* make tools dependent on imageformat
* build options must be passed a bit different then normal qmake options
* add the required dependencies
* a new dependency discovered in qt5-declarative
* need webpdemux also
* qt5-declarative is dependent on imageformats so we can drop it here
* remove empty qt.conf if it exists. closes #8180
* add all recommended dependencies as dependencies in control.
Автор | Тема: установка драйвера mysql для QT на linux (Прочитано 15893 раз) |
|
||||||
|
||||||
|
||||||
|
||||||
|
||||||
|
||||||
|
||||||
|
||||||
|
||||||
|
||||||
|
||||||
|
||||||
|
||||||
|
||||||
|
||||||