[Insight-developers] SGI Build

Hans Johnson hans-johnson at uiowa.edu
Thu Jul 28 20:41:29 EDT 2005


Karthik,

I would love to submit this file, but I need to specify it from
/usr/local/bin/cmake.   I do not run the ctest command, but rather do a
"make Nightly" in the build directory.

Regards,
Hans

PS:  I need to be able to add the extra commands to the following call to
cmake.
==================
»·cd  $(BUILDDIR) && cmake $(CONFIGDIR) \
-DCMAKE_CXX_COMPILER:FILEPATH="$(CXX) " \
-DCMAKE_CXX_FLAGS:STRING="$(CXXFLAGS) " \
-DCMAKE_C_COMPILER:FILEPATH="$(CC) " \
-DCMAKE_C_FLAGS:STRING="$(CFLAGS) " \
-DCMAKE_EXE_LINKER_FLAGS:STRING="$(LDFLAGS) " \
-DCMAKE_MODULE_LINKER_FLAGS:STRING="$(LDFLAGS) $(CXX_ARFLAGS_SHARED) " \
-DCMAKE_SHARED_LINKER_FLAGS:STRING="$(LDFLAGS)  $(CXX_ARFLAGS_SHARED)" \
-DCMAKE_INSTALL_PREFIX:PATH=$(INSTALLDIR)  \
-DEXECUTABLE_OUTPUT_PATH:PATH=$(INSTALLDIR)/bin \
-DLIBRARY_OUTPUT_PATH:PATH=$(INSTALLDIR)/lib \
-DCMAKE_MAKE_PROGRAM:FILEPATH=$(MAKE) \
-DBUILD_AUXILIARY:BOOL=ON \
-DBUILD_FEM_CODE:BOOL=ON \
-DBUILD_FEM_MESH_EXAMPLE:BOOL=ON \
-DBUILD_METAIMAGE:BOOL=ON \
-DBUILD_EXAMPLES:BOOL=ON \
-DBUILD_TESTING:BOOL=ON \
-DBUILD_VTKINTERFACE:BOOL=ON \
-DFEM_USE_SMART_POINTERS:BOOL=OFF \
-DITK_USE_SYSTEM_STDLIB:BOOL=$(DEFAULT_ITK_USE_SYSTEM_STDLIB) \
-DBUILD_SHARED_LIBS:BOOL=ON \
-DITK_WRAP_TCL:BOOL=$(LOCAL_ITKTCL) \
-DITK_CSWIG_TCL:BOOL=$(LOCAL_ITKTCL) \
-DTCL_INCLUDE_PATH:PATH=$(TCLBASEPATH)/include \
-DTCL_LIBRARY:FILEPATH=$(TCLBASEPATH)/lib/libtcl8.4.so \
-DTCL_TCLSH:FILEPATH=$(TCLBASEPATH)/bin/tclsh8.4  \
-DTK_INCLUDE_PATH:PATH=$(TCLBASEPATH)/include \
-DTK_LIBRARY:FILEPATH=$(TCLBASEPATH)/lib/libtk8.4.so \
-DSITE:STRING=$(COMPILER_HOSTNAME).uiowa \
-DBUILDNAME:STRING=$(ITK_BUILD_NAME) \
-DUSE_GDCM:BOOL=ON \
$(FFTW_OPTIONS)

cd  $(BUILDDIR) && make Nightly
==================


On 7/28/05 5:50 PM, "Karthik Krishnan" <Karthik.Krishnan at kitware.com> wrote:

> Hi Hans,
> 
> Could you please post your CMakeLists.txt file to the dashboard like
> most of the other machines do. That way everybody can see the
> flags/settings on all the machines.
> All you need to do is to add
> 
> -A ${CTEST_SCRIPT_DIRECTORY}/${CTEST_SCRIPT_NAME}
> 
> to the CMakeLists.txt file.
> 
> See 
> http://www.itk.org/Testing/Sites/Sabbath.kitware/Linux-g++-3.4-Shared/20050728
> -0100-Nightly/Notes.html
> 
> Thanks
> Regards
> Karthik
> 
> 
> Hans Johnson wrote:
> 
>> Mathieu,
>> 
>> SGI Flags for both 7.3.3.1m and 7.4.2m compilers that are working for the
>> kraepelin.uiowa nightly builds.
>> 
>> DEBUG BUILD:
>> //No help, variable specified on the command line.
>> CMAKE_CXX_FLAGS:STRING= -n32 -g -DUDEBUG -G0 -multigot  -no_auto_include
>> -xansi -LANG:std -LANG:ansi-for-init-scope=ON -woff
>> 15,84,1110,1209,1424,1468,3102,3210,3439
>> 
>> //No help, variable specified on the command line.
>> CMAKE_C_FLAGS:STRING= -n32 -g -DUDEBUG -G0 -multigot   -xansi -woff
>> 15,84,1110,1209,1424,1468,3102,3210,3439
>> 
>> OPTIMIZED BUILD:
>> CMAKE_CXX_FLAGS:STRING= -n32 -O3 -DNDEBUG -G0 -multigot  -no_auto_include
>> -xansi -LANG:std -LANG:ansi-for-init-scope=ON  -woff
>> 15,84,1110,1209,1424,1468,3102,3210,3439
>> 
>> //No help, variable specified on the command line.
>> CMAKE_C_FLAGS:STRING= -n32 -O3 -DNDEBUG -G0 -multigot   -xansi -woff
>> 15,84,1110,1209,1424,1468,3102,3210,3439
>> 
>> These flags have been stable for 6-8 months.
>> 
>> Regards,
>> Hans
>> 
>> PS:  These notes are now on the WIKI site.
>> 
>> 
>> On 7/28/05 3:18 PM, "Mathieu Malaterre" <mathieu.malaterre at kitware.com>
>> wrote:
>> 
>>  
>> 
>>> Hans Johnson wrote:
>>>    
>>> 
>>>> Mathieu,
>>>> 
>>>> I've been compiling gdcm and all of itk+ the wrapping on 6.5.26m for months
>>>> on the 7.3.3.1m compilers (see dashboard for Kraepelin.uiowa).
>>>> Additionally, I've gotten 6.5.26m with the 7.4.2 compilers working for itk
>>>> (wrapping still does not work).
>>>> 
>>>> I do use different compiler flags than the defaults.
>>>> 
>>>> Can I help?
>>>>      
>>>> 
>>> Sure do you have like notes or a Wiki for that. There is a user: Michael
>>> Hardisty who is not able to build ITK. And I seriously have no idea what
>>> is going on, the error looks pretty odd.
>>> 
>>> Thanks
>>> Mathieu
>>> 
>>>    
>>> 
>> 
>> 
>> _______________________________________________
>> Insight-developers mailing list
>> Insight-developers at itk.org
>> http://www.itk.org/mailman/listinfo/insight-developers
>> 
>>  
>> 
> 




More information about the Insight-developers mailing list