Re: [Nuke-dev] trouble compiling python extension for Nuke on windows

2016-12-12 Thread Frank Rueter|OHUfx
So I got it to work finally. Some additional confusion was that the official Python 2.7.3 was not compiled with VS2010, so I had to run the compile via Nuke's python interpreter, not the system's one (to avoid having to compile Python myself). So therefore, after installing VS2010, I also had

Re: [Nuke-dev] trouble compiling python extension for Nuke on windows

2016-12-12 Thread Frank Rueter|OHUfx
Thanks Kevin, over at the python list Thorsten suggested the same. This is what I just posted over there (sorry for cross posting, but I'm growing desperate): I tried all day yesterday to install VS 2010 but on both machines I tried it on the installer hangs half way through "Microsoft .NET

Re: [Nuke-dev] trouble compiling python extension for Nuke on windows

2016-12-12 Thread Kevin Wheatley
On 11 December 2016 at 10:03, Frank Rueter|OHUfx wrote: > MSVCR120 I haven't done much Nuke plugin development on Windows recently, but that version of the runtime is from Visual Studio 2012 and from the documentation Nuke needs 2010 for the recent builds, I suspect your python install or defa

[Nuke-dev] trouble compiling python extension for Nuke on windows

2016-12-11 Thread Frank Rueter|OHUfx
Hi all, I am trying to compile a python package for Nuke via Cython. All seems to work well on osx and linux, but on windows I get this error when trying to import the main module from within Nuke (i.e. the parent folder of the main module is added via nuke.pluginAddPath() which shoudl also ad