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

Some tech files should live in the "Stackup" object #315

Open
jwright6323 opened this issue Feb 22, 2019 · 3 comments
Open

Some tech files should live in the "Stackup" object #315

jwright6323 opened this issue Feb 22, 2019 · 3 comments
Labels
advanced PR API bug medium priority Hard workaround exists, costing time/effort, chip QoL/QoR issue

Comments

@jwright6323
Copy link
Contributor

For example, QRC techfiles and technology LEFs are stackup-specific, so these should live in the "stackup" data structure. Right now, if you have multiple stackups, you'd need separate technology JSONs to support that. This is low priority since right now we don't support any technologies with multiple stackups, but we should fix it before we build too much infrastructure with the current APIs.

@jwright6323 jwright6323 added bug low priority Easy workaround exists, regular QoL issue API advanced PR labels Feb 22, 2019
@jwright6323
Copy link
Contributor Author

Also, obligatory comment that this relies on #308

@jwright6323
Copy link
Contributor Author

Bumping the priority here, as it's an annoyance for building new plugins. The QRC techfile should definitely not be a library-specific thing.

@jwright6323 jwright6323 added medium priority Hard workaround exists, costing time/effort, chip QoL/QoR issue and removed low priority Easy workaround exists, regular QoL issue labels May 22, 2019
@jwright6323
Copy link
Contributor Author

Also, funnily enough, the tech LEF is an independent library and one could argue it belongs with the std cells, although I think it's also reasonable to keep it separate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
advanced PR API bug medium priority Hard workaround exists, costing time/effort, chip QoL/QoR issue
Projects
None yet
Development

No branches or pull requests

1 participant