Re: dpkg-cross and -config scripts, (e.g. libusb-config)
> The difficulty is that the program's configure script calls the
> libusb-config script (eg "libusb-config --libs"), but that was removed
> from the .deb by dpkg-cross. (And even if it hadn't been removed I
> guess that it would have reported wrong paths.) It instead picks up my
> native libusb-config and returns "-L/usr/lib -lusb".
Thank you for pointing this out.
I will see what could be done here.
> So, I wonder how best to sort this out. Perhaps dpkg-cross could
> transform libusb-config; it would work if it just replaced /usr/lib with
> /usr/armeb-linux/lib. Perhaps I could replace libusb-config with an
> indirection of some sort to pkg-config.
Difference is that .pc file is a data file, while *-config is an executable
file. So question is - where to put it, how to make it to be used whan
needed and only when needed, etc.