[Insight-users] Using automake instead CMake - Dangerous?

[Luis Ibanez]

Hi Wagner,


Using Automake instead of CMake is indeed *Very Dangerous*:


You are are terrible risk of:


1) Wasting your valuable time in tweaking the
    configure options instead of using your skills
    for doing Medical Image Processing.

2) Have a hard time finding all the settings required
    for building applications based on ITK and/or VTK.

3) Customizing a configuration that will only work
    in a Unix environment and cannot be ported to
    MS-Windows, Mac, or be used with the Borland compiler.

4) Finding at the end that the reason why CMake came
    into existence is that ITK/VTK developers got tired
    of the obscurities and lack of portability of Automake.

5) You will have trouble publishing a papers with a title:
     "How I configured my project with Automake".


Enjoy CMake !


   Best regards,


     Luis



---------------------
Wagner Sales wrote:
> Hi all,
> 
> I'm currently using ITK, Qt, kdelibs and VTK and others on a Linux box. 
> CMake are the default only in ITK and VTK, and others projects are using 
> Automake ( unsermake ) to build. Putting all in together ( my project ) 
> I was decided to use choose the build tool Automake, instead of CMake, 
> and by editing my Makefile.am, I put the includes, libs, etc. To me, in 
> exception some compile warnings ( deprecated, etc ) that's work pretty 
> fine. Well, but I'm not the most experienced user of ITK/VTK :) ... Then 
> I asking by others here: Are dangerous this build approach? Have some 
> experience with that? And my compile warnings ( some I know how solve, 
> others not ), have some compiler documentation, more especific: gcc tips 
> or parameters ( of course, except the --wno-deprecated ;) )?
> 
> Thks in advance.
> 
> Wagner
> _______________________________________________
> Insight-users mailing list
> Insight-users at itk.org
> http://www.itk.org/mailman/listinfo/insight-users
> 
>