nicogodet
commented
1 month ago FYI @m-kuhn
Open nicogodet opened 1 month ago
nicogodet
commented
1 month ago FYI @m-kuhn
danodom-tcb
commented
1 month ago @nicogodet I am having a similar issues, I think that I just downloaded some python packages to get around some of that as, regardless of how I tried to reference the sdk, nothing worked.
The issue now is that I have a built exe that will not run, but... I can move it to the "install" folder and create an env file and it will run.
m-kuhn
commented
1 month ago @nicogodet I am having a similar issues, I think that I just downloaded some python packages to get around some of that as, regardless of how I tried to reference the sdk, nothing worked.
please don't! This is an issue to be solved within the sdk (and working properly with a full vcpkg build without sdk)
danodom-tcb
commented
1 month ago @nicogodet I am having a similar issues, I think that I just downloaded some python packages to get around some of that as, regardless of how I tried to reference the sdk, nothing worked.
please don't! This is an issue to be solved within the sdk (and working properly with a full vcpkg build without sdk)
I will have have to wipe the current system and restart, but I was following the instructions and there were things missing and errors being thrown and I had to find a way around them.
@m-kuhn , I agree this should be a straightforward repeatable build process and I don't mind helping get through these issues. I know you had me run some other cmake commands to turn some options off (QT6, I think).
danodom-tcb
commented
1 month ago @nicogodet @m-kuhn , question... Do you know anyone that has set up a Windows environment from scratch and following the VCPKG instructions in the Install.md file and successfully built and ran the qgis.exe without any issues?
nicogodet
commented
1 month ago @danodom-tcb Currently, no. I report errors when I encounter one and wait/propose a fix/reasonable workaround if I can
danodom-tcb
commented
1 month ago @danodom-tcb Currently, no. I report errors when I encounter one and wait/propose a fix/reasonable workaround if I can
@nicogodet, What's the primary build environment for QGIS?
I am assuming those currently building on Windows has had the environment set up for a while, so probably some of the issues I ran into were related to not having my system set up in the same manner (python, etc.).
nicogodet
commented
1 month ago OSGeo4W is the main build env for windows (.msi are created this way)
VCPKG based build is fairly new and bugfix seem needed to have a working build outside GH CI.
m-kuhn
commented
4 weeks ago @nicogodet I have added a tiny bit of context to the top message (only affects SDK) and removed windows (it's actually the same for macos, even though easier to handle because one can manually edit the shebang in the sipbuild file there, while on windows it's a .exe)
danodom-tcb
commented
4 weeks ago @nicogodet, What's the primary build environment for QGIS?
I am assuming those currently building on Windows has had the environment set up for a while, so probably some of the issues I ran into were related to not having my system set up in the same manner (python, etc.).
@nicogodet , Newly built out Windows server/Windows 11 system with no development tools on it, so starting from scratch. I've tried on both.
m-kuhn
commented
3 weeks ago Fixed for macos/linux in https://github.com/open-vcpkg/python-registry/pull/70
For windows it's a bit harder since sip-build is a .exe (binary), we could either try to fix this in the python packaging/build backend (didn't manage to ...) or add a wrapper .bat file that calls python with a relative path (similar to what's done in the PR above for macos/linux).
What is the bug or the crash?
Build fails when it tries to generate SIP files when using the vcpkg SDK
After a little investigation:
D:\a\QGIS\QGIS\build\vcpkg_installed\x64-windows-release\tools\python3\python.exeis a CI pathIt looks like it affects python only
Steps to reproduce the issue
.
Versions
.
Supported QGIS version
New profile
Additional context
No response