Marvin1099

So got a bunch of tracebacks by running: `G_DEBUG=fatal-warnings gdb ./BEE2` For logging i run (gdb): `set logging file gdb.log` And (gdb): `set logging on` Then i run it with...

And any idea that this the exporting problem is about? I'm referring to screenshot of couse.

> You might need to press "reset package cache" in options, to force a new export. That didn't seem to work, any other ideas? Edit: I tried the main branch...

I have reopened the [issue here](https://github.com/BEEmod/BEE2.4/issues/2040) for better organization.

Makes scene, I have to try it to be sure but I think the package that pyinstaller spits out is a universal Linux package, I think all that would be...

If thats the case that that would be very strange since i use the same building script for main and dev, nevertheless I will check for this later today when...

so i ran a script to compare the files from the 2 build folders. I used this script, cant hurt to post it ```bash #!/bin/bash # Directory paths dir1="BEE2.4" dir2="MainBEE2.4"...

So it says the compiler wants to be in the "BEE2.4/dist/64bit/BEE2/compiler/" folder right (thanks for your commit), there is a compiler folder for me in "/BEE2.4/dist/64bit/compiler/" will that folder need...

> It could be that you didn't build the compiler, it expects that to be built in a `compiler/` subfolder. so it seems that is infact the issue, is that...

> Actually thinking about it, could be a mistake in the packages with case-sensitivity. I have no idea, all files in packages/ are lowercase if you mean that. Even if...