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
Hmm, I don't know anything about this. Googling the issues seems to suspect it's related to low-level LLVM stuff and linking configurations.
Polyscope uses a pretty boring setup and links against standard packages.... any chance this is an issue with the platform rather than something Polyscope-specific?
Did you observe this on the current master branch? There were a few changes merged recently to additionally link with EGL when it is available, I suppose it's possible one of the EGL dependencies is a source of new problems.
Maybe could try setting cmake -DPOLYSCOPE_BACKEND_OPENGL3_EGL=OFF .. at CMake configuration-time to see if the error goes away? (Don't forget to delete the CMakeCache.txt when you rebuild.) Or you could build from the old tagged v2.3.0 version.
Indeed it looks like the issue is caused when working with the spack environment. It works fine with the standard installation of packages.
Maybe could try setting cmake -DPOLYSCOPE_BACKEND_OPENGL3_EGL=OFF .. at CMake configuration-time to see if the error goes away? (Don't forget to delete the CMakeCache.txt when you rebuild.) Or you could build from the old tagged v2.3.0 version.
Ok, seems to be a general problem, unrelated to those recent EGL changes. Has probably been this way for a while.
issue is caused when working with the spack environment
Hmmm, that's annoying. Unfortunately I don't have a way to help with this, and it's hard to say for sure if it's a problem with Polyscope's build setup or just a general issue with spack packages.
If anyone can suggest a change to Polyscope's build options that would resolve this I'm willing to merge it, but otherwise I don't think I can help here.
Activity
nmwsharp commentedon Jan 1, 2025
Hmm, I don't know anything about this. Googling the issues seems to suspect it's related to low-level LLVM stuff and linking configurations.
Polyscope uses a pretty boring setup and links against standard packages.... any chance this is an issue with the platform rather than something Polyscope-specific?
nmwsharp commentedon Jan 1, 2025
Did you observe this on the current
masterbranch? There were a few changes merged recently to additionally link with EGL when it is available, I suppose it's possible one of the EGL dependencies is a source of new problems.Maybe could try setting
cmake -DPOLYSCOPE_BACKEND_OPENGL3_EGL=OFF ..at CMake configuration-time to see if the error goes away? (Don't forget to delete theCMakeCache.txtwhen you rebuild.) Or you could build from the old taggedv2.3.0version.vinayakvijay commentedon Jan 2, 2025
Indeed it looks like the issue is caused when working with the spack environment. It works fine with the standard installation of packages.
Tried this but doesn't work still.
nmwsharp commentedon Jan 2, 2025
Thanks for following up!
Ok, seems to be a general problem, unrelated to those recent EGL changes. Has probably been this way for a while.
Hmmm, that's annoying. Unfortunately I don't have a way to help with this, and it's hard to say for sure if it's a problem with Polyscope's build setup or just a general issue with spack packages.
If anyone can suggest a change to Polyscope's build options that would resolve this I'm willing to merge it, but otherwise I don't think I can help here.