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.

Sign up for GitHub

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

Jump to bottom

generated_cmd_multinet.h: No such file or directory #382

Closed
hursto75 opened this issue Nov 4, 2024 · 2 comments · Fixed by #392
Closed

generated_cmd_multinet.h: No such file or directory #382

hursto75 opened this issue Nov 4, 2024 · 2 comments · Fixed by #392

Comments

@hursto75
Copy link

hursto75 commented Nov 4, 2024

./utils.sh build
Getting the error when i try to run the build for the hardware bin image.

Files/__idf_main.dir/audio.c.obj -MF esp-idf/main/CMakeFiles/__idf_main.dir/audio.c.obj.d -o esp-idf/main/CMakeFiles/__idf_main.dir/audio.c.obj -c /willow/main/audio.c
/willow/main/audio.c:47:10: fatal error: generated_cmd_multinet.h: No such file or directory
47 | #include "generated_cmd_multinet.h"
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
@thess
Copy link

thess commented Dec 12, 2024

This file is created by the python script located in the speech_commands folder. The file is only included if Multinet support is enabled by WILLOW_SUPPORT_MULTINET is defined (default in CMakeLists.txt). If generate_commands.py is not successful, no file is created. See generate_speech_commands() in utils.sh. If you are trying to get Multinet working, I'd be interested in how you enabled it in WAS so that this file is automatically generated.

Best to just disable WILLOW_SUPPORT_MULTINET in CMakeLists.txt. If you want Multinet support, you will have to create this file somehow.

@stintel
Copy link
Collaborator

stintel commented Jan 23, 2025 •
edited
Loading

You can work around it by running like this inside the build container:

./utils.sh clean
CI=1 ./utils.sh build

That said, we no longer support multinet. We should clean this up.

stintel added a commit that referenced this issue Feb 18, 2025
@stintel
CMake: make MultiNet support opt-in
cf3e5d1 
We haven't supported MultiNet in any of the Willow or WAS releases.
Let's make it opt-in, rather than disabling it in CI builds. This will
solve the missing generated_cmd_multinet.h file for people trying to
build manually.

It is still possible to enable MultiNet when building manually by
setting the MULTINET environment variable, we will not provide support
for any issues related to it. Issues will be closed without resolution.

Closes: #382
stintel added a commit that referenced this issue Feb 18, 2025
@stintel
CMake: make MultiNet support opt-in
fa1f509 
We haven't supported MultiNet in any of the Willow or WAS releases.
Let's make it opt-in, rather than disabling it in CI builds. This will
solve the missing generated_cmd_multinet.h file for people trying to
build manually.

It is still possible to enable MultiNet when building manually by
setting the MULTINET environment variable, but we will not provide
support for any issues related to it. Issues will be closed without
resolution.

Closes: #382
stintel added a commit that referenced this issue Feb 18, 2025
@stintel
CMake: make MultiNet support opt-in
1ff2c1f 
We haven't supported MultiNet in any of the Willow or WAS releases.
Let's make it opt-in, rather than disabling it in CI builds. This will
solve the missing generated_cmd_multinet.h file for people trying to
build manually.

It is still possible to enable MultiNet when building manually by
setting the MULTINET environment variable, but we will not provide
support for any issues related to it. Issues will be closed without
resolution.

Closes: #382
stintel added a commit that referenced this issue Feb 18, 2025
@stintel
build: make MultiNet support opt-in
4f8803e 
We haven't supported MultiNet in any of the Willow or WAS releases.
Let's make it opt-in, rather than disabling it in CI builds. This will
solve the missing generated_cmd_multinet.h file for people trying to
build manually.

It is still possible to enable MultiNet when building manually by
setting the MULTINET environment variable, but we will not provide
support for any issues related to it. Issues will be closed without
resolution.

Closes: #382
@stintel stintel mentioned this issue Feb 18, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

build: make MultiNet support opt-in toverainc/willow
3 participants
@stintel @thess @hursto75