You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
while working with the engine with my SO we encountered a couple issues while setting up our linux development environment compared to our windows.
in the halleyproject cmake, finding X11 doesn't work with find_library, only find_package (at least for us on arch)
after compiling, the shared_gen components would always contain different componentID's because of linux sorting files differently in directories, meaning instead of using the order you put in shared_gen_src of
0_transform
1_rendering
2_audio
it would generate them out of order however adding
std::sort(files.begin(), files.end(), [](CodegenSourceInfo a, CodegenSourceInfo b) -> bool {
return a.filename.cppStr() < b.filename.cppStr();
});
in ECSData::loadSources (src/tools/tools/src/ecs/ecs_data.cpp) seemed to work in fixing this issue for us
aside from that joystick support doesn't appear to work on linux however that for us isn't really an issue at the moment.
the reason for this ticket is just in case you weren't aware and have the changes that worked for us in case you'd like to use these in the main repo.
The text was updated successfully, but these errors were encountered:
while working with the engine with my SO we encountered a couple issues while setting up our linux development environment compared to our windows.
in the halleyproject cmake, finding X11 doesn't work with
find_library
, onlyfind_package
(at least for us on arch)after compiling, the shared_gen components would always contain different componentID's because of linux sorting files differently in directories, meaning instead of using the order you put in shared_gen_src of
it would generate them out of order however adding
in ECSData::loadSources (src/tools/tools/src/ecs/ecs_data.cpp) seemed to work in fixing this issue for us
aside from that joystick support doesn't appear to work on linux however that for us isn't really an issue at the moment.
the reason for this ticket is just in case you weren't aware and have the changes that worked for us in case you'd like to use these in the main repo.
The text was updated successfully, but these errors were encountered: