Build Process Description and Workflow

Note: Most notable changes compared to the previous workflow is the deprecation of curabuild-lulzbot and cura-le-build-environment.

CuraLE consists of a Python module in this repository and multiple other dependencies (C++, C++ Python bindings, Python modules) either owned by LulzBot, UltiMaker, or third-parties.

LulzBot-owned repositories which are part of CuraLE will be built and exported with a GitHub Action on a certain repository events, such as a push to a branch. These exported packages and/or binaries can then be used by other repositories when required. This workflow greatly reduces complexity, maintenance and build time.

The figure below shows the sequence diagram for an individual repository.

C++ and C++ Python binding dependencies are now managed by Conan, while the Python modules are managed by Pip. Conan is the orchestrator for the complete installation and setting up the development environment.

All dependencies are built, stored, and used in such away that interaction and 'pollution' of the global system should be non-existant. Installing dependencies for CuraLE and initializing a Virtual Python environment should be as simple as executing a single command in the end.

Cross Dependency Development (All OSs)

Note: This is a work in progress and largely untested at the moment.

When you're working on CuraLE it could be needed to work on other repositories such as UraniumLE and/or CuraEngineLE in parallel. To this end, Conan allows you to put a package into editable mode. Instead of pointing to a Conan package in the local Conan cache, it will point to the working directory of the other repository.

You can find out which version of a package is used by CuraLE by examining the conandata.yml file in the root directory of the repository. The specific data, including the version of a requirment is stored per version key, e.g. curale/5.1.0-beta+1234 will use curaengine/latest@lulzbot/stable

Make sure CuraLE and her dependencies are cloned locally and are located in the same workspace directory.

workspace_root  
|  
└─ CuraLE
└─ CuraEngineLE
└─ UraniumLE
└─ libSavitarLE
└─ libArcusLE
└─ libNest2DLE
└─ pynest2dLE

You can put a dependency, such as CuraEngine, into editable mode by executing the following command in the root directory of CuraEngineLE:

conan editable add . curaengine/latest@lulzbot/stable

If you then perform a new conan install command as usual (See: Initializing a Virtual Python Development Environment (All OSs)) the correct paths should be set for the CuraEngine dependency, and you should be able to develop for CuraLE and CuraEngine simultaneously.