Re: [Libusb-devel] 1.0.9.rc1

[Chuck C. <cm...@ea...>]

ldd
     libusb-1.0.so.0 => /usr/lib64/libusb-1.0.so.0 (0x00000035fc400000)

the print command yields:
../src/flmidusb.cpp:14:52: error: 'libusb_error_name' was not declared 
in this scope
make: *** [src/flmidusb.o] Error 1

... I use the pkg-config commands to get the header files so, I need to 
go in and figure out
where "make install" put everything, and then tweak my eclipse 
configuration.
------------------------------------------------------------------------
/Charles Cook PhD/ (owner)
Florida Midland LLC <http://cmcook3.dyndns.org/>
Longwood, FL

On 09/15/2011 03:55 PM, Peter Stuge wrote:
> Chuck Cook wrote:
>> Did the pull, make&  install  ---no errors
>> rebuilt my application, again no errors
>> It seems to be working the same as before, which is good, because it
>> was working fine before.
> Sounds good! :)
>
>
>> Question: How do I know if I am using the new library?
> Good question. On Linux you can run:
>
> ldd yourapplicationbinaryhere
>
> That shows which shared objects your application will use when it is
> started.
>
> You can also add a call to one of the new APIs in 1.0.9-rc1 into your
> application, an easy test is to add:
>
>    printf("%s\n", libusb_error_name(LIBUSB_ERROR_IO));
>
> into your code. It should print the unspectacular string
> LIBUSB_ERROR_IO.
>
>
> //Peter
>
> ------------------------------------------------------------------------------
> Doing More with Less: The Next Generation Virtual Desktop
> What are the key obstacles that have prevented many mid-market businesses
> from deploying virtual desktops?   How do next-generation virtual desktops
> provide companies an easier-to-deploy, easier-to-manage and more affordable
> virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/
> _______________________________________________
> Libusb-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-devel
>