You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The libDaisy capitalization is inconsistent across the tools in DaisyExamples. The submodule is set to always clone into libdaisy, and some of the helper.py commands create lower case libDaisy references. Since the repo name is libDaisy, it's probably best to get everything aligned with that capitalization.
This was particularly annoying for mac / linux users because the unix cpp configuration for vscode assumed a capital D.
The text was updated successfully, but these errors were encountered:
this should be resolved, but I know people may still run into an issue with previous clones (though at this point, even with wrong spelling it compiles on the mac OS machine I was testing on ... So we'll see I suppose).
I'll leave this open for a bit with this note:
If you get a can't find libDaisy related error -- you can either manually rename the "libdaisy" folder to "libDaisy", or reclone the repo to resolve the issue.
Hello, I'm on a linux platform.
It's a problem when using helper.py for creating a new project.
The makefile won't work as it refers to "libdaisy" instead of libDaisy.
Easy to fix, though.
The libDaisy capitalization is inconsistent across the tools in DaisyExamples. The submodule is set to always clone into
libdaisy
, and some of thehelper.py
commands create lower case libDaisy references. Since the repo name is libDaisy, it's probably best to get everything aligned with that capitalization.This was particularly annoying for mac / linux users because the unix cpp configuration for vscode assumed a capital D.
The text was updated successfully, but these errors were encountered: