[M3devel] replace build system??

[Jay K]

Yes it is a backend within cm3, a peer of cm3cg and the integrated NT/x86 backend.
I'd really like to move everyone from cm3cg to it. I tested it a bunch at least a while ago.


There is still some scripting or such to make a distribution with it.
Currently what is provided is enough to build cm3 and mklib from system-specific C.
Statically linked.
System-specific is hard to completely fix.
Statically linked is normal for cm3/mklib anyway.
It generates little Makefiles.

Ideally the entire system would be distributed this way.
Though merely distributing the cm3cg produced .s/.o/.a files would be an approvement.

Everytime I look, I don't like cmake or autotools, nor want to keep maintaining our system-specific config files,
nor have the time/energy to write something new in C or C++.

 - Jay



----------------------------------------
> Date: Tue, 31 May 2016 12:05:03 -0400
> From: hendrik at topoi.pooq.com
> To: m3devel at elegosoft.com
> Subject: Re: [M3devel] replace build system??
>
> On Tue, May 31, 2016 at 07:32:23AM +0000, Jay K wrote:
>> Design of a new or bootstrap/cross/distribution build system?
>>
>>
>> I'd really like our stuff to be as easy to distribute and develop
>> as stuff using e.g. autotools or cmake. And as portable.
>>
>>
>> And to reuse other people's work.
>>
>>
>> And have a solid cross build story.
>>
>>
>> And distribution be C or .o or .a or .S files, not executables and so/dylibs.
>
> Isn't there an m3 compiler that generates C? Didn't you even write it?
>
> -- hendrik
> k
> _______________________________________________
> M3devel mailing list
> M3devel at elegosoft.com
> https://mail.elegosoft.com/cgi-bin/mailman/listinfo/m3devel