On Mon, Sep 3, 2012 at 10:57 PM, xantares 09 <xantares09@xxxxxxxxxxx> wrote:
>> On Mon, Sep 3, 2012 at 6:16 PM, xantares 09 <xantares09@xxxxxxxxxxx>
>> wrote:
>> > Spotted another one: shouldn't 'libftdi-config --libs' return the usb
>> > libraries ? Before configuring, it seems LIBS is empty.
>>
>> It seems to be okay to me since now 'libftdi-config --libs' returns
>> '-L/usr/local/lib -lftdi1' which should be correct.
>>
>> But if you want to point the user for possible static linking,
>> then yes libusb-1.0 library should be included for that,
>> supposedly it can be something like this.
>> https://github.com/libusbx/libusbx/blob/master/libusb-1.0.pc.in
>> But I just tried to use "pkg-config --static libusb-1.0" and yet
>> it returns nothing under my Mac OS X machine.
>
> Shouldn't it be the contrary ?
> I mean if you want to build a shared library, you have to pass all the
> libraries containing the dso reference.
> And if you build statically, all the symbols are included and you don't have
> to pass any other libraries to link to.
I am not an expert here but here are two links from libusb
mailing list, saying to include the extra libraries in Libs.private
in the pc file.
http://libusb.6.n5.nabble.com/libusb-1-0-pc-files-when-static-linking-td43.html
http://libusb.6.n5.nabble.com/How-to-use-static-linking-with-libusb-td5104747.html
--
Xiaofan
--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx
|
