Hello,
I am trying to build Slicer at my laptop, Win 10 while I follow nightly instructions from slicer documentation for Release mode. But I got the following errors:
Do you have any idea how can I solve that issue?
Thanks
Hello,
I am trying to build Slicer at my laptop, Win 10 while I follow nightly instructions from slicer documentation for Release mode. But I got the following errors:
Do you have any idea how can I solve that issue?
Thanks
I see in your Visual Studio window that the configuration is currently specified as “Release”, but your build tree is called “C:/S4D/…” which seems to indicate that you want a “Debug” configuration. Did you previously start a build as debug and are now doing a release build?
According to the Slicer build instructions https://www.slicer.org/wiki/Documentation/Nightly/Developers/Build_Instructions#Windows_2 you cannot use the same build tree for both release and debug builds.
Otherwise I suggest making sure you have fetched and pulled all the latest commits from Github for Slicer’s master branch. If all else fails, clearing out your S4D directory and trying again should fix it.
Thanks for the response.
No, I didn’t start to build in debug, only at release.
Sure, I am going to try again and let you know if I will have the same issue.
I suggest you first close Visual Studio (currently open with the top-level solution) and instead open the solution file C:\s4d\Slilcer-build\Slicer.sln
, then you wlll be able to build again, this should report a more informative message.
@jcfr I built that sln and I got the follwoing:
Also interesting is that @siaeleni told me that her slicer build does run (using Slicer-build\Slicer.exe), but those build errors at the top level persist.
I tried to build again the top level sln after a lot of tries and got it finally.
I don’t know why, but seems that has no errors now. Note, that I didn’t change any setting at my laptop.
That’s good news anyway
I still suspect it’s an antivirus or similar issue that locks some of the files at random.
I usually get errors similar to those top-level errors (launcher icon cannot be updated, etc.) when I have a Slicer instance running.