3 messages in com.perforce.jammingBuilding two targets from the same so...
FromSent OnAttachments
Dian...@whistle.com09 Aug 1996 12:38 
Laur...@sybase.com09 Aug 1996 13:39 
Dian...@whistle.com09 Aug 1996 14:58 
Subject:Building two targets from the same source
From:Dian...@whistle.com (Dian@whistle.com)
Date:08/09/1996 12:38:38 PM
List:com.perforce.jamming

Has anyone built two different targets from the same source during the same run of 'jam'? For example, built both a static (.a) and shared (.so) library from the same source? Or two different executables, one compiled -g and built into a "tools" directory, then the .c recompiled w/o the - -g and built into a "release" area.

I've tried lots of different combinations of provided rules, rules I've written, and actions, but the best I can get is close but no cigar. (For example, I can get it to link two different targets, but not to recompile the .o after the first link so the second one ends up just being the same thing. Or I can get it to do 2 compiles, but before it does any linking, so the second compile just overwrites the first, and I still end up with the same 2 executables.)

If I can't get 'jam' to do this, I won't be able to use it, and I'd really like to be able to use it, so if any of you have done this, please let me know. If you need more specific examples, feel free to ask.

Thanks,

Diane