Jump to content
Sign in to follow this  
JoshJ

cvex file reloading in standalone application

Recommended Posts

I'm experimenting with processing data with cvex in a standalone application.  Everything is working except for the following issue:

Reloading an existing .vfl file doesn't seem to update.  Loading a new .vfl file does update.

 

Explanation:

 

I load and run a hand-coded cvex .vfl file, then modify the .vfl file and resave.  My application releases and cleans up the objects which held the cvex contexts, then creates new cvex contexts and loads the updated .vfl file.  However, the cvex processing doesn't reflect the new resaved .vfl file, it still runs the originally loaded code.  If I resave the .vfl file as a new name, and load that new file, the processing updates as expected.

 

I've tried running cvex_context::clearAllFunctions(), but whether I call it in the destruction of the old cvex contexts, or right at the creation of new cvex contexts, I have only had it result in a crash.

 

 

Share this post


Link to post
Share on other sites

I've experienced the same issue with vexexec utility! I think this is a bug and should be reported.

Share this post


Link to post
Share on other sites

well, even with inlinecpp (using python and ctypes), it looks like a new library name with a random string is created and reloaded.  Is this a limitation of c or c++ itself, which prevents easy reloading of dynamic libraries?

 

or is it a limitation of the way its implemented in houdini?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×