At Wed, 27 Jan 2010 12:17:07 +0100, Nicolas Lelong wrote: > > My thought was to leave the library files as-is, and to simply enable > the unit tests on 'toolsets' related to Microsoft compilers, and perhaps > add later other compilers that might support these calling conventions, > based on users needs. > > This way, each user would be free to configure its boost.python > without hassle, and tests would not break on 'uncertified' toolsets.
I'm not sure exactly what "enable the unit tests" means in this case. Can you be explicit and/or preferably provide an illustrative patch? -- Dave Abrahams Meet me at BoostCon: http://www.boostcon.com BoostPro Computing http://www.boostpro.com _______________________________________________ Cplusplus-sig mailing list Cplusplus-sig@python.org http://mail.python.org/mailman/listinfo/cplusplus-sig
