Closed e2002e closed 1 year ago
hi, thanks for the report. Yes i did as you suggested here: https://github.com/UPBGE/upbge/commit/0bb0edf849d354b989489a0c16ee0a203cb05bb0
it happened only on linux. i had other issues in debug builds but idk if i did something wrong or not. But release builds were compiling.
ok, troubles to build in debug mode were related to bad RAM management with compiler + current chipset drivers.... Then i close this report. Thanks.
There were a lot of errors that actually don't come from the code indeed. i.e runing make again would solve them. I guess this is the compiler issue you'r refering to. Np. bye.
Le jeu. 13 juil. 2023 22:23, youle31 @.***> a écrit :
Closed #1822 https://github.com/UPBGE/upbge/issues/1822 as completed.
— Reply to this email directly, view it on GitHub https://github.com/UPBGE/upbge/issues/1822#event-9815300027, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHDG6X4FM4EFVRAJYGEQ33DXQBKL3ANCNFSM6AAAAAA2JDCPBM . You are receiving this because you authored the thread.Message ID: @.***>
Lattest commit introduces a bug on compilation:
I tried adding -fpermissive to be to CMAKE_C_FLAGS in the screen/CMakeLists.txt but it doesn't help.
After looking at the file I found the same declaration than line 1977 with a cast, copying it in stead of the faulty line solves the error: reinterpret_cast<void *>(ed_screen_context);