Building LuxCoreRender: Difference between revisions

From LuxCoreRender Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Tag: Reverted
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>
{{#ask:
[[Category:City]]
[[Area::+]]
[[Population::+]]
|?Population=Inhabitants
|?Area#km²=Size in km²
|format=template
|template=Query output demo
|limit=3
}}


{{#mermaid: sequenceDiagram
{{#mermaid: sequenceDiagram

Revision as of 18:55, 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>

{{#ask:

Area::+
Population::+ 
|?Population=Inhabitants
|?Area#km²=Size in km²
|format=template
|template=Query output demo
|limit=3

}}

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