DragonDreams Developer Forum

gale_username wrote: ↑Wed Oct 30, 2024 10:40 pm I wasn't planning on using it much, so the extra effort to get it working wasn't worth it.

I see. I guess NixOS is quite special in the way packaging works to cause that many troubles.

gale_username wrote: ↑Tue Oct 29, 2024 10:24 pm I ended up not using dragengine, but got a fair amount working...

Can you quickly explain the reasons for not using it so I can improve in the future?

So is it now all working as expected? Anything I should upstream or not?

The manifest files are XML files. You can use an XML library to load, edit and save them. Most probably simpler would be using an XSLT processor to alter a specific tag content. "xsltproc" is the usual command line tool to do this.

That's really not nice. It's a security feature to avoid file corruption and tampering. But you could disable the checks in if nothing helps: - https://github.com/LordOfDragons/dragengine/blob/21c890f688717483ccc988f1918680e341d554e6/src/dragengine/src/systems/modules/deLibraryModule.cpp#L548 ...

So you could get it compiling without changing the Drag[en]gine sources or do I need to include some fixes in a future release?

I don't know. These headers are standard locations. Has NixOS a unique way of handling X include files? I googled quickly and NixOS seems to be quite peculiar in handling this. Maybe these links help you out? - https://discourse.nixos.org/t/cant-compile-dwm-x11-xlib-h-not-found/12633/6 - https ...

The sndio should not need a patch nor disabling since no package has it as dependency. Hence SCons will never pull it into the build process automatically.

Concerning the IGDE build this line is caused by missing X11.

Concerning OpenAL I checked the sources. Current head has the same fix applied so building against system OpenAL should be safe with version 1.23.1 and newer.

Hi gale_username. I'll try to answer the question as good as possible. Can you also state which version of Drag[en]gine you try to package? Patch 1: It is possible to do it that way but this will not affect external build software. This is because external builds are not affected by SCons LIBPATH ...