Re: [Pysdl-devel] Distutils Test

[Pete S. <pe...@vi...>]

ok, this has been rattling around my head all day.
i've got to get some ideas out, or my head will bust.

after chewing on the "single binary" idea, i've grown
to dislike it. the main reason that it ties the compile
process way to tightly to its dependencies. there's a
better way.

so i'm putting all that aside and have created a 
new, extremely simple distutil for pysdl that gets
pysdl compiled and linked to its dependencies.
it's pretty cool, and i'll release that here soon.


in the meantime. if you haven't tried it before,
getting all the pysdl dependencies compiled under WIN
is a major chore. none of the packages compile
'out of the box', but need paths changed and flags
altered to get each library happy. i've got a different
compiling script almost done that compiles each library
into its own .DLL and .LIB on windows. i'm just going
to add a little optional glue between this build and
what the pysdl distutil script can use.

i think this is a great way to make everything work.
it doesn't change things too much from how it is now,
the whole process is just simpler and more streamlined

how is the compiling scene under linux? i know it is a
lot smoother, since that's where all the packages are
originally meant to compile (plus linux is much more
compiler friendly). it looks pretty easy to just do a
"./configure;make install" or grab a 'devel' package.
is there any room for improvement getting pysdl started
from scratch?

in any event i'll have distutils working really well
with pysdl, and a cleaner compile pipeline for us WIN
users before the week is out.