[MINC-development] compiling Display from github

[Jordi Gutiérrez Hermoso]

On 5 November 2012 10:39, Vladimir S. FONOV <vladimir.fonov at gmail.com> wrote:
> On Mon, Nov 5, 2012 at 10:28 AM, Jordi Gutiérrez Hermoso
> <jordigh at octave.org> wrote:
>>
>> On 5 November 2012 10:03, Jason Lerch <jason at phenogenomics.ca> wrote:
>> > No, I was using the master branch. I'll give the devel branch a try
>> > later - which I guess will include trying to understand the god
>> > forsaken cmake build system (I know that autoconf sucks and the
>> > thought of writing anything in m4 is horrid, but at least I got used
>> > to it!).
>>
>> Cmake sucks too, since it's a lot more difficult to write custom tests
>> for it that aren't already built-in. It's less flexible than
>> autotools, but using it as a user should be no more difficult than
>> autotools. Instead of doing
>>
>>     cd build-directory ## optional
>>     /path/to/configure
>>     make
>>     make install
>>
>> do
>>
>>     cd build-directory ## optional
>>     cmake /path/to/CMakeLists.txt
>>     make
>>     make install
>>
>> As we say in IRC, "The 'suck' is a unit vector. A given foo doesn't
>> suck LESS, it just sucks in a direction a given hacker finds less
>> disagreeable."

> Are you ready to take over as official minc maintainer?

No, I didn't mean to say that CMake is a bad choice. Building is a
chore. All choices are equally annoying. For MINC, CMake may have a
'suck' vector in a better direction than autotools. I'm used to both
and I dislike both for different reasons, but I've disliked every
build system I've ever seen (ant, Scons, bjam...)

> If you are not, then in this particular situation your 'suck' vector is
> purely imaginary.

So it points straight up in the complex plane? :-)

- Jordi G. H.