Since Copy to current project pulls in the complete library structure including the examples folder, a project build will fail.
Only after removing the examples folder (or the relevant .ino or .cpp files) the project would build.
But not for automaticly migrated libraries due to the "compatiblity stub header" that just contains the #include "../libName.h" file(s).
So you'd also need to remove all of these.
Either don't download the offending files or make the upload or build farm ignore these extra files.
Very involed users might understand the reason for a breaking build when moving from Add to current project to Copy to current project, but most users will just get confused and annoyed by that.
Since
Copy to current projectpulls in the complete library structure including the examples folder, a project build will fail.Only after removing the examples folder (or the relevant
.inoor.cppfiles) the project would build.But not for automaticly migrated libraries due to the "compatiblity stub header" that just contains the
#include "../libName.h"file(s).So you'd also need to remove all of these.
Either don't download the offending files or make the upload or build farm ignore these extra files.
Very involed users might understand the reason for a breaking build when moving from
Add to current projecttoCopy to current project, but most users will just get confused and annoyed by that.