Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

added missing function speex_header_free to libspeex.def #7

Closed
wants to merge 1 commit into from
Closed

added missing function speex_header_free to libspeex.def #7

wants to merge 1 commit into from

Conversation

vividos
Copy link
Contributor

@vividos vividos commented Oct 1, 2017

libspeex.def is missing the function speex_header_free(), so library users on Visual Studio are not able to free speex_header structures, resulting in a (small) memory leak.

@erikd
Copy link
Member

erikd commented Oct 1, 2017

LGTM! 👍

@vividos
Copy link
Contributor Author

vividos commented Oct 9, 2017

It seems the AppVeyor build isn't configured correctly - it doesn't know where to find the .sln file to build. It may help to point it to speex/win32/VS2008/libspeex.sln, but I don't know if it can build libspeex with Visual Studio 2008.

@vividos
Copy link
Contributor Author

vividos commented Jan 7, 2018

@erikd what's the process to get this pull request into the repository? The only missing step seems to be that someone checks the Appveyor configuration and specifies the .sln file to build.

@erikd
Copy link
Member

erikd commented Jan 7, 2018

Have you looked at the appveyor build failure?

Maybe we should ping @tmatth .

@tmatth
Copy link
Member

tmatth commented Jan 7, 2018

Thanks, will merge once I figure out what's up with this appveyor build failure.

Normally Speex development happens on the Speex-dev mailing list:
http://lists.xiph.org/mailman/listinfo/speex-dev

@vividos
Copy link
Contributor Author

vividos commented Mar 15, 2018

It seems the AppVeyor build fails since it isn't properly configured. The error message of the AppVeyor build prints:

Specify which project or solution file to use because the folder contains more than one project or solution file.

The speex project could use the .appveyor.yml file from another xiph project, e.g. from opus:
https://github.com/xiph/opus/blob/master/.appveyor.yml

@tmatth
Copy link
Member

tmatth commented Mar 15, 2018

@vividos yes, I'm assuming that appveyor works with vs2008 .sln files? That's the most recent one we have in speex.

@vividos
Copy link
Contributor Author

vividos commented Mar 15, 2018

Visual Studio 2008 Community Edition is supported by AppVeyor, but I saw PR #8, and it seems the build there is not completing successfully.

@vividos
Copy link
Contributor Author

vividos commented Apr 11, 2018

The patch contained in this PR was recently added to master in commit 0c02121, so I guess this PR can be closed.

@vividos vividos closed this Apr 11, 2018
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.

3 participants