Ingo, Go ahead and add the bits to Jam if you feel it'll work :) Also Readme sounds like a good idea. david ----- Original Message ----- From: "Ingo Weinhold" <bonefish@xxxxxxxxxxxxxxx> To: <openbeos-build-team@xxxxxxxxxxxxx> Sent: Thursday, June 27, 2002 11:48 AM Subject: [openbeos-build-team] Re: Detecting libgcc > > On Wed, 26 Jun 2002, David Reid wrote: > > > 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? > > The question is how to include it in the build. The only way I see, is to > included it in the actions of the rules where they are needed, like `cat > openbeos.inc`. Do I have to say, that I find this very ugly? > > Please, let's add a built-in Jam rule for executing commands at parsing > time. Such a thing is really missing (at least when comparing it to make). > I reckon, the `src/tools/jam' directory is not just for fun in the new > tree. > > Regarding the ReadMe file: unless someone objects I'll go add a short one > this evening/night. I tested BeBochs and it works fine (though slow -- I > hope due to the emulation and not because the kernel is a snail ;-) and > thus will also add a respective section. > > CU, Ingo > > >