DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to build Loopcut from source to change its add-on with Loopcut

Clone the fork, build the dev app and run the add-on tests to modify Loopcut.

  • Content
  • Advanced
  • 1 hour
  • From the README
  • Any agent

Who it is forA developer who wants to change the Loopcut add-on or the fork itself, and needs a working dev build with tests.

The problemChanging the add-on or the fork needs a local build that reloads the panel and a way to run tests without opening Blender.

The outcomeA dev build of Loopcut is installed and the Blender-free tests run.

What you need first

  • A Mac with Apple silicon or a 64-bit Windows PC (the README lists these builds)
  • An Anthropic key, an OpenAI-compatible key, a local model server such as Ollama, or a Loopcut hosted account
  • Blender scene files you are happy to let the agent modify, since each step runs Python in the open scene

Steps

  1. Clone the repository from https://github.com/Samffprice/loopcut and open the directory on the main branch.
  2. Run make update to fetch Blender's libraries from projects.blender.org.
  3. Run ninja -C ../build/lite install to build the dev app.
  4. Edit the add-on in scripts/addons_core/loopcut/, or run loopcut/scripts/dev.sh to reload the panel when you save a file.
  5. Run python3 -m unittest discover -s loopcut/tests to run the Blender-free tests.

Prompt for your agent

In the Samffprice/loopcut repo, run `make update`, then `ninja -C ../build/lite install`, then `python3 -m unittest discover -s loopcut/tests`. Expect the build to finish and the tests to report a result. Verify that the test run completes without Blender open and report any failing test names.

Caveat. The README gives the build commands but not the system requirements for compiling a Blender fork, so expect a long first build on a machine that already has the needed toolchain.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page