Heikki Toivonen wrote:
On Windows: use ours
Currently there is no reason it has to be so, as we use the same
compiler that official Windows Python was compiled with. So we could
make configure detect Windows Python etc. and have it use that if
available.
Unless there have been major changes in the past few years I don't think
autoconf is usable on Windows unless you are using the cygwin or mingw
compilers. When it is doing checks for availability of libs or specific
symbols it actually makes a small C or C++ file and tries to compile and
link it. The MSVC command-line options are just too different for it to
be able to do the same thing without a ton of work. Also, even if that
hurdle were bypassed somehow there are no standards for where libs or
headers or packages will be installed, so configure would have no idea
where to look for them.
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
