QT build from source in windows 10 (shellscalingapi.h not found)
-
@vakh said in QT build from source in windows 10 (shellscalingapi.h not found):
but compiler can not find it. how can i add this directory to compiler include path?
If you use the gcc from C:\Programs\Qt\Tools\mingw1120_64\bin, the directory is part of the compiler default include path. Which gcc are you using (which path shows up if you run "where gcc")?
-
@vakh said in QT build from source in windows 10 (shellscalingapi.h not found):
but compiler can not find it. how can i add this directory to compiler include path?
If you use the gcc from C:\Programs\Qt\Tools\mingw1120_64\bin, the directory is part of the compiler default include path. Which gcc are you using (which path shows up if you run "where gcc")?
-
@kkoehne
It is the output of CMD:Microsoft Windows [Version 10.0.19043.1110] (c) Microsoft Corporation. All rights reserved. Z:\>where gcc C:\Programs\Qt\Tools\mingw1120_64\bin\gcc.exe C:\Programs\Strawberry\c\bin\gcc.exeit seems true.
-
@vakh You are apparently usingf wrong compiler!
Start from scratch: delete build folder, create new one and continue with the build. It should now pick up the correct compiler.@jsulm thanks a lot. after I see your answer, I tested it. the problem solved. but another problem appeared.

is it for little RAM? my system is intel core i5 6500T with 8 GB RAM and 58 GB free space on drive C. (I test this procedure two times and it failed because of low space on memory. then i solve it but now it failed with this error). -
@jsulm thanks a lot. after I see your answer, I tested it. the problem solved. but another problem appeared.

is it for little RAM? my system is intel core i5 6500T with 8 GB RAM and 58 GB free space on drive C. (I test this procedure two times and it failed because of low space on memory. then i solve it but now it failed with this error).@vakh said in QT build from source in windows 10 (shellscalingapi.h not found):
is it for little RAM?
Yes. You can limit the number of parallel compiler processes using make instead of ninja. For example to only use 4 processes do: make -j 4.
-
thanks a lot! QT static compile successfully done :)
now after adding this new qmake.exe to project development kit, I face a new problem. As I said before, doing this steps in ubuntu and macOS solved the need for shared libraries and application works without any problems in other computers (without QT installation). but here after doing all of these steps, application in windows need other libraries like "libgcc_s_seh-1.dll". how can I solve this problem? -
thanks a lot! QT static compile successfully done :)
now after adding this new qmake.exe to project development kit, I face a new problem. As I said before, doing this steps in ubuntu and macOS solved the need for shared libraries and application works without any problems in other computers (without QT installation). but here after doing all of these steps, application in windows need other libraries like "libgcc_s_seh-1.dll". how can I solve this problem?@vakh said in QT build from source in windows 10 (shellscalingapi.h not found):
how can I solve this problem?
Well, you would also have to compile all these libraries as static libraries and rebuild your app...
-
@vakh said in QT build from source in windows 10 (shellscalingapi.h not found):
how can I solve this problem?
Well, you would also have to compile all these libraries as static libraries and rebuild your app...
