Hi,
I'm getting this same error with any inlinecpp attempts in Python operators. MSVCDir is set to VC9 and the HDK is building samples fine - is there a step I've missed for compiling inline code?
(this is Houdini 12.5.506 in Win7 64)
The following code example raises the same error:
import inlinecpp
mymodule = inlinecpp.createLibrary(“test”, function_sources=[“”“
int doubleIt(int value)
{
int x;
return value * 2;
}
”“”])
print mymodule._compiler_output()
Searching online, it seems to be a 32bit->64bit issue, but I can't get any straight solutions deeper than that.
I'd be grateful for any help or advice in setting the environment up correctly. Windows is such a pain sometimes.
Cheers
Python inlinecpp: Windows error2: 'The handle is invalid'
3119 7 0- AdamT
- Member
- 184 posts
- Joined: June 2010
- Offline
- Anonymous
- Member
- 678 posts
- Joined: July 2005
- Offline
- AdamT
- Member
- 184 posts
- Joined: June 2010
- Offline
- Anonymous
- Member
- 678 posts
- Joined: July 2005
- Offline
- AdamT
- Member
- 184 posts
- Joined: June 2010
- Offline
- Anonymous
- Member
- 678 posts
- Joined: July 2005
- Offline
- AdamT
- Member
- 184 posts
- Joined: June 2010
- Offline
This is 64bit Windows 7, and the compiler path is:
C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\bin\amd64\cl.exe
…as installed by Windows SDK (3.51 framework)
I can only assume it's fine sitting in the x86 program files structure (since you can't install anywhere else). The HDK seems to be fine with it building from hcustom.
C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\bin\amd64\cl.exe
…as installed by Windows SDK (3.51 framework)
I can only assume it's fine sitting in the x86 program files structure (since you can't install anywhere else). The HDK seems to be fine with it building from hcustom.
- AdamT
- Member
- 184 posts
- Joined: June 2010
- Offline
Ah, ok that's a bit weird. I was going to export a sample file, but discovered…
It works if I run Houdini from a shortcut - the error only appears if I launch it from Command Line Tools (which is how I have it set to run by default).
So, good news and odd news! (is this expected behaviour, or a bug?)
Thanks for your help, even if success was a bit random I'd probably never have ran it outside command line otherwise! ;-)
It works if I run Houdini from a shortcut - the error only appears if I launch it from Command Line Tools (which is how I have it set to run by default).
So, good news and odd news! (is this expected behaviour, or a bug?)
Thanks for your help, even if success was a bit random I'd probably never have ran it outside command line otherwise! ;-)
-
- Quick Links