From: Vladimir Prus (ghost_at_[hidden])
Date: 2007-07-30 05:56:13
Michael Walter wrote:
> On 7/30/07, Vladimir Prus <ghost_at_[hidden]> wrote:
>> Let's put it this way. pkgconfig is capable of expanding 'boost' into
>> a bunch of -l, -L and -I compiler options. pkgconfig is not capable of
>> dealing with variants. Therefore, pkgconfig can be only used when there's
>> "default variant" that can be linked to. On Linux, we can decide what
>> such variant is. I'm not sure such default variant can be easily
>> established on Windows, so pkgconfig is of limited use there.
> How about simply generating the .pc files during the build process?
> Then the user can install whatever they feel is the right default to
> their pkgconfig directory.
Let me ask a straight-forward question. Are you using pkgconfig
on windows, and if so, is the above what you'd do?
My understanding is that right library on windows is highly dependent
on the type of project you're building, so there's no one default
that can be installed and make the user happy.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk