[openbeos] Re: jam issues
- From: "Andrew Bachmann" <shatty@xxxxxxxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Fri, 16 Jul 2004 17:19:11 -0700 PDT
Hi Gabe,
I would need to look at your situation in context, if you haven't resolved
this issue yet. But it's often sufficient to put your library into the rule
for building your executable like this example:
Addon nv.accelerant : accelerants :
Acceleration.c
<some sources snipped>
SetDisplayMode.c
: false : libnvidia_engine.a
;
Put it at the back where you would put shared libraries. This will
invoke the same processing as the link shared os library rule, which
Axel mentioned earlier and it will probably also work as well.
Andrew
Gabe Yoder <gyoder@xxxxxxxxxxx> wrote:
> Okay, this should be a pretty easy question for our jam gurus. I have a
> directory where the stuff that I build needs to link in a static library
> produced in a neighboring directory. The static library is built using the
> StaticLibrary rule, and I try to link using a rule like
> LinkStaticOSLib foo : libbar.a ;
> (I am writing this from memory, so I might be a little off).
>
> When I build, gcc complains that it can't find libbar.a. I checked in the
> objects directory and traverse down the tree to find that libbar.a exists in
> the directory corresponding to its source directory. I then tried
> specifying ../bar/libbar.a instead of just libbar.a, and that didn't work
> either. Clearly, I need to do something so that it knows where to get the
> library. How can I get it to link in my library?
>
>
> Gabe
>
>
- Follow-Ups:
- [openbeos] Re: jam issues
- From: Gabe Yoder
- References:
- [openbeos] jam issues
- From: Gabe Yoder
Other related posts:
- » [openbeos] jam issues
- » [openbeos] Re: jam issues
- » [openbeos] Re: jam issues
- » [openbeos] Re: jam issues
- » [openbeos] Re: jam issues
- » [openbeos] Re: jam issues
- » [openbeos] Re: jam issues
- [openbeos] Re: jam issues
- From: Gabe Yoder
- [openbeos] jam issues
- From: Gabe Yoder