I am building custom slicer from templet provided by slicer cat
I have gone through https://github.com/Slicer/SlicerBuildEnvironment and able to build it but getting issue in how to execute the executable I am using "qt5-centos7 to use GCC 7 " based docker image.
The SlicerBuildEnvironment docker image is for testing the build. We have separate dockerfiles for running Slicer, which typically install a precompiled release in the image and set up a vnc server so that you can see the GUI of the application running in the container. Probably you can combine the two kinds of images.
However, to better reproduce the end-user experience, it is probably better to build Slicer using the standard build instructions and test it by running directly, natively on a physical machine.
we are using standard build environment but facing issue while replicating build environment in multiple local system, however we are keeping same tool versions.
Any solution for this?
What operating systems are causing trouble? What problems do you have when replicating the build environment: build fails on some systems or the generated binaries are not compatible with each other?
First build system configuration is EDDITION: Windows Server 2016 Standard Evaluation VERSION: 1607 OS BUILD: 14393.4651
I would like to give you brief introduction regards our development.
First we started building on above mentioned system.
which we are still using.
Now we are expanding the development team, and providing local personal system with following Operating system configurations. EDDITION: Windows 10 Home Single Language VERSION: 20H2 OS BUILD: 19042.1288
and how we are building is First we are taking our custom templet and building it, which is successfully building then we are replacing slicersource-src folder with our latest developed code. then we are building and getting errors as mentioned in previous answer.
moreover is there any way to implement GITHUB in our development?
This can certainly lead to build errors. For performance reasons, not all dependencies are rebuilt when you just change the Slicer source folder, which may result in trying to build a new Slicer with an older CTK version. You can fix this by rebuilding CTK manually - opening the (slicer-build)\CTK-build\CTK.sln project in Visual Studio and build it in the appropriate build mode. But the clean solution is to update the template to pull Slicer source from your repository and then do a clean build.
I don’t think that’s the issue here, but Windows Server works quite differently from a regular Windows version. If you can, use non-server Windows edition.