s...@pobox.com schrieb: > >> Requiring that the C++ compiler used to make the dll's/so's to be the > >> same one Python is compiled with wouldn't be too burdensome would it? > > Scott> And what gave you then impression that Python is compiled with a > Scott> C++ compiler? > > I don't think it's too much to expect that a C++ compiler be available for > the configure step if Python is being built in a C++ shop. The C compiler > used to build Python proper should be compatible with the C++ compiler > available to build C++ extension modules or C++ libraries dynamically linked > into Python. > > If there is no C++ compiler available then the proposed layout sniffing just > wouldn't be done and either a configure error would be emitted or a run-time > exception raised if a program attempted to use that feature. (Or the > sniffing could be explicitly enabled/disabled by a configure flag.) >
Hm, on Linux, gccxml (if its version is compatible with that of the C++ compiler) can probably help a lot. At runtime, no configure step needed. Unfortunately not on Windows. Thomas -- http://mail.python.org/mailman/listinfo/python-list
