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
{{ message }}
This repository has been archived by the owner on Mar 1, 2021. It is now read-only.
the packaging repository is currently making use of standard autotools to build packages for ubuntu. we dont want to continue to maintain both autotools and cmake as this is just added burden and someone will forget. we need to move toward updating packing to make use of cmake.
googling around suggests at least one thing we need to do is update debian/rules to tell it to use cmake:
dh $@ --buildsystem=cmake
there are bound to be other issues beyond that. it should also be noted that @oxidase has added cmake targets that produce .deb files but they dont conform to the same layout as the ones published on the ubuntu ppas (launchpad).
@kevinkreiser I guess this means we're currently not building new releases, right? Any idea when that might be resolved? I would rather not have to build from source to get Valhalla onto the new telemetry Spark cluster (but that's probably a doable workaround).
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
recently valhalla has been moving towards
cmake
support in valhalla/valhalla#1272the packaging repository is currently making use of standard
autotools
to build packages for ubuntu. we dont want to continue to maintain bothautotools
andcmake
as this is just added burden and someone will forget. we need to move toward updating packing to make use ofcmake
.googling around suggests at least one thing we need to do is update
debian/rules
to tell it to usecmake
:there are bound to be other issues beyond that. it should also be noted that @oxidase has added
cmake
targets that produce.deb
files but they dont conform to the same layout as the ones published on the ubuntu ppas (launchpad).cc: @TheMarex
The text was updated successfully, but these errors were encountered: