Bug 1518

Summary:	Port to Haiku OS
Product:	[JogAmp] General	Reporter:	Javier Steinaker <jsteinaker>
Component:	builds	Assignee:	Javier Steinaker <jsteinaker>
Status:	CONFIRMED ---
Severity:	enhancement	CC:	sgothel
Priority:	P4
Version:	2.7.0
Hardware:	pc_all
OS:	other
Type:	FEATURE	SCM Refs:
Workaround:	---

Description Javier Steinaker 2025-07-09 21:56:09 CEST

As discussed with Sven via email, I'm interested in porting the libraries to Haiku (an alternative OS, BeOS's successor), mostly to be able to run SweetHome3D. Haiku is pretty much POSIX compliant and has a Wayland compatibility layer, which is used to run software like Firefox.

Transcription of what Sven thinks that may need to be done at first glance:

shouldn't be too hard, more tedious :)

One layer of OS detection it the ant build-system,
either
- add some lines to the gluegen-cppbase.xml or
- use an override pre-set like in gluegen/make/lib/*xml

We need a new triple identifier to name the native jars,
and add a native subfolder to the fat jars.

Another layer is in the MachineDescription and Platform code,
which is pretty local and not wide spread.
MachineDescription is just to ensure proper CPU mechanics are met
like data type size, cache size etc.
In the Platform part the actual OS is matched to also allow loading
the proper compiled native code (-> above triple).

Guess that's all so far :)

Tedious ant build changes may need to apply in JOAL, JOGL and JOCL?

Comment 1 Sven Gothel 2025-07-14 12:54:02 CEST

Hi Javier, excellent. Thank you!

I have moved this to version 2.7.0 (we use it as the target version)
and assigned you for the job, since you wanted to do the work.
Surely I will assist, no problem.

Yes, I already have seen Haiku OS in Mesa3D OS targets,
as I was building a soft-renderer.

So just using the X11Lib layer should in theory be seamless AWT + NEWT,
while adding the native Haiku OS's Windowing toolkit for NEWT 
would be some work of course (if possible w/ Mesa3D).