Conversation
Add packaging/debian/ with standard Debian packaging metadata to produce two binary packages: eld (linker binary, libLW.so, templates, YAMLMapParser) and eld-plugin-dev (PluginAPI headers). A symlink at debian -> packaging/debian keeps the layout consistent with packaging/arch/ while satisfying dpkg-buildpackage's requirement for debian/ at the source root. Signed-off-by: Brian Cain <brian.cain@oss.qualcomm.com>
Triggers on v* tag pushes, installs LLVM from apt.llvm.org, and runs dpkg-buildpackage to validate the packaging. Built packages are verified with dpkg-deb and lintian but no binary artifacts are published. Signed-off-by: Brian Cain <brian.cain@oss.qualcomm.com>
e0bac4b to
015b301
Compare
|
FIXME/TODO:
|
|
We dont have support for out of tree builds and we dont build with llvm19, as a lot of stuff has changed in eld and is compatible only from LLVM 21 onwards. maintainer email id can be eld@noreply.github.com ? |
Ok I'll see what I can do to sort out the gap, then.
No - it'll need to be someone responsive to community support requests. That email address looks like it wouldn't get delivered to someone who will answer. |
|
Thank you so much @androm3da for adding support with all the three major linux package managers!
Would it be possible to directly use LLVM 21 and provide eld release/21.x for apt package manager? (we will always need to match the LLVM version with the eld version; eld release/21.x will require LLVM release/21.x) |
I see now that the unstable and testing channels of debian use 21.1.6. So maybe it makes sense for |
No description provided.