faiss_gpu object is not linked to static library libfaiss.a about faiss HOT 3 OPEN

This seems normal to me, libfaiss.a works standalone and contains only CPU code, libfaiss_gpu.a depends on the former and contains GPU code.

from faiss.

@mdouze Thanks for the reply!
In FAISS v1.7.4, libfaiss_gpu.a was not generated and libfaiss.a contained both CPU and GPU objects.
Has the specification changed in FAISS v1.8.0?

Also, it appears that libfaiss_gpu.a is not installed as described in issue #3375.
This specification seems to make it difficult for users to use libfaiss_gpu.a.

from faiss.

libfaiss_gpu.a is supposed to be linked into libfaiss via the WHOLE_ARCHIVE directive in its entirety. Maybe this doesn't work when libfaiss is compiled as a static lib.

In FAISS v1.7.4, libfaiss_gpu.a was not generated and libfaiss.a contained both CPU and GPU objects.
Has the specification changed in FAISS v1.8.0?

It's still the case that libfaiss*.so contains both CPU and GPU code. libfaiss_gpu.a was introduced to share the same objects for GPU code across the different versions of libfaiss (generic, avx2, avs512). This considerably reduced the build times for the conda packages. However, it's possible when built as a static library (libfaiss.a) that WHOLE_ARCHIVE packaging (of libfaiss_gpu into libfaiss) doesn't work.

from faiss.