Glassvision/IfcOpenShell
1
0
Fork 0
mirror of https://github.com/IfcOpenShell/IfcOpenShell.git synced 2026-09-21 08:35:14 +00:00
Code Issues Packages Projects Releases Wiki Activity

Mention builds website in docs.

Browse Source
This commit is contained in:
Dion Moult
2025-01-20 12:15:49 +11:00
parent a65aa92c87
commit 193ff1cd0c
1 changed files with 9 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/bonsai/docs/guides/development/installation.rst
+9 -3
View File
@@ -174,10 +174,16 @@ in the `rem` tags.
After you modify your code in the Git repository, you will need to restart After you modify your code in the Git repository, you will need to restart
Blender for the changes to take effect. Blender for the changes to take effect.
If there are changes to the IfcOpenShell binaries, you may replace the two
``*ifcopenshell_wrapper*`` files with new ones downloaded from the automated
`IfcOpenShell builds directory <https://builds.ifcopenshell.org/>`__.
The downside with this approach is that if a new dependency is added, or a The downside with this approach is that if a new dependency is added, or a
compiled dependency version requirement has changed, or the build system compiled dependency has changed (that is not available via the build
changes, you'll need to fix your setup manually. But this is relatively rare. directory), or the build system changes, you'll need to fix your setup
Reviewing the Makefile history, `here <https://github.com/IfcOpenShell/IfcOpenShell/commits/v0.8.0/src/bonsai/Makefile>`__, is one quick way to see if a dependency has changed. manually. But this is relatively rare. Reviewing the Makefile history, `here
<https://github.com/IfcOpenShell/IfcOpenShell/commits/v0.8.0/src/bonsai/Makefile>`__,
is one quick way to see if a dependency has changed.
.. seealso:: .. seealso::