On Mon, Jun 20, 2011 at 4:07 AM, Uwe Bonnes
<bon@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
> I see a lot of constructs like
> /usr/include/<libname>-x.y/<libname>/<include files>
> on my system
Even then, the question may come back to what is the intention
of libftdi-1.0?
Is the intention to replace libftdi-0.1x, then it is probably a better
idea to put it in the same location. Right now only one can exist
in the same place (/usr or /usr/local) anyway -- they can not coexist
under /usr. I suspect this is the original intention and then it is
better to be compatible with libftdi-0.1x and put the header in
the same place.
Is the intention not to replace libftdi-0.1x but create a new library,
in that case, it is better to rename the header file so that it
can easily coexist with the old library.
--
Xiaofan
--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx
|
