QNNPACK icon indicating copy to clipboard operation
QNNPACK copied to clipboard

How to build dependencies separately

Open adamjstewart opened this issue 5 years ago • 0 comments

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.

adamjstewart avatar Nov 01 '19 22:11 adamjstewart