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

codec2-dev build automation #19

Closed
drowe67 opened this issue Aug 17, 2024 · 2 comments
Closed

codec2-dev build automation #19

drowe67 opened this issue Aug 17, 2024 · 2 comments
Labels
help wanted Extra attention is needed

Comments

@drowe67
Copy link
Owner

drowe67 commented Aug 17, 2024

Following on from #8, automagically build codec2-dev under radae.
Modify README.md
Edit *.sh CODEC2_DEV path

Skills: cmake

@drowe67 drowe67 added the help wanted Extra attention is needed label Aug 17, 2024
@tmiw
Copy link
Collaborator

tmiw commented Oct 26, 2024

Since codec2-dev is only used for test, any value in also suppressing its build unless unit tests are enabled?

On that note, perhaps lpcnet_demo, FARGAN etc. should also only be built if tests are enabled. Currently freedv-gui pulls its own copy of Opus for its build, so in effect Opus/FARGAN are built twice. Should that be tracked as a separate issue?

@drowe67
Copy link
Owner Author

drowe67 commented Oct 27, 2024

This repo has served it's purpose (see Scope statement), and I don't want us to get bogged down in unnecessary maintenance. Time to move on from this repo, if you have some spare cycles, let start working on #28 (4) "C port of core ML".

I'll filter out/remove the Issues in this repo at some point.

@drowe67 drowe67 closed this as completed Nov 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants