Skip to content

Include Python.Runtime.dll in scripts directory in the wheels #26

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
davidanthoff opened this issue Mar 18, 2014 · 2 comments
Closed

Include Python.Runtime.dll in scripts directory in the wheels #26

davidanthoff opened this issue Mar 18, 2014 · 2 comments
Labels
Milestone

Comments

@davidanthoff
Copy link
Contributor

nPython.exe as installed by the wheels doesn't work because it doesn't find the runtime dll. I think the correct solution is that the wheel places two copies of the runtime dll in the python dirs: one in the scripts directory and one in the site-packages location.

@davidanthoff davidanthoff added this to the 2.0.0 Beta 1 milestone Mar 18, 2014
@davidanthoff davidanthoff changed the title Include Python.Runtime.dll in scrips directory in the wheels Include Python.Runtime.dll in scripts directory in the wheels Mar 18, 2014
@tonyroberts
Copy link
Contributor

Just came across this: http://research.microsoft.com/en-us/people/mbarnett/ILMerge.aspx
Might be neater to package npython as a single binary to avoid mismatching versions getting accidentally installed.

@tonyroberts
Copy link
Contributor

This is probably a better bet since ILMerge apparently doesn't work on mono:
http://blogs.msdn.com/b/microsoft_press/archive/2010/02/03/jeffrey-richter-excerpt-2-from-clr-via-c-third-edition.aspx

I'll take a look at doing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants