![]() Mklink /D " %blenderbim% \core" " %cd% \src\blenderbim\blenderbim\core" mklink /D " %blenderbim% \tool" " %cd% \src\blenderbim\blenderbim\tool" mklink /D " %blenderbim% \bim" " %cd% \src\blenderbim\blenderbim\bim" echo Remove the IfcOpenShell dependency Python code. Rd /S /Q " %blenderbim% \core\" rd /S /Q " %blenderbim% \tool\" rd /S /Q " %blenderbim% \bim\" echo Replacing them with links to the Git repository. SET blenderbim = %appdata%\Blender Foundation\Blender\x.x\scripts\addons\blenderbimĮcho Removing the Blender add-on Python code. ![]() rem Put the script to the folder where IfcOpenShell git repository is located rem (script will try to clone IfcOpenShell.git if it's not present). Rem SETUP BLENDER-BIM LIVE DEVELOPMENT ENVIRONMENT rem Setup blenderbim addon location below (probably just need to change "x.x" for your Blender version). Or, if you’re on Windows, you can use the batch script below.īefore running it follow the instructions descibed after rem echo off # Manually download some third party dependencies $ ln -s $PWD/src/ifcfm/ifcfm $BLENDER_ADDON_PATH/libs/site/packages/ifcfm $ ln -s $PWD/src/ifctester/ifctester $BLENDER_ADDON_PATH/libs/site/packages/ifctester $ ln -s $PWD/src/ifcpatch/ifcpatch $BLENDER_ADDON_PATH/libs/site/packages/ifcpatch $ ln -s $PWD/src/ifcclash/ifcclash $BLENDER_ADDON_PATH/libs/site/packages/ifcclash $ ln -s $PWD/src/ifccityjson/ifccityjson $BLENDER_ADDON_PATH/libs/site/packages/ifccityjson $ ln -s $PWD/src/ifc5d/ifc5d $BLENDER_ADDON_PATH/libs/site/packages/ifc5d $ ln -s $PWD/src/ifc4d/ifc4d $BLENDER_ADDON_PATH/libs/site/packages/ifc4d $ ln -s $PWD/src/ifcdiff/ifcdiff.py $BLENDER_ADDON_PATH/libs/site/packages/ifcdiff.py $ ln -s $PWD/src/ifccsv/ifccsv.py $BLENDER_ADDON_PATH/libs/site/packages/ifccsv.py $ rm -r $BLENDER_ADDON_PATH/libs/site/packages/ifcfm $ rm -r $BLENDER_ADDON_PATH/libs/site/packages/ifctester $ rm -r $BLENDER_ADDON_PATH/libs/site/packages/ifcpatch $ rm -r $BLENDER_ADDON_PATH/libs/site/packages/ifcclash $ rm -r $BLENDER_ADDON_PATH/libs/site/packages/ifccityjson $ rm -r $BLENDER_ADDON_PATH/libs/site/packages/ifc5d $ rm -r $BLENDER_ADDON_PATH/libs/site/packages/ifc4d $ rm -r $BLENDER_ADDON_PATH/libs/site/packages/ifcdiff.py $ rm -r $BLENDER_ADDON_PATH/libs/site/packages/ifccsv.py # Remove and link other IfcOpenShell utilities $ ln -s $PWD/src/ifcopenshell-python/ifcopenshell/util $BLENDER_ADDON_PATH/libs/site/packages/ifcopenshell/util $ ln -s $PWD/src/ifcopenshell-python/ifcopenshell/api $BLENDER_ADDON_PATH/libs/site/packages/ifcopenshell/api $ rm -r $BLENDER_ADDON_PATH/libs/site/packages/ifcopenshell/util $ rm -r $BLENDER_ADDON_PATH/libs/site/packages/ifcopenshell/api # Remove the IfcOpenShell dependency Python code $ ln -s $PWD/src/blenderbim/blenderbim/bim $BLENDER_ADDON_PATH/bim $ ln -s $PWD/src/blenderbim/blenderbim/tool $BLENDER_ADDON_PATH/tool $ ln -s $PWD/src/blenderbim/blenderbim/core $BLENDER_ADDON_PATH/core # Replace them with links to the Git repository # default path on Mac: "/Users/ $USER /Library/Application Support/Blender/X.X/scripts/addons/blenderbim" # default path on Linux: " $HOME /.config/blender/X.X/" $ BLENDER_ADDON_PATH = "/path/to/blender/X.XX/scripts/addons/blenderbim" # Remove the Blender add-on Python code You can choose between a PYVERSION of p圓9, or p圓10. You canĬhoose between a PLATFORM of linux, macos, macosm1, and win. You can create your own package by using the Makefile as shown below. Instructions on how toĬompile IfcOpenShell is out of scope of this document. IfcOpenShell (using an IfcOpenBot build) for convenience. The following instructions will use a pre-built Note that the BlenderBIM Add-on does depend on IfcOpenShell, and IfcOpenShellĭoes require compilation. BlenderBIM is coded in Python and doesn’t require anyĬompilation, so this is a relatively easy process. Is possible to make your own Blender add-on from the bleeding edge source code Instead of waiting for an official release on the BlenderBIM Add-on website, it Sometimes, a build may be delayed, or contain broken code. If you are on Blender >=2.93 and <3.1, choose p圓9Ĭhoose linux, macos, macosm1 (for Apple M1 devices), or win ![]() You will need to choose which build to download. The Github releases page, then follow the same That they are typically updated every day. Unstable installation is almost the same as Stable installation, except Packaged installation is recommended for those who use a package manager. Live development environment is recommended for developers who are actively coding. Unstable installation is recommended for power users helping with testing.īundling for Blender is recommended for distributing the add-on. There are different methods of installation, depending on your situation. Toggle table of contents sidebar Installation #
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |