Skip to content

Exporting excite as a function instead of a binary - #11

Merged
r9y9 merged 4 commits into
r9y9:masterfrom
jfsantos:master
Oct 23, 2015
Merged

r9y9 merged 4 commits into
r9y9:masterfrom
jfsantos:master

Conversation

@jfsantos

Copy link
Copy Markdown
Contributor

This PR adds excite as a function. I'll be sending a separate PR to pysptk with the Cython part of the code.

@r9y9

r9y9 commented Oct 23, 2015

Copy link
Copy Markdown
Owner

Looks good!

A request: Can you rename excite.c to _excite.c? Source files that start with _ are automatically collected by waf (see bin/wscript#L20-L22) and compiled into the SPTK shared library (libSPTK.{so, dylib, dll}). This will enable other languages (e.g. Julia) to call excite function from the shared library.

Comment thread bin/excite/excite.c Outdated

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess this line may cause compilation error on MSVC on windows. While I was working on #8, I found MSVC on AppVeyor throws error for C89-imcompatible codes.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right, I forgot MSVC still does not have support for C99 (they're only 16 years late!). This is now fixed.

r9y9 added a commit that referenced this pull request Oct 23, 2015
Exporting excite as a function instead of a binary
@r9y9
r9y9 merged commit 06318f9 into r9y9:master Oct 23, 2015
@r9y9

r9y9 commented Oct 23, 2015

Copy link
Copy Markdown
Owner

Thanks!

r9y9 added a commit to r9y9/SPTK.jl that referenced this pull request Oct 27, 2015
@r9y9 r9y9 mentioned this pull request Oct 27, 2015
1 task done
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants