Build Bforartists, and help shape it.
Everything you need to compile Bforartists from source, find your way around the code, and send your first change.
Your first build
1
Get the code
Clone the Bforartists repository from GitHub, or fork it to send changes back.
2
Set up your tools
Git, CMake and a C++ compiler, plus the precompiled libraries for your system.
3
Build and run
Compile, start your build, and compare it with the official release.
The handbook
What is in it
Guides move here from the old handbook as they are rewritten. The Windows build guide is ready now.
Developing with GitHub
Branches, pull requests, and merging the latest Blender changes.
Official releases
How a release is built, tested and published.
Icons
Add new icons and update the tool shelf icons.
Defaults
Change the default theme, hotkeys and font.
Interface code
Tooltips for operators, list rows, and adding a new editor.
House rules
Before you send a change
Talk first
Open an issue or a discussion before big work, so nobody builds the same thing twice.
Follow the seven rules
Every interface change answers to them: top level access, iconography, customisable, discoverable, consistent, documented, less hits.
Stay Blender-compatible
Files saved in Bforartists must keep opening in Blender, and the other way round.
One change per pull request
Small, focused changes are reviewed and merged faster.