Hello everyone, I am currently getting started on creating an extension for 3DSlicer. As https://www.slicer.org/wiki/Documentation/Nightly/Developers/Build_Module suggests, I have to build 3DSlicer from source to use C++ modules. I am running Archlinux and I was following https://www.slicer.org/w…

C++14 is default for gcc 6 (see https://gcc.gnu.org/gcc-6/changes.html ) and I think Slicer is not expected/tested to compile with even C++11.

Eight months ago, I could build Slicer on ArchLinux with gcc6 using c++98 throughout. I tried again a few weeks ago with gcc7. Using c++98, build fails in DCMTK. Using c++11, DCMTK builds, but then it will fail again in BRAINSCommonLib. The latter seems to require c++98 however. I gave up after a f…

[image] chir.set: I tried again a few weeks ago with gcc7. Using c++98, build fails in DCMTK. How did you make sure that your flags prescribing c++98 were propagated throughout the superbuild process? I am not sure that works. [image] chir.set: BRAINSCommonLib @hjmjohnson maintains th…

We’ll release a new stable version (based on the latest nightly) within a few weeks. So, probably it is not worth spending time with the old stable release, just try to build the latest nightly and let us know if you still have issues.

I used : export CXXFLAGS="-std=c++98 -Wno-error -fpermissive" export CFLAGS="-Wno-error" before configuring with ccmake. The latter allows to switch to advanced options, where the CXXFLAGS declared to ccmake can be checked. Concerning BRAINSCommonLib, it seems to ignore environment variables tot…

Of course I always ‘git pull’ before building.

[image] chir.set: VNL, which has been built with c++11 (if not, we won’t get beyond DCMTK) I don’t understand this part. You seem to imply DCMTK requires c++11, but this is not the case.

Ok, so I tried to built the current nightly (master-branch). I still used gcc 7.1 and tried both C++11 and C++98 (using export CXXFLAGS) with -DCMAKE_BUILD_TYPE:STRING=Release. I always get compile errors in DCMTK about char16_t not being available. I’m kind of clueless at the moment. I am always d…

[image] thaenel: tried both C++11 and C++98 (using export CXXFLAGS) I think all CXX flags have to be set in CMake (what you set in Slicer are propagated to all libraries). Environment variables should not have any effect.

[image] thaenel: Or is the current nightly still using C++98? I believe this is the case. [image] thaenel: Does this mean that my system header files requires C++11? Probably not. You can look into that header file. It probably has a series of checks to include certain line of code de…

Building 3DSlicer from source using gcc 7.1

Support

Topic		Replies	Views
3D Slicer Build Error with GCC 7 on Ubuntu 17.04 Development	18	1609	February 18, 2018
Build slicer stable release from the source on ArchLinux Development build	6	737	October 31, 2020
Failed build Slicer in Windows10 with Visual Studio 2017,Qt 5.10.1 Development build , qt	27	2395	April 15, 2024
Can't start Slicer on Linux on one machine Support	57	3590	January 21, 2020
Build failure windows Development	36	3469	July 28, 2019

Building 3DSlicer from source using gcc 7.1

Related topics