Windows 11, Visual Studio build, QGIS.exe built, but will not run #59249

danodom-tcb · 2024-10-28T15:18:55Z

What is the bug or the crash?

I have successfully built QGIS.exe with Visual Studio with some great assistance from @m-kuhn (thank you). However, I cannot get the .exe to run in Windows from the bin folder. QGIS goes to startup, and I can see something like "Starting Python" and then the window just goes away..

Also, I can take the built .exe and put it in the "QGIS Install Folder from the Installer", create an .env file in the bin folder, and it works. So, the executable is good, but there appears to be a few things missing. I am betting it needs the .env file, which I started, but there appears to be gaps in what's in the install folder vs what's in the SDK or some things might be the same, but referenced by a different name. .

I am running Windows 11, with Visual Studio 2022, SDK(vcpkg-export-20241015-154141).

Steps to reproduce the issue

see above.

Versions

Close to latest version of source, post install.md update referencing the SDK

Supported QGIS version

I'm running a supported QGIS version according to the roadmap.

New profile

I tried with a new QGIS profile

Additional context

No response

nicogodet · 2024-10-28T15:49:26Z

I looked at your other issues and, in my opinion, your build environment is kind a mess 😄
And it makes it very difficult to debug...

You should proceed step by step. If you encounter an error, report it (make sure this is a real issue, double check your cmake command, etc...)

danodom-tcb · 2024-10-28T15:51:54Z

I looked at your other issues and, in my opinion, your build environment is kind a mess 😄 And it makes it very difficult to debug...

You should proceed step by step. If you encounter an error, report it (make sure this is a real issue, double check your cmake command, etc...)

@nicogodet It was initially a clean system following the build instructions but I've had to add things that were missing to get past build issues as there are gaps in the documentation. Literally, this was a completely clean system before I started and I started with the install.md instructions but those did not work. I finally have a build and @m-kuhn has been helping get through some issues.

nicogodet · 2024-10-29T08:54:11Z

It was initially a clean system following the build instructions but I've had to add things that were missing to get past build issues

This is wrong. I try to build locally too and I assumed that Install.md is perfect and everything is correct. I just followed the steps and reported errors when I found some :

I believe this is the correct way to proceed instead of locally install missing things...

nicogodet · 2024-10-29T08:55:46Z

Currently, with fixes, I can follow Install.md steps without errors when building dependencies locally (I expect bigobj to raise an error soon)

nicogodet · 2024-10-29T12:58:03Z

Successful build fix bigobj workaround (waiting for automoc)
Need to figure out .env file now...

danodom-tcb · 2024-10-29T15:20:17Z

>I believe this is the correct way to proceed instead of locally install missing things...

@nicogodet , I agree with you here and have a thread open working with m-kuhn as we go along. Please keep in mind that I am primarily a windows guy, and not really familiar with python, but coming up to speed.. So, there was a lot of things I was learning and picking up on the fly. I did follow the instructions, and even added missing parameters to the cmake for the missing flex and bison parameters that in the command, so intentions were good, I just didn't know what I didn't know. So, after the build worked, do you think it's basically the missing .env file causing most of the issues with it not being able to run? That's my thought, but I am not 100% sure I can align everything in the installed environment file vs. what's in the sdk. That, I'll need some help with and some guidance. Also, my plan is going to go back from square one and see if I can get a repeatable build and run process, that's the goal. Please let me know about what you find with getting the built .exe to run.

…

________________________________ From: Nicolas Godet ***@***.***> Sent: Tuesday, October 29, 2024 12:58 PM To: qgis/QGIS ***@***.***> Cc: danodom-tcb ***@***.***>; Author ***@***.***> Subject: Re: [qgis/QGIS] Windows 11, Visual Studio build, QGIS.exe built, but will not run (Issue #59249) Successful build fix bigobj workaround (waiting for automoc) Need to figure out .env file now... — Reply to this email directly, view it on GitHub<#59249 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BMHU5DYNKESRA4HZCX4XIJTZ56A7FAVCNFSM6AAAAABQXVPRK6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBUGE2DKMBWGA>. You are receiving this because you authored the thread.Message ID: ***@***.***>

danodom-tcb · 2024-10-29T15:26:44Z

@nicogodet , Also, could provide me with what all needs to be installed, currently the instructions say Visual Studio 2022 and then the SDK and basically that's it. What else needs to be installed as I am going to be working on getting a clean system to use for starting this from scratch again? From the outside looking in, the install.md can be a tad confusing on what's required based on which method you are using.

________________________________ From: Daniel Odom ***@***.***> Sent: Tuesday, October 29, 2024 3:20 PM To: qgis/QGIS ***@***.***>; qgis/QGIS ***@***.***> Cc: Author ***@***.***>

Subject: Re: [qgis/QGIS] Windows 11, Visual Studio build, QGIS.exe built, but will not run (Issue #59249) >I believe this is the correct way to proceed instead of locally install missing things...

I agree with you here and have a thread open working with m-kuhn as we go along. Please keep in mind that I am primarily a windows guy, and not really familiar with python, but coming up to speed.. So, there was a lot of things I was learning and picking up on the fly. I did follow the instructions, and even added missing parameters to the cmake for the missing flex and bison parameters that in the command, so intentions were good, I just didn't know what I didn't know. So, after the build worked, do you think it's basically the missing .env file causing most of the issues with it not being able to run? That's my thought, but I am not 100% sure I can align everything in the installed environment file vs. what's in the sdk. That, I'll need some help with and some guidance. Also, my plan is going to go back from square one and see if I can get a repeatable build and run process, that's the goal. Please let me know about what you find with getting the built .exe to run.

…

________________________________ From: Nicolas Godet ***@***.***> Sent: Tuesday, October 29, 2024 12:58 PM To: qgis/QGIS ***@***.***> Cc: danodom-tcb ***@***.***>; Author ***@***.***> Subject: Re: [qgis/QGIS] Windows 11, Visual Studio build, QGIS.exe built, but will not run (Issue #59249) Successful build fix bigobj workaround (waiting for automoc) Need to figure out .env file now... — Reply to this email directly, view it on GitHub<#59249 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BMHU5DYNKESRA4HZCX4XIJTZ56A7FAVCNFSM6AAAAABQXVPRK6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBUGE2DKMBWGA>. You are receiving this because you authored the thread.Message ID: ***@***.***>

nicogodet · 2024-10-30T07:51:18Z

(side note: Best would be to answer on github directly instead of email which tends to break message format)

Also, could provide me with what all needs to be installed, currently the instructions say Visual Studio 2022 and then the SDK and basically that's it.

What else needs to be installed as I am going to be working on getting a clean system to use for starting this from scratch again?

You only need visual studio and you need to compile dependencies yourself as SDK is broken (see #59231).

Cmake command looks like:

cmake -S . `
	  -B build `
	  -D WITH_VCPKG=ON `
	  -D BUILD_WITH_QT6=ON `
	  -D WITH_QTWEBKIT=OFF `
	  -D VCPKG_TARGET_TRIPLET=x64-windows-release `
	  -D VCPKG_HOST_TRIPLET=x64-windows-release `
	  -D CMAKE_BUILD_TYPE=RelWithDebInfo `
	  -D WITH_DESKTOP=ON `
	  -D WITH_3D=ON `
	  -D WITH_BINDINGS=ON `
	  -D ENABLE_TESTS=OFF `
	  -D USE_CCACHE=ON `
	  -D CMAKE_C_COMPILER_LAUNCHER="C:\ccache\ccache.exe" `
	  -D CMAKE_CXX_COMPILER_LAUNCHER="C:\ccache\ccache.exe" `
	  -D VCPKG_INSTALL_OPTIONS="--x-buildtrees-root=C:\vcpkg\src" `
	  -D FLEX_EXECUTABLE="C:\Flex_bison\win_flex.exe" `
	  -D BISON_EXECUTABLE="C:\Flex_bison\win_bison.exe" `
	  -D CREATE_ZIP=ON

nicogodet · 2024-10-30T10:36:49Z

@m-kuhn I'm able to confirm a successful build on windows with below steps:

Install VS2022

 cmake -S . `
       -B build `
       -G Ninja `
       -D WITH_VCPKG=ON `
       -D BUILD_WITH_QT6=ON `
       -D WITH_QTWEBKIT=OFF `
       -D VCPKG_TARGET_TRIPLET=x64-windows-release `
       -D VCPKG_HOST_TRIPLET=x64-windows-release `
       -D CMAKE_BUILD_TYPE=RelWithDebInfo `
       -D WITH_DESKTOP=ON `
       -D WITH_3D=ON `
       -D WITH_BINDINGS=ON `
       -D ENABLE_TESTS=OFF `
       -D USE_CCACHE=ON `
       -D CMAKE_C_COMPILER_LAUNCHER="C:\ccache\ccache.exe" `
       -D CMAKE_CXX_COMPILER_LAUNCHER="C:\ccache\ccache.exe" `
       -D VCPKG_INSTALL_OPTIONS="--x-buildtrees-root=C:\vcpkg\src" `
       -D FLEX_EXECUTABLE="C:\Flex_bison\win_flex.exe" `
       -D BISON_EXECUTABLE="C:\Flex_bison\win_bison.exe" `
       -D CREATE_ZIP=ON `
       -D CMAKE_INSTALL_PREFIX="D:\Qgis_local"

Use CREATE_ZIP=ON to simplify the qgis execution later (my own choice)
Specify CMAKE_INSTALL_PREFIX to avoid error later

 cmake --build build --config RelWithDebInfo --parallel

 cmake --build build --config RelWithDebInfo --target bundle

Execute .\build\_CPack_Packages\win64\ZIP\qgis-3.39.0-win64\bin\qgis.exe

m-kuhn · 2024-10-30T12:29:46Z

🎉

Specify CMAKE_INSTALL_PREFIX to avoid error later

where did that come from?

nicogodet · 2024-10-30T12:36:51Z

#59267

CMake tries to install icons in default install dir (C:/Program Files (x86)) without admin rights

danodom-tcb · 2024-10-30T14:56:01Z

@nicogodet @m-kuhn , so I don't need to install python or anything else, only Visual Studio 2022?

danodom-tcb · 2024-10-30T14:58:12Z

@nicogodet @m-kuhn and do not build from within VS 2022 (debug or release)?

m-kuhn · 2024-10-30T15:02:24Z

@nicogodet @m-kuhn , so I don't need to install python or anything else, only Visual Studio 2022?

and flex and bison

@nicogodet @m-kuhn and do not build from within VS 2022 (debug or release)?

I would avoid doing so in a first step (just to avoid problems); but it should also work

danodom-tcb · 2024-10-30T15:07:53Z

and flex and bison

Assume the link to winflexbison in the install.md is appropriate for these?

nicogodet · 2024-10-30T15:18:29Z

Assume the link to winflexbison in the install.md is appropriate for these?

Yes

danodom-tcb · 2024-10-30T15:29:21Z

@nicogodet is this the root path to the QGIS source code?

-D VCPKG_INSTALL_OPTIONS="--x-buildtrees-root=C:\vcpkg\src" `

nicogodet · 2024-10-30T15:33:38Z

No.

My QGIS src are in D:\QGIS_src and all commands from #59249 (comment) are executed within this folder.

-D VCPKG_INSTALL_OPTIONS="--x-buildtrees-root=C:\vcpkg\src" allows you to specify where vcpkg will store sources of downloaded dependencies. I think you can safely omit this option.

m-kuhn · 2024-10-30T21:16:53Z

This is there to avoid "long paths". Windows has a limitation (of 260?) chars and with some build paths this can cause problems. Or spaces in the path. You can try without, but it may cause issues

nicogodet · 2024-10-30T21:41:21Z

Indeed. Even with long path modification in regedit I recall build failure because of too long path.

danodom-tcb · 2024-10-31T13:09:52Z

No.

My QGIS src are in D:\QGIS_src and all commands from #59249 (comment) are executed within this folder.

-D VCPKG_INSTALL_OPTIONS="--x-buildtrees-root=C:\vcpkg\src" allows you to specify where vcpkg will store sources of downloaded dependencies. I think you can safely omit this option.

@m-kuhn @nicogodet so, do I need to use this or not? if so, it looks like I need to also download the current SDK.

fyi, I have a net new server and starting the process of getting vs and other things installed to start/test the build/execute process.

m-kuhn · 2024-10-31T13:12:55Z

you should set it, it needs to be a short path (not sure exactly, fewer than 10 chars or so) which is writable for you.
at the moment you should avoid the SDK it is not fully working. you do not need to download it.

danodom-tcb · 2024-10-31T13:15:09Z

you should set it, it needs to be a short path (not sure exactly, fewer than 10 chars or so) which is writable for you. at the moment you should avoid the SDK it is not fully working. you do not need to download it.

@m-kuhn . but isn't this the path to the SDK? or maybe I am misinterpreting

-D VCPKG_INSTALL_OPTIONS="--x-buildtrees-root=C:\vcpkg\src"

danodom-tcb · 2024-10-31T13:27:40Z

you should set it, it needs to be a short path (not sure exactly, fewer than 10 chars or so) which is writable for you. at the moment you should avoid the SDK it is not fully working. you do not need to download it.

@m-kuhn . but isn't this the path to the SDK? or maybe I am misinterpreting

-D VCPKG_INSTALL_OPTIONS="--x-buildtrees-root=C:\vcpkg\src"

Is this a local that will be created and written to, I can add it in but want to make sure I provision correctly, if any is needed.

danodom-tcb · 2024-10-31T13:31:25Z

@m-kuhn @nicogodet

Is this something I need to download or an option for the visual studio install (but I didn't see it)?

   -D CMAKE_C_COMPILER_LAUNCHER="C:\ccache\ccache.exe" `
   -D CMAKE_CXX_COMPILER_LAUNCHER="C:\ccache\ccache.exe" `

I don't have a ccache folder and the exe is not anywhere in the VS installed location tree..

nicogodet · 2024-10-31T13:48:49Z

but isn't this the path to the SDK? or maybe I am misinterpreting

-D VCPKG_INSTALL_OPTIONS="--x-buildtrees-root=C:\vcpkg\src"

This should point to an empty directory where your user can create folders and files

Is this something I need to download or an option for the visual studio install (but I didn't see it)?
   -D CMAKE_C_COMPILER_LAUNCHER="C:\ccache\ccache.exe" `
   -D CMAKE_CXX_COMPILER_LAUNCHER="C:\ccache\ccache.exe" `
I don't have a ccache folder and the exe is not anywhere in the VS installed location tree..

You can remove this option.
See https://ccache.dev/ for more info (this is a tool you need to manually install)

danodom-tcb · 2024-10-31T13:58:17Z

I don't have a ccache folder and the exe is not anywhere in the VS installed location tree..

You can remove this option. See https://ccache.dev/ for more info (this is a tool you need to manually install)

@nicogodet , I found it and went ahead and downloaded it, trying to follow as close to exact as I can ..

I've started the first cmake to build everything out... wish me luck :)

danodom-tcb · 2024-10-31T14:06:08Z

@nicogodet @m-kuhn I received errors on the first cmake, I'll post the manifest.

danodom-tcb · 2024-10-31T14:08:02Z

CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:112 (message):
Command failed: C:/QGIS/QGIS/build/vcpkg_installed/x64-windows-release/tools/python3/python.exe -m installer --prefix C:/QGIS/QGIS/build/vcpkg_installed/x64-windows-release/tools/python3 --destdir C:/QGIS/QGIS/build/vcpkg_installed/vcpkg/pkgs/py-setuptools_x64-windows-release C:/QGIS/QGIS/build/vcpkg_installed/vcpkg/pkgs/py-setuptools_x64-windows-release/wheels/setuptools-72.1.0-py3-none-any.whl
Working Directory: C:/QGIX/vcpkg/src/py-setuptools
Error code: 1
See logs for more information:
C:\QGIX\vcpkg\src\py-setuptools\python-installer-x64-windows-release-err.log

danodom-tcb · 2024-10-31T14:15:49Z

@nicogodet , @m-kuhn , I ran into at least one issue during the first cmake

Here are the files with the error information :
vcpkg-manifest-install.txt
python-installer-x64-windows-release-err.txt

Here is the command (yes, I know there is a typo, but files were populated there) :)
cmake -S .
-B build
-D WITH_VCPKG=ON
-D BUILD_WITH_QT6=ON
-D WITH_QTWEBKIT=OFF
-D VCPKG_TARGET_TRIPLET=x64-windows-release
-D VCPKG_HOST_TRIPLET=x64-windows-release
-D CMAKE_BUILD_TYPE=RelWithDebInfo
-D WITH_DESKTOP=ON
-D WITH_3D=ON
-D WITH_BINDINGS=ON
-D ENABLE_TESTS=OFF
-D USE_CCACHE=ON
-D CMAKE_C_COMPILER_LAUNCHER="C:\QGIS\ccache\ccache.exe"
-D CMAKE_CXX_COMPILER_LAUNCHER="C:\QGIS\ccache\ccache.exe"
-D VCPKG_INSTALL_OPTIONS="--x-buildtrees-root=C:\QGIX\vcpkg\src"
-D FLEX_EXECUTABLE="C:\QGIS\winflex\win_flex.exe"
-D BISON_EXECUTABLE="C:\QGIS\winflex\win_bison.exe"
-D CREATE_ZIP=ON

nicogodet · 2024-10-31T14:21:40Z

See https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=registry#enable-long-paths-in-windows-10-version-1607-and-later
And retry

danodom-tcb · 2024-10-31T14:24:49Z

See https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=registry#enable-long-paths-in-windows-10-version-1607-and-later And retry

@nicogodet ,
ok, I'll look, but I would suggest adding the link to ccache download and this link to the install.md file as well. :)

nicogodet · 2024-10-31T14:29:23Z

ccache is not mandatory

Link for long path could be added indeed

danodom-tcb · 2024-10-31T14:31:26Z

ccache is not mandatory

Link for long path could be added indeed

@nicogodet , How is ccache.exe used when it's included?

danodom-tcb · 2024-10-31T14:48:14Z

@nicogodet @m-kuhn , I have to admit, this is the first time I've seen a reference to fortran..

Also, how long does this step take in the process as it's just been sitting here for like 10+ minutes.

m-kuhn · 2024-10-31T15:21:16Z

prepare for hours

nicogodet · 2024-10-31T15:56:25Z

It took between 1 and 2 hours on an AMD Threadripper 32C/64T.

danodom-tcb · 2024-10-31T17:32:56Z

It took between 1 and 2 hours on an AMD Threadripper 32C/64T.

first step completed in 169 minutes... no errors thankfully..

danodom-tcb · 2024-11-01T03:01:41Z

@m-kuhn @nicogodet I got a ton of errors on the last step

cmake --build build --config RelWithDebInfo --target bundle

This looks like maybe some sort of path issue as it looks like it failed adding every file into the cpack.

tons of these :
CMake Error at C:/QGIS/QGIS/build/src/auth/basic/cmake_install.cmake:39 (file):
file INSTALL cannot find
"C:/QGIS/QGIS/build/output/plugins/Release/authmethod_basic.dll": File
exists.
Call Stack (most recent call first):
C:/QGIS/QGIS/build/src/auth/cmake_install.cmake:37 (include)
C:/QGIS/QGIS/build/src/cmake_install.cmake:38 (include)
C:/QGIS/QGIS/build/cmake_install.cmake:285 (include)

CMake Error at C:/QGIS/QGIS/build/src/auth/esritoken/cmake_install.cmake:39 (file):
file INSTALL cannot find
"C:/QGIS/QGIS/build/output/plugins/Release/authmethod_esritoken.dll": File
exists.
Call Stack (most recent call first):
C:/QGIS/QGIS/build/src/auth/cmake_install.cmake:38 (include)
C:/QGIS/QGIS/build/src/cmake_install.cmake:38 (include)
C:/QGIS/QGIS/build/cmake_install.cmake:285 (include)

CUSTOMBUILD : CPack error : Error when generating package: qgis [C:\QGIS\QGIS\build\bundle.vcxproj]
C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(254,5): e
rror MSB8066: Custom build for 'C:\QGIS\QGIS\build\CMakeFiles\4f936f24e2671abb107f35661b43692c\bundle.rule;C:\QGIS\QGIS
\CMakeLists.txt' exited with code 1. [C:\QGIS\QGIS\build\bundle.vcxproj]

m-kuhn · 2024-11-01T05:36:12Z

It seems it picks up Release instead of RelWithDebInfo when installing the targets from src/auth, I am not sure why that happens (but I'm confident that doing the build and bundling with Release instead would work)

nicogodet · 2024-11-01T08:51:05Z

I'm not confident it would work
Could you double check your commands and see if your are consistent with keyword value for CMAKE_BUILD_TYPE and --config ?

danodom-tcb · 2024-11-01T13:29:00Z

@nicogodet @m-kuhn , everything has worked so far up till Step 4 above in this thread.

this was the command from step3 above
cmake --build build --config RelWithDebInfo --parallel
this was the last command that failed (straight from step 4 above)
cmake --build build --config RelWithDebInfo --target bundle

danodom-tcb · 2024-11-01T13:34:25Z

@nicogodet @m-kuhn , It is a path issue... check this out..

this is the first error running the last step

CMake Error at C:/QGIS/QGIS/build/src/core/cmake_install.cmake:1046 (file):
file INSTALL cannot find
"C:/QGIS/QGIS/build/output/bin/Release/qgis_core.dll": File exists.
Call Stack (most recent call first):
C:/QGIS/QGIS/build/src/cmake_install.cmake:37 (include)
C:/QGIS/QGIS/build/cmake_install.cmake:285 (include)

Check the actual path 👍

CMake is referencing it in "Release" but the file is located in "RelWithDebInfo"

The bin/Release folder does not exist.

danodom-tcb · 2024-11-01T13:45:55Z

@nicogodet is there a good way to pass in the actual path here, or is something hardcoded?

I know it's a hack, but I could copy the RelWithDebInfo -> Release folders as I think that might work.. Albeit not the preferred method.

nicogodet · 2024-11-01T14:46:11Z

This is something configured by CMake.
I ran into the same issue before because I mixed CMAKE_BUILD_TYPE and --config keyword value. I had to delete build folder and rebuild
See my previous message

danodom-tcb · 2024-11-01T14:50:11Z

This is something configured by CMake. I ran into the same issue before because I mixed CMAKE_BUILD_TYPE and --config keyword value. I had to delete build folder and rebuild See my previous message

@nicogodet not completely following.. Are you saying I need to go back and rerun the first couple of steps. This is the initial command that I ran.

Not sure what you are requesting I do, but am hoping it's something with the last step where I don't have to do a complete rebuild.

cmake -S .
-B build
-D WITH_VCPKG=ON
-D BUILD_WITH_QT6=ON
-D WITH_QTWEBKIT=OFF
-D VCPKG_TARGET_TRIPLET=x64-windows-release
-D VCPKG_HOST_TRIPLET=x64-windows-release
-D CMAKE_BUILD_TYPE=RelWithDebInfo
-D WITH_DESKTOP=ON
-D WITH_3D=ON
-D WITH_BINDINGS=ON
-D ENABLE_TESTS=OFF
-D USE_CCACHE=ON
-D CMAKE_C_COMPILER_LAUNCHER="C:\QGIS\ccache\ccache.exe"
-D CMAKE_CXX_COMPILER_LAUNCHER="C:\QGIS\ccache\ccache.exe"
-D VCPKG_INSTALL_OPTIONS="--x-buildtrees-root=C:\QGIS\vcpkg\src"
-D FLEX_EXECUTABLE="C:\QGIS\winflex\win_flex.exe"
-D BISON_EXECUTABLE="C:\QGIS\winflex\win_bison.exe"
-D CREATE_ZIP=ON

nicogodet · 2024-11-01T15:03:05Z

Well I can't help much...

If CMake target looks for files in Release folder it means that you run with Release at some point.

Indeed completely delete build folder and rebuild is a solution.

danodom-tcb · 2024-11-01T15:06:37Z

@m-kuhn I'm able to confirm a successful build on windows with below steps:

Install VS2022

 cmake -S . `
       -B build `
       -G Ninja `
       -D WITH_VCPKG=ON `
       -D BUILD_WITH_QT6=ON `
       -D WITH_QTWEBKIT=OFF `
       -D VCPKG_TARGET_TRIPLET=x64-windows-release `
       -D VCPKG_HOST_TRIPLET=x64-windows-release `
       -D CMAKE_BUILD_TYPE=RelWithDebInfo `
       -D WITH_DESKTOP=ON `
       -D WITH_3D=ON `
       -D WITH_BINDINGS=ON `
       -D ENABLE_TESTS=OFF `
       -D USE_CCACHE=ON `
       -D CMAKE_C_COMPILER_LAUNCHER="C:\ccache\ccache.exe" `
       -D CMAKE_CXX_COMPILER_LAUNCHER="C:\ccache\ccache.exe" `
       -D VCPKG_INSTALL_OPTIONS="--x-buildtrees-root=C:\vcpkg\src" `
       -D FLEX_EXECUTABLE="C:\Flex_bison\win_flex.exe" `
       -D BISON_EXECUTABLE="C:\Flex_bison\win_bison.exe" `
       -D CREATE_ZIP=ON `
       -D CMAKE_INSTALL_PREFIX="D:\Qgis_local"

Use CREATE_ZIP=ON to simplify the qgis execution later (my own choice)
Specify CMAKE_INSTALL_PREFIX to avoid error later

 cmake --build build --config RelWithDebInfo --parallel

 cmake --build build --config RelWithDebInfo --target bundle

Execute .\build\_CPack_Packages\win64\ZIP\qgis-3.39.0-win64\bin\qgis.exe

These are what I followed.

danodom-tcb · 2024-11-01T15:06:57Z

Well I can't help much...
If CMake target looks for files in Release folder it means that you run with Release at some point.
Indeed completely delete build folder and rebuild is a solution.

@nicogodet
I didn't run with Release, I have posted my exact commands from the shell and are verbatim to what you posted ^^^^^^.

danodom-tcb · 2024-11-01T15:13:49Z

@nicogodet @m-kuhn , so for grins and giggles, I did the copy/paste for the RelWithDebInfo folder -> release, and step 3 ran...

AND... I am able to run QGIS using the last command.. my guess is that there's something in that initial cmake that is hardcoded to release in some cases, but not all. IDK..

I am happy to help debug/triage this as it feels like the process refinements you guys have made are VERY, VERY close to beginning to end.

danodom-tcb · 2024-11-06T15:16:02Z

@m-kuhn @nicogodet , just bumping this in case you have any ideas or if this needs to be reported as a separate issue.

nicogodet · 2024-11-06T15:18:22Z

I solved this issue by cleaning my build folder and retry. So it looks like a local issue rather than a real one...

danodom-tcb · 2024-11-06T15:23:50Z

I solved this issue by cleaning my build folder and retry. So it looks like a local issue rather than a real one...

@nicogodet , did you change anything on the command that you ran (see above)? I ran from a clean system that had just been built out, so there wasn't any residual data/items floating around.

m-kuhn · 2024-11-06T15:48:36Z

I think this is about running from the build folder vs running from a bundled zip.
To run from the build folder, a qgis.env might help point it to the proper paths in the vcpkg_installed folder, but didn't check yet what variables to set exactly.

danodom-tcb · 2024-11-06T16:50:39Z

I think this is about running from the build folder vs running from a bundled zip. To run from the build folder, a qgis.env might help point it to the proper paths in the vcpkg_installed folder, but didn't check yet what variables to set exactly.

@m-kuhn @nicogodet I am thinking that we can close this if you guys concur. The only issue is the last step in building the artifacts and an issue of where it's trying to find them.

Leave this open to track, or close?

Either way, a huge thank you to you both for getting this almost to the finish line.

danodom-tcb · 2024-11-12T15:33:40Z

@m-kuhn @nicogodet I did rerun a build and it looks like there are only 3 of the n-number of folders that need to be renamed from "RelWithDebInfo" to "Release", so this looks like it may be isolated to a subset of the dependent folders for the pack process.

The issue seems possibly isolated to these paths :
C:\QGIS\QGIS\build\output
C:\QGIS\QGIS\build\output\plugins
C:\QGIS\QGIS\build\output\bin
C:\QGIS\QGIS\build\output\python\qgis

m-kuhn · 2024-11-21T14:06:23Z

Here is an approach that solves some of the issues for this scenario: kadas-albireo/kadas-albireo2#179
Inspired by the current (windows specific) .env file of QGIS, adjusted for vcpkg

xuhancn · 2025-01-27T15:04:53Z

Mark, I occurred this issue also.

danodom-tcb added the Bug Either a bug report, or a bug fix. Let's hope for the latter! label Oct 28, 2024

agiudiceandrea added the Build/Install Related to compiling or installing QGIS label Oct 31, 2024

Windows 11, Visual Studio build, QGIS.exe built, but will not run #59249

Windows 11, Visual Studio build, QGIS.exe built, but will not run #59249

Comments

danodom-tcb commented Oct 28, 2024

What is the bug or the crash?

Steps to reproduce the issue

Versions

Supported QGIS version

New profile

Additional context

nicogodet commented Oct 28, 2024

danodom-tcb commented Oct 28, 2024

nicogodet commented Oct 29, 2024

nicogodet commented Oct 29, 2024

nicogodet commented Oct 29, 2024

danodom-tcb commented Oct 29, 2024 via email • edited Loading

danodom-tcb commented Oct 29, 2024 via email • edited Loading

nicogodet commented Oct 30, 2024

nicogodet commented Oct 30, 2024

m-kuhn commented Oct 30, 2024

nicogodet commented Oct 30, 2024

danodom-tcb commented Oct 30, 2024

danodom-tcb commented Oct 30, 2024

m-kuhn commented Oct 30, 2024

danodom-tcb commented Oct 30, 2024

nicogodet commented Oct 30, 2024

danodom-tcb commented Oct 30, 2024

nicogodet commented Oct 30, 2024 • edited Loading

m-kuhn commented Oct 30, 2024

nicogodet commented Oct 30, 2024

danodom-tcb commented Oct 31, 2024

m-kuhn commented Oct 31, 2024

danodom-tcb commented Oct 31, 2024 • edited Loading

danodom-tcb commented Oct 31, 2024

danodom-tcb commented Oct 31, 2024

nicogodet commented Oct 31, 2024

danodom-tcb commented Oct 31, 2024

danodom-tcb commented Oct 31, 2024

danodom-tcb commented Oct 31, 2024

danodom-tcb commented Oct 31, 2024 • edited Loading

nicogodet commented Oct 31, 2024

danodom-tcb commented Oct 31, 2024

nicogodet commented Oct 31, 2024

danodom-tcb commented Oct 31, 2024 • edited Loading

danodom-tcb commented Oct 31, 2024

m-kuhn commented Oct 31, 2024

nicogodet commented Oct 31, 2024

danodom-tcb commented Oct 31, 2024

danodom-tcb commented Nov 1, 2024

m-kuhn commented Nov 1, 2024

nicogodet commented Nov 1, 2024

danodom-tcb commented Nov 1, 2024

danodom-tcb commented Nov 1, 2024 • edited Loading

danodom-tcb commented Nov 1, 2024

nicogodet commented Nov 1, 2024

danodom-tcb commented Nov 1, 2024

nicogodet commented Nov 1, 2024

danodom-tcb commented Nov 1, 2024

danodom-tcb commented Nov 1, 2024

danodom-tcb commented Nov 1, 2024

danodom-tcb commented Nov 6, 2024

nicogodet commented Nov 6, 2024

danodom-tcb commented Nov 6, 2024

m-kuhn commented Nov 6, 2024

danodom-tcb commented Nov 6, 2024

danodom-tcb commented Nov 12, 2024

m-kuhn commented Nov 21, 2024 • edited Loading

xuhancn commented Jan 27, 2025

danodom-tcb commented Oct 29, 2024 via email •

edited

Loading

danodom-tcb commented Oct 29, 2024 via email •

edited

Loading

nicogodet commented Oct 30, 2024 •

edited

Loading

danodom-tcb commented Oct 31, 2024 •

edited

Loading

danodom-tcb commented Oct 31, 2024 •

edited

Loading

danodom-tcb commented Oct 31, 2024 •

edited

Loading

danodom-tcb commented Nov 1, 2024 •

edited

Loading

m-kuhn commented Nov 21, 2024 •

edited

Loading