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

Cloud compile - Files goes to original directory #3

Closed
kennethlimcp opened this issue Feb 25, 2014 · 4 comments
Closed

Cloud compile - Files goes to original directory #3

kennethlimcp opened this issue Feb 25, 2014 · 4 comments

Comments

@kennethlimcp
Copy link
Contributor

So i saved an ino as, blinky.ino on my desktop.

Arduino would create a DIR called blinky and blinky.ino is inside.

To make it easier to call the blinky.ino, i placed it in e:\ drive and run: spark cloud compile e:\blinky.ino

The execution is successful but the bin file appears in my desktop\blinky folder

If i delete the desktop\blinky folder, the compilation is successful but the bin file went to my USER directory (C:\Users\Kenneth Lim)

Maybe it only happens in windows

@dmiddlecamp
Copy link
Contributor

I think right now the CLI will download the firmware binary to the current working directory, or wherever you ran the command from. It sounds like it would be more straightforward to use the directory of the target file?

@kennethlimcp
Copy link
Contributor Author

@dmiddlecamp Ah i get what you mean!

How is it like on Mac and linux? Since the terminal on them doesn't really have a base directory specified when running.

I CHDIR on the Command prompt and the bin file appeared where it should be.

Just thinking how we can make it easier for the 1st time users 👍

@dmiddlecamp
Copy link
Contributor

I'm thinking just displaying the full path makes it easier to know where the downloaded file ended up, what do you think?

@kennethlimcp
Copy link
Contributor Author

It's easy to tell now as i have tested it out but having the .bin where the original source code is might be better since the user is frequently working in that dir

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

No branches or pull requests

2 participants