Re: [Pyobjc-dev] Time for a release ?

[Bill B. <bb...@co...>]

That makes sense to me.    It is definitely more useful than the last 
release.

python setup.py sdist  will do the right thing. :-)

I believe that the next step should be to look at replacing all the 
legacy stuff and cleaning up the method dispatch issues....

b.bum


On Friday, April 6, 2001, at 01:43 AM, Steven D. Majewski wrote:

>
> Bill -- I submitted that patch to add ".m" files to python, and
> I got a note it was accepted.
>
> With your changes to use distutils, it ought to build and install
> out of the box on OSX with Python2.1 once it is released.
> ( Which will probably be soon. )
>
> I think it's probably time for us to put out a release.
>
> I changed the #ifdefs, which, because I originally didn't know
> how to test for OSX, were a hack that probably broke the build
> for other platforms.
>
> Now:
>   In ObjC.h, MACOSX is defined if defined(__APPLE__) && 
> defined(__MACH__)
>
>   #ifdef MACOSX is used elsewhere.
>
> I did it that way because I think the __APPLE__ & __MACH__ trick is
> a little too tricky -- I would rather eventually change it so that
> setup adds a -D line with system name.
>
> I tried to make it #define DARWIN at first, but the compiler
> complained about it. Somewhere there is a precompiled header
> that uses DARWIN, but I didn't want to rely on it being defined
> elsewhere until I can find it.
>
> I'll probably try to see if I can shake out any more bugs, and
> then make a tar file and put it on sourceforge as a release.
>
> -- Steve Majewski
>
>
>
> _______________________________________________
> Pyobjc-dev mailing list
> Pyo...@li...
> http://lists.sourceforge.net/lists/listinfo/pyobjc-dev