[IGSTK-Developers] Cmake help

[Luis Ibanez]

Hi Kevin,


If this is a Mac laptop that you are bringing to the meeting,
then we could check on the build process on Monday too.


   Luis


[----------------
Kevin Gary wrote:

> Hi Luis,
> 
> Thanks for responding. I did do a 't' and still do not see any variables.
> I am running ccmake from the proper placces I think. I also go
> ahead and generate a makefile and do 'make' and cannot build
> as it first complains about not finding ITK-related things.
> 
> I obviously need the 'cmake for dummies' crash course.
> I'll read the online docs and maybe get some help from the
> group Monday.
> 
> Thanks,
> K2
> 
> 
> Luis Ibanez wrote:
> 
>>
>> Hi Kevin,
>>
>> CMakes makes reasonable effort for finding the other tools that
>> you need for IGSTK (e.g. ITK, VTK, FLTK). When CMake finds any
>> of those tools on it own, then it will not ask you for them.
>>
>> It UNIX (Mac/Linux) it is easier to find things in standard
>> directories (e.g. /use/local...), therefore CMake tends to have
>> more success finding things, if they are installed in the standard
>> typical places.
>>
>> So, to put it short: If ccmake is not asking your for those other
>> componente it may mean that they have been found.  Note however,
>> that CMake does a sequencial analysis. That means: when you hit
>> the "c" key for configuring, it will look for the first tool in
>> the list of dependencies and if it is not found it will ask you
>> for this specific one. Then you will hit "c" again and search for
>> the next one... and so on.  This is necessary because at every
>> time you hit "c", new dependencies may come into play and cmake
>> must reevaluate the tools needed.
>>
>> So, don't worry if the options do not appear at the beginnin.
>> Just select "c" (for configure) and see what the dialogs bring.
>> If you manage to go through the configuration without being asked
>> about FLTK, that means that CMake found it on its own.
>>
>> You can alway double-check the entire cache by going to the
>> "Advanced" mode. This is done with the "t" key. In this mode
>> CMake will show you all the variables in the cache. If you go
>> through the multiple pages of the GUI, you should be able to
>> see the FLTK related variables.
>>
>>
>> Please let me know if you find any problem
>> during the configuration.
>>
>>
>>
>>     Thanks
>>
>>
>>        Luis
>>
>>
>>
>> -----------------
>> Kevin Gary wrote:
>>
>>> Unfortunately I am not familiar with cmake so sometimes (like now)
>>> I have questions that are probably elementary to you folks.
>>>
>>> In following our build instructions, it says to run ccmake from the
>>> binary directory and specify the source directory. I do so, but
>>> ccmake only asks me to configure 5 cmake-related looking
>>> variables (CMAKE_BUILD_TYPE, CMAKE_INSTALL_PREFIX)
>>> etc. and not the ITK/VTK/FLTK related ones I typically see
>>> in the GUI version on windows (I'm on a Mac/Darwin).
>>>
>>> Pointers?
>>>
>>> Thanks,
>>> K2
>>>
>>
>>
>>
> 
>