Thanks guys, yeah the RPC ideia looks more promising.
Magno.
On Thu, 23 Jun 2016 03:54:20 -0400, Ben Dickson <ben.dick...@rsp.com.au>
wrote:
Indeed, doesn't seem practically possible
_>> f, pathname, desc = imp.find_module("nuke",
["/path/to/nuke/9.0v8/lib/python2.7/site-packages/"])
_>> module = imp.load_module("nuke9", f, pathname, desc)
Traceback (most recent call last):
File "stdin", line 1, in <module>
ImportError:
/path/to/nuke/9.0v8/lib/python2.7/site-packages/../../../libnuke-9.0.8.so:
symbol _ZN2DD5Image2Op19DDImage_ABI_9_0_002Ev, version Foundry_1.0 not
defined in file libDDImage.so with link time reference
I suspect even if you tampered with the libraries enough to get around
that problem, there would be a bunch more.. and then it'd probably crash
because of some global state thing anyway..
Would be much more practical to run Nuke 10 in a subprocess and
communicate between the two somehow (e.g
https://github.com/Nvizible/NukeExternalControl or any of the many
generic RPC options around)
On 23/06/16 02:08, Nathan Rusch wrote:
I highly doubt it, to the point of just saying "No". The nuke module
links against a lot of stuff that probably isn't API-compatible between
versions, and (on Linux at least) 9 and 10 are built with different
versions of GCC, so even if they were API-compatible, the 9 library
probably wouldn't be able to load things like DDImage from the 10
installation.
-Nathan
On 6/21/2016 2:37 PM, Magno Borgo wrote:
Would it be possible to import the v9 nuke module into v10? if
possible,
how?
_______________________________________________
Nuke-python mailing list
Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
--
Using Opera's mail client: http://www.opera.com/mail/
_______________________________________________
Nuke-python mailing list
Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
