How about this... We create a rule that is something like "GenerateConfig" This basically runs an external shell script that builds a small file called something like "openbeos.inc" with the location of libgcc.a and anything else we find we need. We make the file's existance a dependancy (somehow) so it has to be produced and include it in the build. how does that sound? david ----- Original Message ----- From: "Ingo Weinhold" <bonefish@xxxxxxxxxxxxxxx> To: <openbeos-build-team@xxxxxxxxxxxxx> Sent: Wednesday, June 26, 2002 1:15 PM Subject: [openbeos-build-team] Re: Detecting libgcc > > On Wed, 26 Jun 2002, David Reid wrote: > > > query -a libgcc.a will work nicely > > > > How do we get that into jam though?? > > No chance, unless we hack a command execution rule into Jam. > BTW, query does only work on BeOS -- not that I personally would care > that much. ;-) > > > The how-to can be just that simple, but it needs to be somewhere so people > > can read it :) > > One of those lazy build team guys should add a ReadMe/Building then. > Err... ;-) > > > Probably also explain how to get Jam and maybe also give some guidance on > > Bochs? > > Bochs. Brilliant idea. Honestly, I hadn't thought of it. > > CU, Ingo > > >