Custom VEX operator

[raytheon]

hi all..

I've run hcustom on VEX_Ops.C on ubuntu karmic koala 64-bit and it compiles properly (i did add an include for UT_DSOVersion.h and changed the scope of getpid() to VEX_ALL_CONTEXT). I tried creating a new VEX geometry operator type and entering code with a call to getpid() but vcc cannot find a definition for it. The newVEXOp() function in VEX_Ops.C is not getting called.

Is there something i'm missing? Maybe i'm not testing it correctly .

thanks

[raytheon]

Just as a check i compiled the SOP_Star example and it works fine. LD_DEBUG shows that the both sop and vex shared libraries are loaded by Houdini but a breakpoint set in newVEXOp() never triggers, though a breakpoint in newSopOperator() is hit. The LD_DEBUG logs (i've attached the entries which mention the sop and vex shared libraries) show that Houdini is checking for newVopOperator, newSopOperator, and a number of similar symbols, but never checks for newVEXOp. Has anyone been able to get the VEX_Ops example working on Ubuntu Koala 64-bit? Is there any additional information which might help to resolve this?

thanks!

sop.txt

vex.txt

[mrice]

Each vex library needs a corresponding entry in a VEXdso file. I think its a way of making sure things aren't too easy.

There's an example in $HFS/houdini/vex

Also a bit of info here

[raytheon]

Thanks.. that fixed it! The LD_DEBUG log now shows that Houdini is hooking newVEXOp. I had seen the section on index files earlier, but blitted over it because the word "obsoleted" is in bold in the first sentence .

Digging into it a bit further, there is $HFS/houdini/vex/dso/VEX_VexOp.html, which is quite detailed. This content doesn't seem to be indexed by google.

It would be nice if the VEX_Ops sample included a VEXdso file or a readme.