*still* having problems building Qt (static)
-
@B3lette thanks for the direction to the download page.
I do have sh.exe in my path. The procedure I listed above used to work. I decided to re-install Qt from scratch. I'm now doing the submodule update step, which takes a long time, probably because I didn't exclude any submodules (I need to learn how to do that). When it's done, I'll try the configure command again.
Thanks...
-
No problem, I am currently completely studying the same things and thought I could help here ...
See https://wiki.qt.io/Building_Qt_5_from_Git#Getting_the_submodule_source_code for infos on init-repository.
Personally i did --module-subset=essential,-qtdoc because that was what I needed. -
@B3lette oh, I guess that's one of the advantages of using the init-repository script -- you can include/exclude the modules as desired.
I'd be interested to know whether, after you've built a Qt library, whether you can go back and add modules should the need arise. Qt's build system has been known to be a little fussy in the past.
-
UPDATE: after going through the procedure again, but using the init-repository script, the configure failed again, just as noted above. Then I read the fine print:
../qt5/configure
and inferred from it that the configure command must be using its own relative pathnames to find files like direct.h. So I ran from my already-installed Qt instead, and the configure command succeeded. Now, we'll see how the build does.
Progress, anyway...
-
Ok, happy it succeeded !
Qt building is meant to be made shadow : after your checkout and repo init, you should create another directory, cd into it and call configure from it.
See my first post here for a nice batch script doing it : https://forum.qt.io/topic/113984/cross-compilation-from-windows-to-aarch64 -
@B3lette yeah, I'm still not sure if I fully understand all that's going on, but evidently, not only do you have to build into another directory, but you have to use the configure command that exists within the already-built Qt space.
Anyway, the make and make install worked, and I have my static build.
Thanks to everyone who looked and helped.
-
@mzimmers said in *still* having problems building Qt (static):
and inferred from it that the configure command must be using its own relative pathnames to find files like direct.h. So I ran from my already-installed Qt instead, and the configure command succeeded. Now, we'll see how the build does.
exactly what steps did you take to solve this? Thanks
-
- Make sure that PATH includes paths to:
- the toolchain (eg, C:\qt\tools\mingw1120_64\bin)
- a Ninja (eg, C:\Program Files\ninja-win)
-
Create and enter the directory you want for your static build.
-
Use the following configure command:
C:/Qt/6.8.2/Src/configure.bat -prefix c:/qt_static/6.8.2 -static -static-runtime -release -skip qt3d -skip qt5compat -skip qtactiveqt -skip qtcharts -skip qtdatavis3d -skip qtdoc -skip qtgrpc -skip qtinsighttracker -skip qtmultimedia -skip qtgraphs -skip qtcharts -skip qtquick3d -skip qtquick3dphysics -skip qtquicktimeline -skip qtwayland -skip qtwebchannel -skip qtwebengine -skip qtwebview -skip qtcoap -skip qtspeech -redo
(of course, you'll want to select your own "-skip" modules)
4. cmake --build . --parallel- cmake --install .
-
I'm sorry, but it's been too long ago. There have been so many changes in Qt since then, it very well may work now, but my procedure works correctly, so I haven't been motivated to experiment.
In fact, I don't think I'm even using github for my Qt source files any longer, but am obtaining them through the Qt maintenance tool. So, there are alternatives to my method.
