The Filename of a compiled operator or shader in a SPDL file is specified without a path and without an extension. For this reason, when XSI reads the Filename, it could interpret it as either a .SO file or as a .DLL file.
You can create a workgroups and add-on packages that support both Windows and Linux.
Self-installing Plug-ins
Include both the .dll and .so in the same Application\Plugins folder. XSI will ignore .so files on Windows and .dll files on Linux, so there is no conflict.
To package an add-on for both 32-bit and 64-bit Windows, use the extensions “.32.dll” and “.64.dll”, and put both DLLs in the Application\Plugins folder.
Shaders and SPDL-based Operators
Create separate subfolders (such as linux-x86 and nt-x86) for each platform. For example, this is the folder structure for a cross-platform library file:
\Application
\bin
\nt-x86\MyLib.dll
\nt-x86-64\MyLib.dll
\linux-x86\MyLib.so
|
|
The Filename of a compiled operator or shader in a SPDL file is specified without a path and without an extension. For this reason, when XSI reads the Filename, it could interpret it as either a .SO file or as a .DLL file. |
SOFTIMAGE|XSI v.6.01