12 messages in com.perforce.jamming[jamming] jam's attitude to libraries...
FromSent OnAttachments
Arnt Gulbrandsen19 Mar 2002 07:09 
Matt Armstrong19 Mar 2002 07:55 
Arnt Gulbrandsen19 Mar 2002 08:06 
Matt Armstrong19 Mar 2002 08:45 
Diane Holt19 Mar 2002 09:08 
Arnt Gulbrandsen19 Mar 2002 09:25 
Arnt Gulbrandsen19 Mar 2002 09:29 
Diane Holt19 Mar 2002 09:52 
Arnt Gulbrandsen19 Mar 2002 10:12 
Diane Holt19 Mar 2002 10:31 
EXT-Goodson, Stephen19 Mar 2002 13:01 
Matt Armstrong20 Mar 2002 10:49 
Subject:[jamming] jam's attitude to libraries...
From:Arnt Gulbrandsen (ar@gulbrandsen.priv.no)
Date:03/19/2002 07:09:04 AM
List:com.perforce.jamming

I just converted a project from make.

Preamble:

Once I had removed about 9,000 lines of makefile generation from the makefiles, I was left with something like this:

app: main.c this/libthis.a that/libthat.a other/libother.a ... $(CC) -o app main.c -lthis/this -lthat/that -lother/other ...

That's not syntactically correct, but you get the idea.

Jam doesn't quite like that approach. It builds all the libraries, and it builds the application and links in the libraries, but the dependencies aren't quite what I want.

Question:

I cannot find a pretty way to say that the application depends on $(MYLIBS), so that the libraries must be built first. Hints?

--Arnt