Import SPTAG Failed
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 5k
- Forks
- 622
- Avg merge
- 8h 37m
- Merged PRs (30d)
- 5
Description
Describe the bug
After building SPTAG and passing the tests in SPTAGTest.exe, I tried to run the Tutorial.ipynb codes in juptyer notebook but it fails when:
I checked #75 and #55 but as the above image shows, I should have the right sys path and the right python version attached. I also check CmakeCache.txt and the python path is python 3.9.
But I realized there might be some files missing in my \build\Release folder comparing to the error message to the above two posts.
And upon compiling ALL_BUILD I did get failure from not finding SPTAGLib.lib despite that SPTAGTest.exe passed.
I attached the file I have below:
To Reproduce
Basically following the test of installing SPTAG:
- install swig, boost, cmake and added to environment variables
- clone SPTAG, do cmake as instructed, open SPTAGLib.sln in visual studio and compile ALL_BUILD
- add to environment variables
- run Tutorial.ipynb
Desktop (please complete the following information):
[windows 11 home]
[64-bit, x64]
Could any try to see what's wrong with building SPTAG?
Thank you so much!!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the Windows 11 build and import flow using Tutorial.ipynb, SPTAGLib.sln, CMakeCache.txt, and the build\Release directory. Start by checking the ALL_BUILD failure involving SPTAGLib.lib and compare the generated files with the import error and referenced issues #75 and #55. Done means ALL_BUILD completes and Tutorial.ipynb imports SPTAG successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, cpp, jupyter-notebook, python
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100