Skip to content

Conversation

@per1234
Copy link

@per1234 per1234 commented Jan 8, 2018

The Arduino IDE requires that a sketch be located in a folder of the same name. When opening a file that does not meet this requirement the Arduino IDE presents a dialog:

The file "DevilRemote.ino" needs to be inside a sketch folder named "DevilRemote".
Create this folder,  move the file, and continue?

After clicking "OK" the Arduino IDE currently moves only the file DevilRemote.ino to the new folder, leaving behind the other sketch files. This causes compilation of the sketch to fail:

fatal error: default_config.h: No such file or directory

Although the repository name does match the sketch name, it is common for people to use GitHub's Clone or Download > Download ZIP feature to download sketches, rather than doing a Git clone, and GitHub appends the branch/tag/commit to the downloaded folder name, which will cause the folder to still not match the sketch name.

The Arduino IDE requires that a sketch be located in a folder of the same name. When opening a file that does not meet this requirement the Arduino IDE presents a dialog:

The file "DevilRemote.ino" needs to be inside a sketch folder named "DevilRemote".
Create this folder,  move the file, and continue?

After clicking "OK" the Arduino IDE currently moves only the file DevilRemote.ino to the new folder, leaving behind the other sketch files. This causes compilation of the sketch to fail "fatal error: default_config.h: No such file or directory".

Although the repository name does match the sketch name, it is common for people to use GitHub's "Clone or Download > Download ZIP" feature to download sketches, rather than doing a Git clone, and GitHub appends the branch/tag/commit to the downloaded folder name, which will cause the folder to still not match the sketch name.
@dersimn
Copy link
Owner

dersimn commented Jan 16, 2018

That's fault is on the user in my opinion.

If this project reaches something close to "productive" level, I'll consider publishing major versions via Github Releases - an probably add some schematics.

@per1234
Copy link
Author

per1234 commented Jan 16, 2018

So you have no interest in merging this PR?

@dersimn
Copy link
Owner

dersimn commented Jan 29, 2018

I'll think about it, because splitting the "source code" and "docs" folder kinda makes sense, but all repositories I'm currently working on have the .ino files in the top-level folder. Never had a problem with that.

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

Successfully merging this pull request may close these issues.

2 participants