[openbeos] Re: build problems
- From: "Cedric Degea" <cdegea@xxxxxxxxxxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Fri, 12 Jul 2002 20:37:15 +0200
>> Building media_server and media_addon_server by invoking jam
>> from the top level in /current works fine.
>> But if I try to build it independently by executing jam in
>> /current/src/servers/media I get:
>>
>> $ jam
>> don't know how to make libmedia.so
>That is an unfortunate limitation of Jam. It reads only the Jamfiles in
>the current directory and its subdirectories (if included). Thus it
>doesn't know about libmedia.so when you build in src/servers/media.
>
>To fix this problem we need to modify Jam's standard rules defined in
Ok I'll bite...
Preamble(!):
* I know next to nothing about the soruce tree (lurker)
* I know next to nothing about what specific usage of Jam is done
here in the OBOS build system.
Now with the meat:
talking in the abstract, for the reasons above, I'd take
this build system thinggie as I take code: do it "top down"!
I.e. (no offense intended) if you have a Jamfile in a subdir
that depends on a file build with another jamfile above itself,
then it's like spaghetti code. Or spaghetti building.
So, is my mail totally irrelevant or not ? Out of the blue that's
the "analysis" I'd gather from the initial post in this thread.
PS - someone mentionned missing "references" headers; unless
the header is totally missing from the mail headers I'd wagger
it's maybe related to people who subscribe in "digest" mode
and thus start a "new" thread when they reply to a post on
this ML. If that turns out to be the case, not much can be done.
--
PGP key: http://cdegea.free.fr/degea_kagi_pubkey.txt | BeDev E-16870
"What's oil got to do, got to do with it" -- F02 Chorus
Other related posts:
