xiph / xiph/opus

MinGW Compiling code using Opus using libraries

Open
#173 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
3.3k
Forks
808
PR merge metrics
No merged PRs in 30d

Description

Hello,

I am looking at using libraries but I have already given a few shots... Let say I want to compile this standalone Opus use file: https://pastebin.com/L5P2cyZS

I have libraries available here? https://archive.mozilla.org/pub/opus/win32/opusfile-v0.9-win32.zip

If I do mingw32-g++ main.cpp -L "folderWhereIUnarchiveThePreviousFile" I always get:

undefined reference to `opus_get_version_string'

and others... (I tried this several times in the past weeks...)

Any ideas please?

Note that main.cpp is the code from the pastebin.
I know that g++ don't get the good libraries but I don't know how to solve it...
Am I trying to link not the good libs?

It seems that there isn't any available Windows artifact here: https://github.com/xiph/opus-tools/issues/43

Could we have precise instructions for Windows using MinGW and not Microsoft Visual please? (cf README.md 0) Set up a development environment)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the README's “Set up a development environment” section, the linked main.cpp paste, and the opusfile-v0.9-win32.zip contents. Reproduce the reported mingw32-g++ command and determine the documented MinGW linking steps. Done means the README includes precise Windows MinGW instructions that build the standalone example without undefined references.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, cpp
Domain
build-system, documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.