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

[bug] wildcards in profiles for env variables do not work #8657

Closed
scddev opened this issue Feb 8, 2021 · 6 comments · Fixed by #8688
Closed

[bug] wildcards in profiles for env variables do not work #8657

scddev opened this issue Feb 8, 2021 · 6 comments · Fixed by #8688
Assignees
Milestone

Comments

@scddev
Copy link
Contributor

scddev commented Feb 8, 2021

Environment Details

  • Ubuntu 20.04
  • gcc/clang
  • 1.33.1
  • 3.8

Steps to reproduce

E.g. enhance the sample for profiles from the docs https://docs.conan.io/en/latest/reference/profiles.html:

[settings]
*@myuser/*:compiler=clang
*@myuser/*:compiler.version=3.5
*@myuser/*:compiler.libcxx=libstdc++11
compiler=gcc
compiler.version=4.9
compiler.libcxx=libstdc++11

[env]
*@myuser/*:CC=/usr/bin/clang
*@myuser/*:CXX=/usr/bin/clang++
CC=/usr/bin/gcc
CXX=/usr/bin/g++

If repeating the env variables with every package name (like in docs with e.g. zlib), it works as expected.

@solvingj solvingj self-assigned this Feb 9, 2021
@solvingj solvingj transferred this issue from conan-io/conan Feb 9, 2021
@solvingj
Copy link
Contributor

solvingj commented Feb 9, 2021

Hi @scddev , I have transferred this issue over to the conan-io/docs repository. I think it's a reasonable suggestion. Lets see what others think.
@memsharded do you think this is a suitable enhancement to the docs, to show wildcard usage?

@memsharded
Copy link
Member

Yes, sure, wildcard can be documented properly

@solvingj
Copy link
Contributor

@scddev I've added a PR. ok to close?

@solvingj
Copy link
Contributor

@scddev I apologize, I believe I have misunderstood the original issue request. You are reporting a real bug here. Let me work on this.

@memsharded
Copy link
Member

Proposed a potential fix in #8688 for next 1.35

@memsharded
Copy link
Member

Merged #8688, this will be released in 1.35

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants