Skip to content

Add debian packaging for eld#822

Draft
androm3da wants to merge 2 commits intoqualcomm:mainfrom
androm3da:bcain/deb_pkg
Draft

Add debian packaging for eld#822
androm3da wants to merge 2 commits intoqualcomm:mainfrom
androm3da:bcain/deb_pkg

Conversation

@androm3da
Copy link
Contributor

No description provided.

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>
@androm3da
Copy link
Contributor Author

FIXME/TODO:

  • maintainer email address
  • can we build against llvm-19-dev? Prob some compat issues here: llvm 19 is older, the -dev package is not like the source tree so unlikely to work as-is.

@androm3da androm3da marked this pull request as draft February 13, 2026 04:53
@quic-seaswara
Copy link
Contributor

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 ?

@androm3da
Copy link
Contributor Author

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.

Ok I'll see what I can do to sort out the gap, then.

maintainer email id can be eld@noreply.github.com ?

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.

@parth-07
Copy link
Contributor

Thank you so much @androm3da for adding support with all the three major linux package managers!

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.

Ok I'll see what I can do to sort out the gap, then.

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)

@androm3da
Copy link
Contributor Author

Thank you so much @androm3da for adding support with all the three major linux package managers!

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.

Ok I'll see what I can do to sort out the gap, then.

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 main branch of eld to depend on 23.x and if we're inclined maybe we could cherry-pick this/these commits back to release/21.x / release/22.x where we'd pick the corresponding llvm.

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.

3 participants