On Monday 19 February 2007, Ian Young wrote: > The problem is that many of the opensc source files, but particularly > opensc.h, include files like this: > > #include <opensc/scconf.h> > #include <opensc/errors.h> > #include <opensc/types.h> > > Unfortunately, the <...> means to pick these files up from the globally > installed version of opensc, not the version I'm trying to build. This > caused a problem in my case because the value of SC_MAX_ACL_OPS has > changed since the FC6 packages were created. > > I solved this problem in opensc.h by changing these #includes to: > > #include "opensc/scconf.h" > #include "opensc/errors.h" > #include "opensc/types.h" > > This means search for these files locally, falling back to <...> if the > local versions can't be located, which seems right for a development > environment. > > Can anyone think of any disadvantage to making this change throughout > the opensc sources?
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... 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. _______________________________________________ opensc-devel mailing list [email protected] http://www.opensc-project.org/mailman/listinfo/opensc-devel
