On Feb 1, 2012, at 20:49, Bill Janssen <jans...@parc.com> wrote: > Andi Vajda <va...@apache.org> wrote: > >> Seriously, though, I think that the right thing to do to better >> integrate JCC with distutils/setuptools/distribute/pip/etc... is to >> make it into a distutils 'compiler'. This requires some work, though, >> and I haven't done it in all thee years. Anyone with the itch to hack >> on distutils is welcome to take that on. > > The future here is Python 3.3's "packaging" (aka "distutils2", on > earlier versions of Python): > > try: > import packaging > except ImportError: > import distutils2 > > >> Additionally, issue 43 is all about using the distutils/setuptools >> compiler and linker invocation machinery for building a vanilla shared >> library (as opposed to a Python extension). On linux this is a bit >> cumbersome. On Windows, at little less so. On Mac OS X, it just works. >> >> The alternative would be to write a 'configure' script for that part >> of the JCC build. A configure script would also solve the chicken/egg >> problem of building that library on Windows (the first time, the build >> needs to be done twice for the import library to be in the right >> place). >> >> Currently, I'm leaning towards the configure script solution since >> none of the projects mentioned above seems to have taken issue 43 on >> (by simply integrating my patches) in all these years and Pylucene's >> issue 13 is curently blocked: >> https://issues.apache.org/jira/browse/PYLUCENE-13?focusedCommentId=13162273&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13162273 >> >> I have very little itch to dabble in configure scripts either so I've >> been dragging my feet. If someone were to step forward with a patch >> for that, I'd be delighted in ripping out all this patching >> brittleness. > > I have big chunks of such a configure script written (for Windows/OS > X/Linux) which I'd be happy to contribute.
That would be cool. What are the missing chunks made off ? Andi.. > > Bill
