Re: [jamboost] V2: using pre-built libraries suggestion

From: Vladimir Prus (ghost_at_[hidden])
Date: 2004-02-13 07:13:29

Hi Reece,

> > exe main : main.cpp /usr/lib/somelibrary.a
> >
> > : <find-library>z <library-path>/opt ;
> >
> >to work?
>
> This would be useful. Also, it would be helpful to specify the search
> directories, so you can do:
>
> exe myapp : main.cpp user32.lib atl.lib ... urlmon.lib
>
> without specifying the absolute path all the time. This would also allow
> you to change the location of the libraries when upgrading or switching to
> a different compiler (e.g. using the Windows SDK on Borland or GCC).

That should be possible with <library-path>. For example

project
: requirements <library-path>C:/windows # or whatever
;

> >What do you think?
>
> I think your idea would be the best approach *if* you can get search
> directories working (ideally configurable for different toolsets, e.g. gcc,
> borland, metrowerks, etc.). 

I think proejct requirements combined with conditional requirement will give 
you what you're after:

... requirements <toolset>msvc:<library-path>whatever ;

> That way, it will behave in a manor similar to
> my approach, but without the need to add an alias/lib for each available
> library.

There's one drawback with this approach. If one day you find that a library is 
not avaliable on a given platform and must be built from sources, you can't 
simply change the definition of a target. This might not be critical.

- Volodya