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

Add API to define a package finder and make the -package key resolver use defined finder and only fall back to pkg-config framework. #32

Open
ethouris opened this issue Nov 6, 2024 · 0 comments

Comments

@ethouris
Copy link
Owner

ethouris commented Nov 6, 2024

There should be some method that allows to specify contents of the package and possibly how to search for it and how to autodetect it. The package database will be searched first for a package, and the pkg-config framework will be a default fallback.

The "package" should be treated like something being a "target that is always built, and if it's not, then there's nothing we can do". This will still have to be used through -packages key (not -depends), but in future some methods for automatically resolving lacking packages, should there be defined a method for that, can automatically install packages and make them available.

The command to define a package would be something like:

ag-define-package <name> -include <header dir> -lib <lib dir> -flags ...
ag-provide-package <name> <procname>

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