In Windows, when compiling Slicer, is Slicer directly downloaded and used with the pre-compiled CTKAppLauncher? Specifically, the CTKAppLauncher-0.1.31-win-amd64.tar file. If I want to modify CTKAppLauncherLib, do I need to replace the relevant exe files from my compiled CTKAppLauncherLib-build folder to the CTKAPPLAUNCHER folder? However, when I perform this operation, I encounter compilation errors, and the generated exe file size differs significantly from the original. I am using a custom template in Slicer’s generation. I hope someone can provide some assistance. Thank you.
I have successfully replaced the compiled files from CTKAppLauncher into Slicer. Here, I would like to share my experience. The exes generated within CTKAppLauncherLib-build, compiled from within Slicer, were not functional, possibly due to missing dependencies in my Qt installation. Following the CTKAppLauncher’s build instructions, I obtained a statically compiled version of Qt 5.12 and used it to compile CTKAppLauncher separately. This resolved the issue.
1 Like
The launcher is needed to set up Qt paths so that dynamically-loaded Qt libraries can be found. Since Qt paths are not set up for the launcher itself, the launcher has to be built statically (all the libraries has to be linked into the executable).
We don’t build CTKAppLauncher executable as part of the Slicer build process because static linking of Qt libraries would require a paid Qt license.