You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allowing the user to target a local/custom Blender executable path would make the local development of this addon faster (don't have to download it all the time --which is a great feature by the way--). It would also some CICD pipelines like Gitlab's to use a custom docker image where Blender is already bundled to not overload the bandwidth.
How
Add a blender_path="" parameter to the main function?
The text was updated successfully, but these errors were encountered:
I second this - downloading multiple Blender versions is essential for CI/CD pipelines, but smaller developers would appreciate an option for using a local existing Blender.
Need
Allowing the user to target a local/custom Blender executable path would make the local development of this addon faster (don't have to download it all the time --which is a great feature by the way--). It would also some CICD pipelines like Gitlab's to use a custom docker image where Blender is already bundled to not overload the bandwidth.
How
Add a
blender_path=""
parameter to the main function?The text was updated successfully, but these errors were encountered: