| 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: Ryan Patterson <cgamesplay@xxxxxxxxxx>
- Date: Tue, 13 Dec 2005 12:14:21 -0500
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=tJ+W34MmNDaMDBTr/AEO2Uu0B8UjzSADci07ZC0PU2akGaCe3UCYrbRdCgycxnY0pwMLjedoSYusWhxXVgHUy/1iBMt9HgaEB+gL/yEo6H2/E9U3WCb3YvkI4XxgrmimNe1m3GHcgI+bzEpLp5bMGn6w8p7JkWlloIvNKzX+4n4=
On 12/11/05, Jon Rafkind <workmin@xxxxxxxxxx> wrote:
> Each SConstruct in the scons/ directory returns an environment that it
> has created/modified and a list of files that should be compiled into
> the allegro library. Finally the top level SConstruct uses this
How difficult will it be to compile other projects into Allegro's
source? I.E. Add source files to the Allegro library, *or* chainload
build processes?
--
Regards,
Ryan Patterson <mailto:cgamesplay@xxxxxxxxxx>