Fwd: I'd like to reopen discussion on the Windows path problem

[Shun-ichi GOTO]

2007/4/26, Lee Cantey <lcantey at gmail.com>:
> I managed to get the installer working with using the last
> demandimport patch given in bug 457.  I had to make two other changes
> in addition to get the extensions and DLLs bundled in though.  I'm
> posting a new build tonight as it seems to be working for me.
>
> The changes that I needed were:
>
> 1) I seem to have to use --package hgext on the command-line for
> setup.py even though it's listed in setup.py as a package

I'm using attached patch to tell explicitly.
I guess py2exe with demandimport treats hgext/*.py as 'unused'
because they are not called anywhere.

As related topics, building mercurial with python 2.3 + py2exe
does not bundle non-standard codecs, thus fail to execute on Japanese
console. So I always use python 2.4 to build exe.

> 2)  The .pyd files aren't picked up from the build directory so I had
> to copy them into the mercurial source directory and rebuild.

Realy? py2exe (ver 0.6.6) picks 4 pyd modules expectedly for me.
I tried again after removing lib\site-packages\mercurial and get success.

-- 
Shun-ichi GOTO
-------------- next part --------------
A non-text attachment was scrubbed...
Name: py2exe-force-bundle-hgext
Type: application/octet-stream
Size: 683 bytes
Desc: not available
Url : http://selenic.com/pipermail/mercurial/attachments/20070426/364803ff/attachment.obj