[jamming] Building Objects - Need to reference with grist when using them in another jam file?
holt.diane at gmail.com
Thu Dec 18 07:24:42 PST 2008
Or just override the Objects rule, if you're going to be doing this for all
your Objects targets.
On Thu, Dec 18, 2008 at 7:23 AM, Diane Holt <holt.diane at gmail.com> wrote:
> Oh, sorry -- I read this too quickly -- I missed that you were building
> them out to PRODUCT_LIB_DIR. In that case, I'd recommend writing a wrapper
> rule around Objects (which I assume is what you're using to compile the
> source files), that sets SOURCE_GRIST to whatever you want it to be. Then
> you can list just the simple filenames in LibraryFromObjects.
> On Thu, Dec 18, 2008 at 6:51 AM, Diane Holt <holt.diane at gmail.com> wrote:
>> I would also ask why you're building your object files out to the source
>> On Wed, Dec 17, 2008 at 11:26 PM, Morgenthaler Björn <
>> bjoern.morgenthaler at comlet.de> wrote:
>>> Thank you for your answers Craig and John.
>>> I know the rule FGristFiles but for my understanding, FGristFiles puts
>>> the current grist to files defined by the SubDir rule.
>>> Like Craig pointed out, I would need to change the SubDir for every
>>> object to use FGristFiles because they're not in the location of the lib. I
>>> thought there might be a more automatic way, jam might be able to resolve
>>> Of cource I also could build with the Library rule or call
>>> LibraryFromObjects in every location of the source files but in my case, I'm
>>> afraight this is no subject of change.
>>> So when I get you right, the only possible way to prevent the hard coded
>>> grist in my scenario is to change the SubDir and use FGristFiles for every
>>> object in a different location then the lib?
>>> jamming mailing list - jamming at maillist.perforce.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the jamming