inter directory dependencies (faq?) - Phil...@autologue.com - com.perforce.jamming

11 messages in com.perforce.jamminginter directory dependencies (faq?)

From	Sent On	Attachments
Chri...@ips.cs.tu-bs.de	09 Dec 1998 00:24
Phil...@autologue.com	09 Dec 1998 10:50
'Chr...@ips.cs.tu-bs.de	09 Dec 1998 23:53
Chri...@ips.cs.tu-bs.de	10 Dec 1998 01:41
Iain...@mcclatchie.com	10 Dec 1998 02:00
"Cowham, Robert Associate CowhamR@logica.com	10 Dec 1998 02:03
Iain...@mcclatchie.com	10 Dec 1998 13:01
Chri...@ips.cs.tu-bs.de	11 Dec 1998 01:17
Iain...@mcclatchie.com	11 Dec 1998 12:57
Chri...@ips.cs.tu-bs.de	13 Dec 1998 07:19
Laur...@perforce.com	14 Dec 1998 12:59

Subject:	inter directory dependencies (faq?)
From:	Phil...@autologue.com (Phil...@autologue.com)
Date:	12/09/1998 10:50:52 AM
List:	com.perforce.jamming

This is easy, so I'll attempt it.

First, I'll assume that $(TOP)/Jamfile includes $(TOP)/thelib/Jamfile and $(TOP)/theapp/Jamfile. Then your all you need in $(TOP)/theapp/Jamfile is:

LinkLibraries theapp : thelib ;

The key is that *EVERYTHING* should be visible from $(TOP)/Jamfile.

-----Original Message----- From: Christian Lindig [mailto:lin...@ips.cs.tu-bs.de] Sent: Wednesday, December 09, 1998 12:25 AM To: Jam Mailing List Subject: inter directory dependencies (faq?)

Since I'm new to Jam my question might be a FAQ - I have quickly checked the archive but did not find an answer. The question is related to multiple directory projects: the Jamfile in each directory helps to get the dependencies right inside every directory - but how do I specify inter directory dependencies? The Jam documentation explains how to set up Jamfiles for a source tree but examples there are not inter directory related. Example:

A library `thelib.a' is made of l1.c l2.c l3c. The application `theapp.exe' is made of a1.c a2.c and thelib.a. Library and application source code reside in different directories:

top/thelib/thelib.a /l1.c /l2.c /l3.c /theapp/a1.c /a2.c /a3.c /theapp.exe

How do I specify in top/theapp/Jamfile that theapp.exe requires thelib.a from the library directory? Using the pseudo target `lib' might be a solution in this special case but how to do it in general?

-- Christian