Building LuxCoreRender: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
Line 6: | Line 6: | ||
<TODO: Show it as a graph when Diagrams extension is enabled> | <TODO: Show it as a graph when Diagrams extension is enabled> | ||
{{#mermaid:sequenceDiagram | |||
participant Alice | |||
participant Bob | |||
Alice->John: Hello John, how are you? | |||
loop Healthcheck | |||
John->John: Fight against hypochondria | |||
end | |||
Note right of John: Rational thoughts <br/>prevail... | |||
John-->Alice: Great! | |||
John->Bob: How about you? | |||
Bob-->John: Jolly good! | |||
}} | |||
Dependencies | Dependencies |
Revision as of 18:16, 18 April 2025
This page is under construction
Build targets
LuxCore is made of several targets:
<TODO: Show it as a graph when Diagrams extension is enabled>
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