Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Various Flatpak/CMake fixes #675

Open
wants to merge 9 commits into
base: devel
Choose a base branch
from

Conversation

refi64
Copy link
Member

@refi64 refi64 commented Dec 19, 2019

The main commit is the switch to CMake namespace targets for loading external dependencies, which should fix all the weird build issues associated with the old way.

This updates all the CMake modules to use namespace targets,
which have been supported since CMake 2.8 and bring fix a plethora
of potential linking issues.

Based on the documentation, these should work back until at least
CMake 3.13 which is used by Debian Buster.
install(DIRECTORY "${TSC_BINARY_DIR}/scriptdocs"
DESTINATION ${CMAKE_INSTALL_DATAROOTDIR}/doc/tsc
COMPONENT base)
endif()
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch. I didn't notice the problem -- thanks!

@Quintus
Copy link
Member

Quintus commented Dec 22, 2019

I'm unfamiliar with this new CMake target system, but I trust you know what you're doing. I've always used CMake's XYZ_INCLUDE_DIRS and XYZ_LIBRARIES variables, but apparently this is the new way of doing it...

As for all the .cmake find modules we have in TSC -- they are related to ticket #556. As we have recently dropped cross-compiling support in favour of native compilation with MSYS2, it's likely that we can drop a number of them.

Is there a specific reason why USE_SYSTEM_MRUBY is removed? I remember that muammar wanted to link TSC against the mruby included in Debian rather than our shipped one. The documentation for the option clearly said that mruby version mismatches need to be considered, which is enough of a warning in my opinion. Why take the option away entirely?

Finally, two things for your information (I'll cater for these): First, I think tinyclipboard should be dropped in devel entirely, because there's now sf::Clipboard, which weren't available yet when TSC was ported to SFML. Second, I think I'm going to drop the pod-parser Git submodule and just add the files in themselves. It's unlikely that it'll ever see development outside of TSC.

Ah, and the PR has conflicts with devel now that I merged in release-2.1.0 once more. Would be nice if you could resolve them.

@Quintus
Copy link
Member

Quintus commented Jan 14, 2021

@refi64 Status of this?

@refi64
Copy link
Member Author

refi64 commented Jan 17, 2021

I uhhh forgot about it 😅 I'll see if I can look into it later this week.

@Quintus
Copy link
Member

Quintus commented Sep 4, 2022

As the Flatpak topic came up in #706 again, might you look into getting this merged?

@xet7 xet7 mentioned this pull request Oct 3, 2024
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants