Skip to content
This repository was archived by the owner on Oct 1, 2020. It is now read-only.

How to build dependencies separately #68

Open
adamjstewart opened this issue Nov 1, 2019 · 0 comments
Open

How to build dependencies separately #68

adamjstewart opened this issue Nov 1, 2019 · 0 comments

Comments

@adamjstewart
Copy link

I'm trying to add a package for QNNPACK to the Spack package manager. I see that QNNPACK downloads its own dependencies, and that this can be avoided by setting *_SOURCE_DIR via cmake. Is there a way to point to an existing external installation instead of a source directory so that Spack doesn't need to rebuild all of these dependencies? Spack is designed to work on air-gapped supercomputers that don't have internet access, so I can't have it download anything at build time.

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

No branches or pull requests

1 participant