Open yurivict opened 1 year ago
@yurivict dgl_sparse
is supported with Pytorch backend only. So please append -DBUILD_SPARSE=OFF
to cmake.
Maybe cmake should automatically disable parts that aren't compatible with the currently selected backend, and let the user know that some parts where disabled for the reason of incompatibility.
This would prevent confusion like this.
DGLBACKEND
is not used in cmake stage. But actually we could print more clear error or disable dgl_spare build if backend is not torch.
This issue has been automatically marked as stale due to lack of activity. It will be closed if no further activity occurs. Thank you
Converting this to a feature request. I agree with @Rhett-Ying that we should add a check to bypass dgl.sparse
when backend is not pytorch. Also, wonder why our CI doesn't catch this error.
š Bug
The documentation says that DGLBACKEND sets the backend. However, with
DGLBACKEND=tensorflow
it still imports torch:To Reproduce
cmake configure + build.
Environment
conda
,pip
, source): build as a FreeBSD port