MacArthur, Ian (SELEX) (UK) wrote:
> 
>> Huh?  Why wouldn't it work?
> 
> Because I have a variety of odd, largely "unsupported" targets, often
> built with cross-compilation and using archaic toolsets.
> So, to make my life as simple as possible, I need a "lowest common
> denominator" build environment. Makefiles work, almost anything "clever"
> does not. I used to use jam a lot (long before Apple adopted it for PB,
> then dropped it again...), but keeping that in sync was too
> troublesome... I've looked at other choices since (Cmake, Scons, etc.)
> but so far, for my needs, they introduce more problems than they solve.
> 
> However, I am quite prepared to believe that for users in the general
> desktop cases, these tools probably are easier. YMMV.

You *do* realize that cmake is a Makefile pre-processor, just like
autoconf right?  You get a standard GNU or NMake Makefile in the end (or
an IDE file if you prefer that), which can, barring some minor
exceptions, be created on a different machine with different
architecture for cross-compilation.

Scons, Jam and all that crap are not, and that's why the suck for cross
compilation.


-- 
Gonzalo Garramuño
[EMAIL PROTECTED]

AMD4400 - ASUS48N-E
GeForce7300GT
Kubuntu Edgy

_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev

Reply via email to