Re: Windows Build of GUI Overhaul Branch
kfj <_kfj <at> yahoo.com>
2012-06-01 07:30:36 GMT
On 28 Mai, 21:48, Matthew Petroff <matt... <at> mpetroff.net> wrote:
> While I included enough of Python for Hugin to run, I did not include
> enough for the Python based features to work.
What is the point? Why don't you just do it like Brian in his Windows
build which he published a couple of days before you? It's a python-
enabled build, so to run it, python has to be installed. Not a
crippled isolated version (which is specifically missing the modules
which would be needed to run the few included plugins), but an
ordinary python install which everyone can get with a few clicks from
python.org. Your minimal python takes up lots of space and has heaps
of totally unnecessary stuff, and if any needed python modules can be
installed into it, it would take some wizardry which is certainly way
beyond the usual mechanism of just picking them up from the 'cheese
shop' (the python package index PyPI).
> I also mistook
> "_hsi.pyd" for a ".pyc" file and accidentally deleted it before
> packaging the build.
Ooops... you happened to forget the core component
If your intention was to provide a demo of the new GUI, you had better
built it without python. Packaging a crippled python interface will
make everyone think it's crap.
> Here is a new build that includes a stripped down
> Python install similar to what is included with Blender or the GIMP
> (the old build only included Python32.dll).