52d64fca66
turns out that just appending builtin-qt.conf isn't a good idea: executable-editing tools (objcopy, prelink, etc.) will happily drop the "attachment". a safe method would be adding a proper section to the executable, but there doesn't appear to be an objcopy equivalent in msvc, and using entirely different methods of embedding the file with different toolchains seems like a rather bad idea. so instead go back to the old method of building qmake with a generated qconfig.cpp. of course, as said file is now created by qmake itself, we have to compile qlibraryinfo.cpp a second time, and link a second qmake executable. Task-number: QTBUG-57803 Change-Id: I9e232693550aa870cec154e49cc06add13017cc2 Reviewed-by: Lars Knoll <lars.knoll@qt.io>
26 lines
545 B
INI
26 lines
545 B
INI
option(host_build)
|
|
TEMPLATE = aux
|
|
|
|
# qmake documentation
|
|
QMAKE_DOCS = $$PWD/doc/qmake.qdocconf
|
|
|
|
# qmake binary
|
|
win32: EXTENSION = .exe
|
|
|
|
!build_pass {
|
|
qmake_exe.target = $$OUT_PWD/qmake$$EXTENSION
|
|
qmake_exe.commands = $(MAKE) binary
|
|
qmake_exe.CONFIG = phony
|
|
QMAKE_EXTRA_TARGETS += qmake_exe
|
|
|
|
QMAKE_DISTCLEAN += qmake$$EXTENSION
|
|
|
|
first.depends += qmake_exe
|
|
QMAKE_EXTRA_TARGETS += first
|
|
}
|
|
|
|
qmake.path = $$[QT_HOST_BINS]
|
|
qmake.files = $$OUT_PWD/qmake$$EXTENSION
|
|
qmake.CONFIG = no_check_exist executable
|
|
INSTALLS += qmake
|