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]: Building Basetools For Different Archs Does Not Clean #936

Closed
1 task done
os-d opened this issue Jun 20, 2024 · 2 comments
Closed
1 task done

[Bug]: Building Basetools For Different Archs Does Not Clean #936

os-d opened this issue Jun 20, 2024 · 2 comments
Assignees
Labels
state:needs-triage Needs to triaged to determine next steps state:stale Has not been updated in a long time type:bug Something isn't working urgency:low Little to no impact

Comments

@os-d
Copy link
Contributor

os-d commented Jun 20, 2024

Is there an existing issue for this?

  • I have searched existing issues

Current Behavior

If you build basetools for different architectures, the .obj files are attempted to be used from the last architecture, which leads to linking errors.

Expected Behavior

A clean would be performed (or different obj files generated).

Steps To Reproduce

Build basetools with VS2022 ARM and AARCH64.

Build Environment

- OS(s): Windows
- Tool Chain(s): VS2022
- Targets Impacted: Basetools

Version Information

Top of tree.

Urgency

Low

Are you going to fix this?

Someone else needs to fix it

Do you need maintainer feedback?

No maintainer feedback needed

Anything else?

No response

@os-d os-d added state:needs-triage Needs to triaged to determine next steps type:bug Something isn't working labels Jun 20, 2024
@github-actions github-actions bot added urgency:low Little to no impact state:needs-owner Needs an issue owner to be assigned and removed state:needs-owner Needs an issue owner to be assigned labels Jun 20, 2024
Copy link

This issue has been automatically marked as stale because it has not had activity in 45 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions.

@github-actions github-actions bot added the state:stale Has not been updated in a long time label Aug 23, 2024
Copy link

This issue has been automatically been closed because it did not have any activity in 45 days and no follow up within 7 days after being marked stale. Thank you for your contributions.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state:needs-triage Needs to triaged to determine next steps state:stale Has not been updated in a long time type:bug Something isn't working urgency:low Little to no impact
Projects
None yet
Development

No branches or pull requests

2 participants