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

Error compiling with LC3plus #599

Closed
Hunter-Phipps opened this issue Nov 11, 2022 · 6 comments
Closed

Error compiling with LC3plus #599

Hunter-Phipps opened this issue Nov 11, 2022 · 6 comments

Comments

@Hunter-Phipps
Copy link

Hunter-Phipps commented Nov 11, 2022

In file included from ../../src/a2dp-sbc.c:31:
../../src/utils.h:54:30: error: unknown type name ‘LC3PLUS_Error’
54 | const char *lc3plus_strerror(LC3PLUS_Error err);
| ^~~~~~~~~~~~~
make[3]: *** [Makefile:736: a2dp-sbc.o] Error 1

@arkq
Copy link
Owner

arkq commented Nov 14, 2022

Do you have LC3plus (not LC3) library installed? The lc3.h from lc3plus defines typdef enum { ... } LC3PLUS_Error;.

@Hunter-Phipps
Copy link
Author

I compiled libLC3plus.so using the makefile changes in #479 and copied it into the /usr/lib/ folder.

@arkq
Copy link
Owner

arkq commented Nov 15, 2022

Please, check from where the lc3.h is included with command like this: echo '#include <lc3.h>' | gcc -H -x c - Then, check whether the included lc3.h file has LC3PLUS_Error definition.

@Hunter-Phipps
Copy link
Author

I copied lc3.h and lc3.c from the ETSI floating point source code to /usr/include/ and it looks like it compiled / installed without any issues but I still don't see LC3 in the pipewire compile.

@arkq
Copy link
Owner

arkq commented Nov 15, 2022

but I still don't see LC3 in the pipewire compile

Hmm... you might be right, because this repo is not for pipewire project :D

But if you meant that in pipewire LC3plus (not LC3) is not activated when connecting with bluealsa, make sure that LC3plus is enabled in bluealsa via command line options, i.e.: bluealsa -p a2dp-source -c lc3plus.

@arkq
Copy link
Owner

arkq commented Jan 1, 2023

Since there are no more replies, I understand that the issues is solved. Otherwise, please reopen it and provide more details about your setup.

@arkq arkq closed this as completed Jan 1, 2023
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

No branches or pull requests

2 participants