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

DEB package dependencies are unreasonable #126

Open
DavidZemon opened this issue Jul 5, 2017 · 4 comments
Open

DEB package dependencies are unreasonable #126

DavidZemon opened this issue Jul 5, 2017 · 4 comments

Comments

@DavidZemon
Copy link
Collaborator

The auto-detected package dependencies are unreasonably new. For instance, the .deb file depends on libfontconfig1 v2.11.94 or newer, which is not available on Debian Stretch (newest release at the time of this writing). Surely the CMake binaries from CMake.org will run on the newest version of Debian Stretch, so this is simply package builder being a PITA.

@DavidZemon
Copy link
Collaborator Author

One option (which I'll probably move forward with) is to create a virtual machine for something like Ubuntu 14.04 and build debs there from now on. This concept could be taken further, and I could start up VMs for Fedora and perhaps even Rhasbian running on a virtual ARM environment.

@DavidZemon
Copy link
Collaborator Author

DavidZemon commented Jul 5, 2017

Another option is to remove CMake from the PropWare package. There are a few permutations of the options here.

  • Require cmake 3.3+, force users to do manual install if their distribution does not provide 3.3+
  • Require cmake 3.3+ and provide cmake packages separately for any user on a system that does not provide it
  • Revert some of the feature use in PropWare to be backwards compatible with older versions of CMake, therefore making it more reasonable to not provide a cmake package and rely on the OS-provided version being new enough

@DavidZemon
Copy link
Collaborator Author

Downgrading to CMake < 3.3 is not looking good. FindPropWare.cmake utilizes the generator expression $<COMPILE_LANGUAGE:...> for setting compilation flags on each target. The feature was introduced in v3.3 and the only other way to implement it (that I've found) in earlier versions is to set flags at a directory level (via set(CMAKE_<LANG>_FLAGS ...)).

@DavidZemon
Copy link
Collaborator Author

Oorrrr... I could just use Docker because that's what Docker was built for.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant