| Re: [AD] build process overhaul |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: Re: [AD] build process overhaul
- From: Chris <chris.kcat@xxxxxxxxxx>
- Date: Sat, 26 Nov 2005 14:59:46 -0800
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:to:subject:date:user-agent:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=Fu3spj0lAQJDdCBObw1mZV6YAv8N0YLGA4ay2BYBmgl0FfgcFdqfFTJDXzdfOIHgArrWIwxUC2Ij+ElUgUccxrKjV9AG91WvIfPA0yG0saaqTAzlhElHrqX+ZQNk6snks87V9WVprHFMeLRIA6LxIZAuBDHqnbhVi5DBqqn1tNU=
On Saturday 26 November 2005 06:09 am, Elias Pschernig wrote:
> Chris: Do you think CBUILD is ready to replace Allegro's current build
> system? Having one of our devs as the author of the build system
> certainly would be an advantage :)
Probably not. Although, I wouldn't know how far it needs to go to be useable.
The only things I can think of off the top of my head are manual dependancy
checking (for the assemebly files) and being able to detect more platforms,
other than Unix and Win32. If the assembly files are going away for 4.3, then
I don't know what else, other than detecting more platforms, would be needed.