[M3devel] AMD64_DARWIN with OSX Mavericks

[Dragiša Durić]

AFAIK, automake/autoconf is big pain… of C world. Whole build systems were devised/built, just to bypass autowhatever.

I don’t see any reason to envy current C build systems. But, if you are looking for a model, then also look at Maven/Gradle of Java world. Convention over configuration paradigm (very accepted, and which looks very much like cm3 config + m3makefile ) is so far away from autowhatever as possible. 
--
Dragiša Durić
dragisha at m3w.org



On 13 Nov 2013, at 18:11, Jay <jay.krell at cornell.edu> wrote:

> I do repeatedly wonder if we should be a thin layer over automake/autoconf/pkg-config/libtool. I look into them every so often. What bugs me, maybe not pkg-config, is that they seem slow and have to generate files. I want something that usually makes fast decisions for every run. Optionally recording them in a file for bootstrapping or overridability. Cm3 was ahead of its time, kinda, but those tools solve much of the same problem, with other people maintaining them and more "dynamism"/"manifestation" -- I can't think of the word, but throw together a random posixish platform and autoconf can probe it and piece it together. There is no need to record static platform definitions and local configuration details are inferred/deduced at build-time, and there is good cross build support.
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20131113/358cbd82/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 495 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20131113/358cbd82/attachment-0002.sig>