Skip to content

Conversation

@reet-
Copy link
Contributor

@reet- reet- commented Oct 31, 2025

LIEF : Library to Instrument Executable Formats.

Note that the external dependencies are not packaged separately as the LIEF cmake build system uses the zip files in the third-party directory of the release tarball (nanobind etc).

LIEF : Library to Instrument Executable Formats.

Note that the external dependencies are not packaged separately as the
LIEF cmake build system uses the zip files in the third-party directory
of the release tarball (nanobind etc).
@jkloetzke
Copy link
Member

Wow. This is not a simply python library but a giant C++ project with a Python binding. 🤯

I think we should rather move this to the devel category, shouldn't we?

The python interface and the library should be separate multipackages I guess. Something like the following?

multiPackage:
    libLIEF:
        multiPackage:
            dev:
                packageScript: cmakePackageDev
            tgt:
                packageScript: cmakePackageLib
    python:
        depends:
            - name: devel::lief-libLIEF-tgt
              use: []
        packageScript: ???
        provideDeps: [ "*-tgt" ]

Regarding the embedded dependencies... It's not nice but that can be later improved if required. So let's not make this more complicated than needed.

Just out of curiosity? Is this recipe intended to be used as a build helper/tool by some other recipes? Or is this cross-compiled for an embedded target?

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