2010/7/27 Roger Brown <[email protected]>: >>> but if for whatever historical reasons pcsc-lite has "DWORD" in the header >>> file and that ends up to be a 64 bit type on 64bit unix/linux/mac os X >>> machines, so be it. > > On 64bit MacOSX(PCSC.framework) and 64bit Solaris(/usr/include) the > wintypes.h headers make DWORD 32bit. So you have mismatches between common > POSIX 64bit systems.
Exact. > You could have a solution where you build a "libpcsclite.so.2" which exposes > 32bit DWORD but internally is just a shim on "libpcsclite.so.1" which then > talks to pcscd, or judging it's role, call the shim libpcsclite64.so.1. The > next part of the problem is sorting out the ELF linking that still works with > two shared libraries loaded into a single process image which export the same > function names. Bad solution. Just define DWORD to uint32_t and build libpcsclite.so.2. > Out of interest, does the WINE project link to libpcsclite? Good question. I have no idea. Building the wine packages for Debian does not request libpcsclite-dev. That is an indication. But rdesktop [1] does use pcsc-lite and support remote smart card. We are talking about an ABI change, not an API change. Any correctly written application should just need to be rebuild with no change at all. Bye [1] http://www.rdesktop.org/ -- Dr. Ludovic Rousseau _______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
