Thanks for that, I like the layout of your json.
It still adds the ‘:&’ to the end of the value in centos7, doesn't have this problem in Windows though.
I've created a bug report, it's not an issue as the documentation states to add it to the env file and that's what I'm doing for now.
Found 2 posts.
Search results Show results as topic list.
Technical Discussion » Trouble setting up a package when is contain "Perforce"
- anthonygelatka
- 2 posts
- Offline
Technical Discussion » Trouble setting up a package when is contain "Perforce"
- anthonygelatka
- 2 posts
- Offline
I'm having a similar issue while switching from houdini.env to packages, but only for optix (I have at least 10 others with same path working ok)
I have an optix.json in ~/packages with the following
I tried shortning the path
from
/central/sw/houdini/plugins/optix/linux
to
/central/sw/optix/lin/
Still get the issue where is adds
Houdini DSO error on ‘/central/sw/optix/lin/:&/liboptix.so’
/central/sw/optix/lin/:&/liboptix.so: cannot open shared object file: No such file or directory
works fine if I stick it in the houdini.env file
Houdini 17.5.391 on Centos7
I have an optix.json in ~/packages with the following
{
"env" :
[
{
"HOUDINI_NVIDIA_OPTIX_DSO_PATH":"/central/sw/houdini/plugins/optix/lin/"
}
]
}
I tried shortning the path
from
/central/sw/houdini/plugins/optix/linux
to
/central/sw/optix/lin/
Still get the issue where is adds
:&into the path
Houdini DSO error on ‘/central/sw/optix/lin/:&/liboptix.so’
/central/sw/optix/lin/:&/liboptix.so: cannot open shared object file: No such file or directory
works fine if I stick it in the houdini.env file
Houdini 17.5.391 on Centos7
-
- Quick Links