OpenVSP on Fedora 42 / Arch Linux and Wayland

[Carlos Rodriguez]

Hello everyone, 

I’m interested in installing OpenVSP on Fedora 42 or Arch Linux. Are there any known issues or recommendations for these distributions? I have tried on my desktop (Fedora 42) following the build instructions but no luck. 

Also, since both use Wayland by default, is OpenVSP compatible with Wayland, or does it require XWayland?

Thanks in advance for your guidance!

Best,

Carlos

[lsol...@gmail.com]

Hey Carlos, what issues are you having? I have been trying to compile OpenVSP on Fedora42 as well but am running into issues with stepcode. After some digging, it appears that the latest version of gcc (15.2.1) has dropped support for some older code syntax that is used by the version of stepcode packaged with OpenVSP. I tried replacing the packaged version of stepcode with that from the official stepcode github and was able to successfully build all the libraries, but now the main build is failing with stepcode issues again so I'm still hunting that down. I don't think Wayland is an issue as I was able to build OpenVSP on Fedora41 and was using Wayland there.

https://groups.google.com/g/openvsp/c/NtF0WNJKAcw/m/pcxvhMXKAQAJ

Lars

[Rob McDonald]

I would be interested in your progress on STEPCode.

The version packaged with OpenVSP is from a long time back -- and a lot of progress has been made, but STEPCode is not a centrally managed project.  Consequently, changes are made by different users that frequently don't get integrated into a central core.  Likewise, their changes may not go in a single direction.

The point is, a lot of the changes have been to the STEPCode build system and how it integrates with external projects -- OpenVSP used STEPCode in a somewhat unconventional way.  So, when I've looked at updating, it has looked rather challenging.

As you say, Wayland should not be a problem.  OpenVSP uses FLTK.  FLTK can be compiled to work with only Wayland, only X, or either Wayland or X (detected at runtime).  OpenVSP shouldn't care, it will just use whatever FLTK uses.

I try to statically link all the libraries I can, but on a Linux platform, you are much more likely to use a packaged library and shared libraries -- so you'll use whatever FLTK was built by the packaging team.

Rob

--
You received this message because you are subscribed to the Google Groups "OpenVSP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openvsp+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/openvsp/a2b1115b-d481-46e1-a079-f6e67a0833a7n%40googlegroups.com.