RFC: Alternative for exemaker

[Mads Kiilerich]

Adrian Buehlmann wrote, On 06/29/2012 01:28 AM:
> On 2012-06-29 01:03, Mads Kiilerich wrote:
>> Matt Mackall wrote, On 06/27/2012 03:00 AM:
>>> My only concern with using this for HackableMercurial is how it will
>>> find the Python DLL we ship.
>> I think we will need something similar to how exemaker parses the first
>> '#!' line of the py script and uses it find the DLL. That would also
>> help us cover the 'hackable' use case where Python isn't installed in
>> PATH but hg.exe somehow is.
> What's the problem with having the pythonXX.dll next to the exe?

That might work too - I don't know.

But I assume that the python main module (by default) finds all the 
support files and libraries by looking for them relative to the dll - I 
don't see how else it should be able to find them.

Placing python dll next to hg.exe (or the other way around) (or in PATH) 
will perhaps work for 'hackable' and when Python is installed and in 
PATH, but I can imagine other setups where Python is somewhere but 
intentionally not in PATH but the user wants hg.exe in PATH.

/Mads