Recent Changes - Search:

References

Notes

edit SideBar

CommandLineBuild

Notes.CommandLineBuild History

Show minor edits - Show changes to output

2011-02-19 00:06 by Jonathan Cook -
Changed line 7 from:
[[http://www.cs.nmsu.edu/~jcook/arduino/resources/Makefile.arduino || Makefile.arduino]]
to:
[[http://www.cs.nmsu.edu/~jcook/arduino/resources/Makefile.arduino | Makefile.arduino]]
Changed line 9 from:
[[http://www.cs.nmsu.edu/~jcook/arduino/resources/Makefile || Makefile]]. In the
to:
[[http://www.cs.nmsu.edu/~jcook/arduino/resources/Makefile | Makefile]]. In the
2011-02-19 00:05 by Jonathan Cook -
Added lines 1-26:
Since the arduino IDE simply invokes external tools, it should be fairly simple to
create a Makefile that does the same for us, and then use the good old command line
for development.

I dumped all the options that the arduino IDE invokes the compiler and other tools
with, and put them in a Gnu makefile: the rules are in
[[http://www.cs.nmsu.edu/~jcook/arduino/resources/Makefile.arduino || Makefile.arduino]]
and an example use of this file is in
[[http://www.cs.nmsu.edu/~jcook/arduino/resources/Makefile || Makefile]]. In the
second file, the TARGET name is the sketch name (e.g., "Lab1" means there is a
"Lab1.pde" file in the current directory, along with any other files. Other
source files need to be listed (by their object file name) in the OTHER_OBJS
variable.

The Makefile will support assembly source files, too.

Running "make" should build the executable and all the files needed for upload.

Running "make upload" should properly upload your program to your arduino board.

I don't yet know how to use a command-line tool to do serial comm with the program.
Email me if you know how.


Edit - History - Print - Recent Changes - Search
Page last modified on 2011-02-19 00:06