Static Compilation of IronPython scripts

a-foton » Static Compilation of IronPython scripts

a-foton » Static Compilation of IronPython scripts — Wed, 06 Aug 2008 09:36:39 GMT

PingBack from http://blog.a-foton.ru/2008/08/static-compilation-of-ironpython-scripts/

re: Static Compilation of IronPython scripts

Juba17 — Tue, 21 Oct 2008 01:11:51 GMT

Hi.

I made a small tool in Ironpython. Im new to it and when testing everything is ok.

But I've been trying to compile both scripts (program script and form class script without sucess)

I just can't get it to work has a standalone exe. I followed the example above:

import clr

clr.CompileModules("form.dll", "foo.py", "form.py", mainModule="program.py")

And I get the form.dll but then I want to get the executable and I get lost. Saw the pyc example and tried to compile with the pyc but get an error about the CompilerSink.

Could you please point more info on how to compile to exe the applications?

My version is Ironpython v. 2 beta 5

Greetings

re: Static Compilation of IronPython scripts

srivatsn — Fri, 24 Oct 2008 10:03:28 GMT

For creating a exe you have to use the pyc sample like this:

ipy.exe pyc.py /main:program.py foo.py form.py /target:winexe

I suppose this is throwing an error for you. Why don't you send a mail to me via the contact link with the exact error?

re: Static Compilation of IronPython scripts

Juba17 — Sat, 25 Oct 2008 09:30:12 GMT

Sry but can't see contact link. I will post the error:

line:

ipy.exe "D:\IronPython 2.0\Samples\Pyc\pyc.py" /main:"D:\IronPython 2.0\proyeto cod4\warning_system.py" "D:\IronPython 2.0\proyeto cod4\cod4form.py" /target:winexe

error:

Traceback (most recent call last):

File "D:\IronPython 2.0\Samples\Pyc\pyc.py", line 35, in D:\IronPython 2.0\Sam

ples\Pyc\pyc.py

AttributeError: 'namespace#' object has no attribute 'CompilerSink'

re: Static Compilation of IronPython scripts

Juba17 — Sun, 26 Oct 2008 11:45:25 GMT

Yes I checked and pyc can't be used with 2.0 version since the only attributes available in Hosting call are:

['ErrorCodes', 'Python', 'PythonCommandLine', 'PythonConsoleOptions', 'PythonOptionsParser']

So how is the independent executable made after all?

re: Static Compilation of IronPython scripts

srivatsn — Mon, 27 Oct 2008 05:37:39 GMT

Are you using the 1.0 pyc sample by any chance? The sample was updated for 2.0 and is here - http://www.codeplex.com/IronPython/Release/ProjectReleases.aspx?ReleaseId=14353

re: Static Compilation of IronPython scripts

Juba17 — Tue, 28 Oct 2008 00:55:09 GMT

Thanks for your help ;)

I managed to compile it with pyc but I must've misunderstand the topic since when I compiled it still requires python lib and Ironpython dlls.

am I doing something wrong or it's suppose to be that way? I mean to a simple app to distribute I have to included the all of python lib? It's not pratical, I must be wrong.

re: Static Compilation of IronPython scripts

srivatsn — Tue, 28 Oct 2008 01:04:52 GMT

You will require the four IronPython DLLs for the exe to run but you can compile the python libraries along with your py files. It doesn't have to be the entire python library as well- only files that are required by your app.

re: Static Compilation of IronPython scripts

Juba17 — Tue, 28 Oct 2008 03:08:36 GMT

So i need to include in the compile all the regular modules? os, sys, socket, so on? But sometimes they need other modules to run. For instance. When i compiled the last time it required me some modules and other modules those modules run. Isn't there a easy way to know wich one are the sub-modules?

re: Static Compilation of IronPython scripts

srivatsn — Fri, 31 Oct 2008 20:56:49 GMT

There might be some static dependency analysis tools for python out there. I'm not aware of any though.

re: Static Compilation of IronPython scripts

Guy Rozendorn — Thu, 11 Dec 2008 03:19:52 GMT

Hi,

I have written a file called myProg.py, and compiled it to myProg.dll and myProg.exe using the pyc.py example file (using IronPython-2.0).

The thing is that the presence of IronPython.dll and myProg.dll is required in the directory from which I am executing pyProg.exe.

What's the magic I need to make so I could execute pyProg.exe from anywhere (i.e it would search the dlls in the same directory pyProg.exe is in, and not in the directory I'm executing from)?

For example,

pyProg.exe, pyProg.dll and IronPython.dll are in C:\Temp, and I'm doing:

C:\WINDOWS> C:\Temp\pyProg.exe

This doesn't work, because the DLLs are in C:\Temp, and not in C:\WINDOWS.

I want to run pyProg.exe from C:\WINDOWS (or any other directory), but I don't want to copy the DLLs to C:\WINDOWS (or any other directory).

Is this possible?

Is it possible to make compile my ironpython script as a standalone exe? meaning, compiling it to an exe that contains all the code,

re: Static Compilation of IronPython scripts

srivatsn — Tue, 23 Dec 2008 02:05:17 GMT

C:\Temp\pyProg.exe should work since the dependencies are picked up from the directory of the executable as well. If you want to copy pyprog.exe to some other place, you can create a pyprog.exe.config file and use the assemblybinding tag - http://msdn.microsoft.com/en-us/library/twy1dw1e(VS.80).aspx

re: Static Compilation of IronPython scripts

Dinesh Varadharajan — Thu, 05 Mar 2009 09:10:48 GMT

Hi,

we are migrating an existing cpython app to ironpython to work with silverlight. We have so many packages and subpackages in cpython and to work with silverlight we tried to convert them all into a dll.

The dll conversion is fine and all files are part of dll, but all the packages can be referred only from the main module. The modules that are present inside packages are not able to refer any other packages. Are we missing something basic.

IronPython pyc

el blog de cHagHi — Sun, 08 Mar 2009 23:31:27 GMT

Estuve investigando el supuesto camino de pre-compilar módulos para ver si lograba resolver los problemas de performance que mencioné hace unos días. Resulta que la punta del iceberg estaba escondida en el pack de ejemplos de ...

re: Static Compilation of IronPython scripts

srivatsn — Mon, 09 Mar 2009 22:06:06 GMT

Dinesh, packages importing other packages from within the dll should work without any extra work. If you can send me a minimal reproduction of the problem, I can probably be of more assitance. Feel free to use the contact link to e-mail me - http://blogs.msdn.com/srivatsn/contact.aspx