I would like to have an additional houdini.env in the $HSITE and have it applied before or after the $HOUDINI_USER_PREF_DIR/houdini.env
The goal is to have one global env file for setting up shared plugins and one local one for additional per machine settings. Hope I'm making myself clear.
I'm on a Windows system if that has any relevancy here.
Multiple houdini.env files possible?
2711 4 1- draxysd
- Member
- 3 posts
- Joined: Aug. 2012
- Online
- dagoose
- Member
- 8 posts
- Joined: Jan. 2014
- Offline
- old_school
- Staff
- 2540 posts
- Joined: July 2005
- Offline
The short answer is you need to work with Houdini's configuration source launch file. Extend it to support beyond $HSITE, say $HSITE_SITE and $HSITE_CUSTOM .
This is all done in your houdini install directory: C:\Program Files\SideEffects Software\Houdini 19.0.513
This is where all the houdini configurations start. It's where the initial configuration is set.
The main use of houdini.env by users is to extend Houdini's own search path which starts with $HOUDINI_PATH and then cascades down form there into the various different components.
https://vfxbrain.wordpress.com/2019/11/20/hudini-env-file-on-windows/ [vfxbrain.wordpress.com]
Then figure out a way to push this out and maintain. On Linux you use shells and all this is in a typical day.
On windows, nope, rarely done.
----
There is another way to extend Houdini and that is to directly reference locations and files using Houdini "packages".
Because of the difficulty in setting up good Houdini environments on Windows in a robust way including the limitations of houdini.env files, we added Packages:
https://www.sidefx.com/docs/houdini/ref/plugins.html [www.sidefx.com]
https://www.sidefx.com/tutorials/houdini-environment-setup/ [www.sidefx.com]
The new installer also allows you to manage and install packages, especially handy for windows configurations:
https://www.sidefx.com/docs/houdini/ref/utils/launcher.html [www.sidefx.com]
I think we should get rid of the Beta in the doc... I'll check on that. To see if it indeed is still in beta.
Move to packages. Full stop. Your life becomes so much easier managing environments on windows imho.
This is all done in your houdini install directory: C:\Program Files\SideEffects Software\Houdini 19.0.513
This is where all the houdini configurations start. It's where the initial configuration is set.
The main use of houdini.env by users is to extend Houdini's own search path which starts with $HOUDINI_PATH and then cascades down form there into the various different components.
https://vfxbrain.wordpress.com/2019/11/20/hudini-env-file-on-windows/ [vfxbrain.wordpress.com]
Then figure out a way to push this out and maintain. On Linux you use shells and all this is in a typical day.
On windows, nope, rarely done.
----
There is another way to extend Houdini and that is to directly reference locations and files using Houdini "packages".
Because of the difficulty in setting up good Houdini environments on Windows in a robust way including the limitations of houdini.env files, we added Packages:
https://www.sidefx.com/docs/houdini/ref/plugins.html [www.sidefx.com]
https://www.sidefx.com/tutorials/houdini-environment-setup/ [www.sidefx.com]
The new installer also allows you to manage and install packages, especially handy for windows configurations:
https://www.sidefx.com/docs/houdini/ref/utils/launcher.html [www.sidefx.com]
I think we should get rid of the Beta in the doc... I'll check on that. To see if it indeed is still in beta.
Move to packages. Full stop. Your life becomes so much easier managing environments on windows imho.
There's at least one school like the old school!
- DJ_Dhrub
- Member
- 4 posts
- Joined: Sept. 2016
- Offline
I have tried to create an article regarding that, feel free to have a look, hope it will help.
Article [andcgi.medium.com]
Article [andcgi.medium.com]
- mabelzile
- Staff
- 396 posts
- Joined: Feb. 2018
- Offline
DJ_DhrubThe path keyword is a shortcut for appending elements to HOUDINI_PATH, as you pointing out elements are prepended by default. You can have more control on how to set path like this
I have tried to create an article regarding that, feel free to have a look, hope it will help.
Article [andcgi.medium.com]
{ "path" : [ { "value" : "/user/bob/libs", "method" : "append" }, "/user/tom/libs", "/user/sam/libs" ] }
Or with the env keyword like this
{ "env": [ { "HOUDINI_PATH" : [ "$BOB/libs", { "value": "$BOB/test", "method": "append" } ] } ] }
-
- Quick Links