Building LuxCoreRender: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 15: | Line 15: | ||
pylux(pyluxcore.so) | pylux(pyluxcore.so) | ||
end | end | ||
style sb1 fill:# | style sb1 fill:#ffffffff,stroke:#333,stroke-width:4px,stroke-dasharray: 5 5 | ||
subgraph Python Wheels | subgraph Python Wheels | ||
Revision as of 20:36, 18 April 2025
This page is under construction
Build targets
LuxCoreRender contains multiple targets:
Dependencies
Libraries:
- luxcore
- pyluxcore
LuxCore Python Wheels
Samples
- luxcoreui
- luxcoreconsole
Plugins - BlendLuxCore - <app plugins>
Pyluxcoretools
Building LuxCore Dependencies
Principles
LuxCore dependencies are built by LuxCoreDeps.
The process is:
- LuxCoreDeps populates a Conan cache by building each of the required dependencies from its sources.
- This cache is published in LuxCoreDeps releases.
- On LuxCore side, during the build, the cache is retrieved from the release and made available (restored) for LuxCore build.
Central build
LuxCoreDeps is intended to be run by Github CI/CD pipeline.
You will find all workflows in repository actions.:
- LuxCore Dependency Builder: build dependencies, triggered on-demand
- LuxCore Dependency Checker: test dependency build, triggered by push (call Builder)
- LuxCore Dependency Releaser: publish release of dependencies
In a typical workflow: Testing: Releasing
Local build
Local build is