Ah, no, I wasn't suggesting rebuilding the dependencies. As to your
automated build process I am wondering why adding the dependencies is
requires a manual step. Is it because config.py prompts for confirmation
when using a prebuilt directory? The Setup file can be reused between
builds.
Lenard
Brian Fisher wrote:
oh it's using setup.py of course.
and it's easy for me to have the automated build use whatever
prebuilts you've got, and I don't have an opinion on any one being
better than another really. The best thing for me would be for there
to be a published and maintained win32 prebuilts zip so I can just
toss it in the right folder if you change anything (like sdl version
rev for instance)
but actually building dependencies myself would be annoying and time
consuming - although I'm sure your script makes it a lot easier, I'm
just not configured for mingw building
On Feb 16, 2008 9:57 PM, Lenard Lindstrom <[EMAIL PROTECTED]> wrote:
There is probably no reason to go with the newer dependencies. But it is
likely best to stick with only one version in official releases. If
there was some subtle bug in the build it has a better chance of
showing up. And it could be that VC programs perform better. But
building the dependencies with VC may be as big an undertaking as
building them with MinGW. As for the automatic build, it is not using
the setup.py script?
