Using wfdb-swig for Python
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 82
- Forks
- 21
- Avg merge
- 35m
- Merged PRs (30d)
- 1
Description
Inside, wfdb-python directory, when I type "make" (using bash on ubuntu 5.4.0 on windows), it throws
Error: Directors are not supported for C code and require the -c++ option
If I ignore this and type "make" again, it throws this error
dereferencing pointer to incomplete type ‘struct WFDB_Siginfo’
if (arg1->fname) free((char*)arg1->fname);
error: Command "x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -I/usr/local/include -fPIC -I/usr/local/include -I/usr/local/lib/python2.7/dist-packages/numpy/core/include -I/usr/include/python2.7 -c wfdb_python_wrap.c -o build/temp.linux-x86_64-2.7/wfdb_python_wrap.o" failed with exit status 1
Makefile:10: recipe for target 'all' failed
make: *** [all] Error 1
I do not know what's happening here, I have wfdb library installed, swig installed, and also made sure anything can find everything(path set). I appreciate if anyone can help me understand this errors.
I hope I do not have to change wfdb.i interface file. I am trying to wrap wfdb for python, so that i can use all functionalities of wfdb library, as native python wfdb is limited in functionality.
Thanks
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
Start in the wfdb-python directory by reading Makefile and wfdb.i, then reproduce the failure with make using the reported Ubuntu-on-Windows environment. Trace the SWIG and C compilation errors involving wfdb_python_wrap.c and WFDB_Siginfo; done means the Python wrapper builds successfully without either error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, python
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100