Ville Skyttä wrote:
> Wouldn't that be the rough equivalent of adding "." to $PATH and/or
> $LD_LIBRARY_PATH, ie. what stuff gets actually used would depend on in which
> dir a command pulling it in would be run? Doesn't sound too good to me when
> thinking about these same headers being installed into system locations...
You may well be right, I'm not sure; my "-I"-fu is a bit rusty these days.
> I suppose a better alternative would be to make opensc's build add an
> explicit -I/path/to/opensc/currently/being/built as appropriate. Unless of
> course it already does, and the problem you see occurs because of something
> else.
Here's what I'm seeing for a recompile of one of the files in the
src/libopensc directory.
gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../src/include
-I/usr/kerberos/include -pthread -I/usr/include/PCSC -I../../src/common
-I../../src/include -Wall -fno-strict-aliasing -g -O2 -MT card-acos5.lo
-MD -MP -MF .deps/card-acos5.Tpo -c card-acos5.c -fPIC -DPIC -o
.libs/card-acos5.o
>From what you're saying, maybe the -I../../src/include option (either of
them!) ought to be making the right thing happen, as that directory does
include an opensc directory containing (soft links to) the appropriate
files. Apparently not, though, and I don't know how to figure out why.
-- Ian
_______________________________________________
opensc-devel mailing list
[email protected]
http://www.opensc-project.org/mailman/listinfo/opensc-devel
