Re: [Boost-build] discovering libraries with boost at build time

Subject: Re: [Boost-build] discovering libraries with boost at build time
From: Artyom (artyomtnk_at_[hidden])
Date: 2010-07-09 14:49:22

> 
> >> > I still do not support  BBv2 for Boost.Locale even in the  release for > 
>review
> >> > for one  simple
> >> >  reason - there is no even way to do something like find_library,   or
> >> > find_path.
> >> 
> >> exactly which libraries  you need to  search?
> > 
> > I need to search for ICU, and it does  not supported by pkg-config and
> > pkg-config is not an option for "Native  Windows" developers (a.k.a. MSVC 
>users).
> > 
> > Before you mention  that Boost.Regex uses ICU, it indeed uses it but:
> > 
> > - If fails to  find correct library under MSVC debug builds and links with
> > release  onces.
> 
> That should be fixed in both Trunk and Release.

At least this wasn't when I looked for ICU configuration.

> 
> >   This is actually a bug. But unlike for Boost.Regex where ICU is totally
> >  optional, for Boost.Locale
> >  it is quite central part.
> > 
> > - It searchs for library manually, I mean it looks for a file like 
>libicuuc.so
> > or  cygicuuc.dll or
> 
> Not really any more - it's more like an autoconf-like  approach now that 
>Boost.Build
> supports configuration-like options - take a look  at the current Regex Jamfile 
>
> and see if it matches your needs at  all.

Not exactly, according to the code I see you actually require from user to 
provide
the option for ICU. autoconf indeed provides such option for various libraries
for purpose of searching for them in non-standard location. By defauly, autoconf 
just
find them.

So, technically you hadn't solved the problem - you had written a work around 
for limitation
of build system and gave it to user - let him find the library, provide the path 
and turn
feature on or off according to if the library installed or not.

Sorry, I don't see this as solution, it is just a workaround.

Artyom