Re: [IronPython] Modifying The PYC Stub EXE

2009-04-06 Thread Dino Viehland
What DLLs you want to be loaded? The reason I ask is that .NET assembly loading doesn't really work on the basis of the current working directory - instead it looks at the app base which by default is where your EXE is located. We do modify sys.path so that IronPython can load things outside

Re: [IronPython] Modifying The PYC Stub EXE

2009-04-06 Thread Davy Mitchell
Hi Dino, All the DLLs are in the Build directory. Everything runs great if the CWD is the folder containing the EXE. If you try and run it from another folder things go wrong (File Not Found Exception). I've posted a basic repro on my Skydrive

Re: [IronPython] Modifying The PYC Stub EXE

2009-04-06 Thread Bruce Bromberek
Davy- I had a similar problem in that the EXE stub built by pyc does not work as expected. My problem was the sys.argv being set to None. As someone who comes to ironpython from Cpython, I want the ironpython equivalent of py2exe where everything just works :) The best advice I've found here

Re: [IronPython] Modifying The PYC Stub EXE

2009-04-06 Thread Dino Viehland
Ahh, I see, you want to add something like: gen.EmitCall(OpCodes.Call, clr.GetClrType(Assembly).GetMethod(GetEntryAssembly), ()); gen.EmitCall(OpCodes.Call, clr.GetClrType(Assembly).GetMethod(get_CodeBase), ()); gen.Emit(OpCodes.Newobj, clr.GetClrType(System.Uri).GetConstructor(