Tough path head for non-Windows deployment...
Looking at subprocess.py saw that it calls into _suprocess, which is a
wrapper for Win32 calls over interop. After being done with the
directory structure, some code will still blow up because of direct
reliance on things like
DllImport("kernel32.dll", EntryPoint = "CreateProcess"...
I wonder how wide-spread this practice is in Iron*.
Daniel.
On Fri, Feb 11, 2011 at 19:23, Tomas Matousek
<[email protected]> wrote:
> Might be. You can compare your layout with the one for Windows - this zip
> file has the right layout:
>
> http://ironruby.codeplex.com/releases/view/55250#DownloadId=206131
>
> Just exclude .bat files and Samples, Silverlight and WP7 directories.
>
> Tomas
>
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On Behalf Of Andrew Jorgensen
> Sent: Friday, February 11, 2011 7:14 PM
> To: Discussion of IronPython
> Cc: [email protected]
> Subject: Re: [IronPython] Contents of Lib (packaging for RPM)
>
> On Fri, Feb 11, 2011 at 8:03 PM, Tomas Matousek
> <[email protected]> wrote:
>> Yes, but the .config file doesn't need to be there at all. "../Lib" is the
>> default value.
>>
>> The files in Config directory are for development env only.
>
> Ah, see I was just copying all the contents of bin/<Configuration> to
> /usr/lib/ironruby
>
> Are there other files I should /not/ be installing?
> _______________________________________________
> Users mailing list
> [email protected]
> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
>
> _______________________________________________
> Users mailing list
> [email protected]
> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
>
_______________________________________________
Users mailing list
[email protected]
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
