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 Make variable for target package source dir #24144

Open
mering opened this issue Oct 30, 2024 · 0 comments
Open

Add Make variable for target package source dir #24144

mering opened this issue Oct 30, 2024 · 0 comments
Labels
team-Rules-API API for writing rules/aspects: providers, runfiles, actions, artifacts type: feature request untriaged

Comments

@mering
Copy link

mering commented Oct 30, 2024

Description of the feature request:

For an external library like glpk, one needs to add all include paths. With bzlmod, the paths to include files are prefixed with external/glpk~VERSION, external/glpk~ or external/glpk+ depending on the Bazel version. There currently isn't any predefined Make variable to get this path.

The current workaround is to add it to includes instead which doesn't need this prefix but this is suboptimal as this include path is propagated to all consumers.

Which category does this issue belong to?

Rules API

What underlying problem are you trying to solve with this feature?

See TODO comment in bazelbuild/bazel-central-registry#3066.

Which operating system are you running Bazel on?

Linux

What is the output of bazel info release?

7.0.2, 7.1, 8.0rc

If bazel info release returns development version or (@non-git), tell us how you built Bazel.

No response

What's the output of git remote get-url origin; git rev-parse HEAD ?

No response

Have you found anything relevant by searching the web?

No response

Any other information, logs, or outputs that you want to share?

No response

@github-actions github-actions bot added the team-Rules-API API for writing rules/aspects: providers, runfiles, actions, artifacts label Oct 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
team-Rules-API API for writing rules/aspects: providers, runfiles, actions, artifacts type: feature request untriaged
Projects
None yet
Development

No branches or pull requests

4 participants