Replies: 1 comment 2 replies
-
|
In void-packages, the clean way is to keep both versions by renaming one (e.g., create a 'sfml2' package that installs to /usr/lib/sfml2 and provides sfml2.pc). Then update dependent packages to depend on the appropriate package. You may need to patch their configure scripts to look for SFML2 vs SFML3. Alternatively, if a package can't be ported to SFML3, keep it using SFML2 in a separate overlay repository. Static linking is possible but not recommended due to updates and license considerations. The void-packages guidelines suggest using versioned package names for libraries that can't coexist. |
Beta Was this translation helpful? Give feedback.
-
|
SFML is currently installed as libsfml-<module name>.so and libsfml-<module name>.so.2.6 does the SFML2 still need to be in a separate directory since the libsfml-<module name>.so can only be symlinked to one version? The problem with having separate names for the SFML2 package and the SFML3 package is that code using SFML2 expects the same names as code using SFML3. Will this be resolved by the sfml2.pc file and the corresponding cmake files? Will they still be found with new names? My guess is no, and that would break packages using SFML2 |
Beta Was this translation helpful? Give feedback.
-
|
Testing out my current SFML2 template with an SFML2 cmake project shows that it is searching for an SFML directory in I am also a bit unsure about the .so symlinks. Do they both try to control the libsfml-<module>.so symlink. Do programs expect this symlink, or do they use the longer version libsfml-<module>.so.2.6? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I am attempting to port SFML from major version 2 to 3, but there are some packages are still on SFML2. How would I go about making them build when SFML has been ported to SFML3?
At first I thought to create a separate SFML2 package, but due to the nature of their headers SFML2 and SFML3 cannot coexist without name changes. My second idea was to grab a specific SFML2 commit and use that one, but then the build system would have to build SFML in pre_configure stage. It would also leave the user without any sfml so on their system. Would I then have to statically link the programs in question?
Beta Was this translation helpful? Give feedback.
All reactions