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

Unsupported targets still have dependent files specified #149

Closed
Karl-G1 opened this issue Mar 9, 2022 · 0 comments · Fixed by #151
Closed

Unsupported targets still have dependent files specified #149

Karl-G1 opened this issue Mar 9, 2022 · 0 comments · Fixed by #151
Labels
bug Something isn't working

Comments

@Karl-G1
Copy link
Contributor

Karl-G1 commented Mar 9, 2022

Describe the bug
We removed changes to the custom device XML file from #138 when enabling the 2021 build.
This was due to the intent of making the XML file changes in #144.

Also as part of #138, we removed build support for Pharlap, Linux ARM, and VxWorks RT targets.
Because of this, the custom device shows missing dependent files in System Explorer.

Expected behavior

  1. New instances of the custom device should not add those dependent files to the sysdef
  2. Existing instances of the custom device should not have errors (either due to mutation or stub files)

Screenshots
image

Please complete the following information:
Affects the 21.0 release builld

@Karl-G1 Karl-G1 added the bug Something isn't working label Mar 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant