Yes, but the ObjectCc/C++Flags is *limited* to single object files, and the jam build system is used explicitly to avoid using things such as CCFLAGS. On Tue, Apr 22, 2008 at 1:33 PM, Ingo Weinhold <ingo_weinhold@xxxxxx> wrote: > > On 2008-04-22 at 18:37:09 [+0200], Duane Ryan <bailey.d.r@xxxxxxxxx> > wrote: > > I was piddling around, trying to get Python to conform to the jam build > > system. So far it's been a good experience, though it would have helped > if > > there were documentation about Haiku's build system ( > > http://dev.haiku-os.org/ticket/2120 ). > > If there was only someone to write it... :-) > > > Anyway, I have just one suggestion: > > per-target build flags. So instead of <name> : <sources> : <libraries> > : > > <res> : [<flags>] ; This means that if you are building two different > > executables in the same directory you can also specify separate build > flags. > > > > If there's already a way to do this, forgive me for suggesting this. :P > > There are at least two ways to achieve that. There are the ObjectCcFlags > and > ObjectC++Flags rules, which allow you to add flags for individual object > files even. Another way is to set the CCFLAGS/C++FLAGS variables: > > CCFLAGS = ... ; > C++FLAGS = ... ; > Application app1 : ... ; > > CCFLAGS = ... ; > C++FLAGS = ... ; > Application app2 : ... ; > > CU, Ingo > >