Hi Ludovic, we have copies of those m4 macro packages, so that developers that don't have them can still develop opensc without installing them first.
I'm ok with updating them or dropping them in favor of requireing everyone to have them. I have no clue why gettextize is required. I never run it and didn't see any error or warning indicating that I should. maybe it has something to do with your autoconf/make/libtool versions? I know that latest automake(2.10?) seems to be incompatible with opensc, no idea why, but the debian/ubuntu automake 2.9 packages work fine. what do you suggest, how shall we proceed? personally I'd like to investigate cmake. if we can use that for our windows build it would help a lot, as it can create visual studio project files, and that way we can create debug versions too and use the visual studio for debugging etc. (something I have absolutely no clue about - but people tell me with a visual studio project and a debug build it should be much easier to find a bug). if cmake works out for the windows build we can consider it for linux/unix too. but we are quite far away from that point. I only mention it so in case we would need to invest lots and lots of time on automake, we could check that alternative. Regards, Andreas _______________________________________________ opensc-devel mailing list [email protected] http://www.opensc-project.org/mailman/listinfo/opensc-devel
