Building LuxCoreRender - FAQ - Revision history

Howetuft: /* Can I use git bisect? */

2026-03-14T11:01:42Z

Can I use git bisect?

← Older revision		Revision as of 13:01, 14 March 2026
Line 54:		Line 54:
	git bisect <good\|bad\|skip> # Depending on above test...		git bisect <good\|bad\|skip> # Depending on above test...

			# Bisection loop
	...		...

	# At a certain point, the bisection stops		# At a certain point, the bisection stops and points at the faulty commit
			# You can reset bisection
	git bisect reset		git bisect reset
	</pre>		</pre>

Howetuft: /* Can I use git bisect? */

2026-03-14T11:00:11Z

Can I use git bisect?

← Older revision		Revision as of 13:00, 14 March 2026
Line 55:		Line 55:

	...		...

			# At a certain point, the bisection stops
			git bisect reset
	</pre>		</pre>

Howetuft: /* Can I use git bisect? */

2026-03-14T10:39:02Z

Can I use git bisect?

← Older revision		Revision as of 12:39, 14 March 2026
Line 42:		Line 42:

	<pre>		<pre>
	# Start bisecting ~~feature~~		# Start git bisecting
	git bisect start		git bisect start

Howetuft: /* Can I use git bisect? */

2026-03-14T10:38:41Z

Can I use git bisect?

← Older revision		Revision as of 12:38, 14 March 2026
Line 38:		Line 38:

	Caveat: this method only works for version >= v2.10.0		Caveat: this method only works for version >= v2.10.0

			Example for Linux (please adapt to other contexts):

			<pre>
			# Start bisecting feature
			git bisect start

			# Define bounds
			git bisect good samples-v2.10.0 # For instance
			git bisect bad HEAD

			# Build the app, test it and report status to git bisect
			make clear && make deps && make # Build at this stage
			./out/install/Release/bin/luxcoreui mytestscene/render.cfg
			git bisect <good\|bad\|skip> # Depending on above test...

			...
			</pre>

Howetuft: /* Can I use git bisect? */

2026-03-14T10:17:05Z

Can I use git bisect?

← Older revision		Revision as of 12:17, 14 March 2026
Line 37:		Line 37:
	<pre>make clear && make deps && make</pre>		<pre>make clear && make deps && make</pre>

	Caveat: this method only works for version >= v2.10.0.		Caveat: this method only works for version >= v2.10.0

Howetuft: /* Can I use git bisect? */

2026-03-14T10:16:52Z

Can I use git bisect?

← Older revision		Revision as of 12:16, 14 March 2026
Line 32:		Line 32:
	== Can I use <code>git bisect</code>? ==		== Can I use <code>git bisect</code>? ==

	Yes, if you need to find a faulty commit, you can use `git bisect`.		Yes, if you need to find a faulty commit, you can use <code>git bisect</code>.

	In that case, please note the correct verb to build LuxCoreRender at each step is		In that case, please note the correct verb to build LuxCoreRender at each step is

Howetuft at 10:16, 14 March 2026

2026-03-14T10:16:33Z

← Older revision		Revision as of 12:16, 14 March 2026
Line 29:		Line 29:
	* Step#3bis: Build luxcoreui:		* Step#3bis: Build luxcoreui:
	<pre>make luxcoreui</pre>		<pre>make luxcoreui</pre>

			== Can I use <code>git bisect</code>? ==

			Yes, if you need to find a faulty commit, you can use `git bisect`.

			In that case, please note the correct verb to build LuxCoreRender at each step is
			<pre>make clear && make deps && make</pre>

			Caveat: this method only works for version >= v2.10.0.

Howetuft at 10:11, 14 March 2026

2026-03-14T10:11:16Z

← Older revision		Revision as of 12:11, 14 March 2026
Line 1:		Line 1:
	== Is it possible~~, in a develop & debug context,~~ to set-up a local-only, end-to-end, build chain? ==		== Is it possible to set-up a local-only, end-to-end, build chain? ==

	Yes it is, but for Linux only, at the moment, and starting with v2.11.		Yes it is, but for Linux only, at the moment, and starting with v2.11.

Howetuft at 05:33, 11 February 2026

2026-02-11T05:33:34Z

← Older revision		Revision as of 07:33, 11 February 2026
Line 2:		Line 2:

	Yes it is, but for Linux only, at the moment, and starting with v2.11.		Yes it is, but for Linux only, at the moment, and starting with v2.11.
			<p>Also, important caveat: this kind of build is solely intended for development and tests. Do not use in production</p>


	Step#1: Build dependencies locally		* Step#1: Build dependencies locally

	Use [[Building_LuxCoreRender#Local_Plain_Build\|local plain build]] or [[Building_LuxCoreRender#Local_Continuous_Integration \| local CI build]] of LuxCoreDeps		Use [[Building_LuxCoreRender#Local_Plain_Build\|local plain build]] or [[Building_LuxCoreRender#Local_Continuous_Integration \| local CI build]] of LuxCoreDeps


	Step#2: Inject local dependencies in LuxCore build		* Step#2: Inject local dependencies in LuxCore build
	<pre>python -m build-system.luxmake deps --local <path/to/deps> --release test</pre>		<pre>python -m build-system.luxmake deps --local <path/to/deps> --release test</pre>


	Step#3: Build a testing wheel		* Step#3: Build a testing wheel
	<pre>make wheel-test</pre>		<pre>make wheel-test</pre>



	Step#4: Inject testing wheel in Blender:		* Step#4: Inject testing wheel in Blender:

	Use [[Developing_and_debugging_BlendLuxCore \| BlendLuxHelper]]		Use [[Developing_and_debugging_BlendLuxCore \| BlendLuxHelper]]


	~~One can also replace steps #3 & #4 by:~~

	Step#3bis: Build luxcoreui:		For a debugging with luxcoreui only, one can also replace steps #3 & #4 by:

			* Step#3bis: Build luxcoreui:
	<pre>make luxcoreui</pre>		<pre>make luxcoreui</pre>


	~~Caveat: this kind of build is solely intended for test.~~

Howetuft: /* Is it possible, in a develop & debug context, to set-up a local-only, end-to-end, build chain? */

2026-02-11T05:29:48Z

Is it possible, in a develop & debug context, to set-up a local-only, end-to-end, build chain?

← Older revision		Revision as of 07:29, 11 February 2026
Line 20:		Line 20:
	Step#4: Inject testing wheel in Blender:		Step#4: Inject testing wheel in Blender:

	Use BlendLuxHelper		Use [[Developing_and_debugging_BlendLuxCore \| BlendLuxHelper]]