Ino: Command Line Toolkit for Arduino Hardware
Ino tools webpage:
Ino is a command line toolkit for working with Arduino hardware
It allows you to:
- Quickly create new projects
- Build a firmware from multiple source files and libraries
- Upload the firmware to a device
- Perform serial communication with a device (aka serial monitor)
Ino may replace Arduino IDE UI if you prefer to work with command line and an editor of your choice or if you want to integrate Arduino build process to 3-rd party IDE.
Ino is based on make to perform builds. However Makefiles are generated automatically and you’ll never see them if you don’t want to.
Features
- Simple. No build scripts are necessary.
- Out-of-source builds. Directories with source files are not cluttered with intermediate object files.
- Support for *.ino and *.pde sketches as well as raw *.c and *.cpp.
- Support for Arduino Software versions 1.x as well as 0.x.
- Automatic dependency tracking. Referred libraries are automatically included in the build process. Changes in *.h files lead to recompilation of sources which include them.
- Pretty colorful output.
- Support for all boards that are supported by Arduino IDE.
- Fast. Discovered tool paths and other stuff is cached across runs. If nothing has changed, nothing is build.
- Flexible. Support for simple ini-style config files to setup machine-specific info like used Arduino model, Arduino distribution path, etc just once.
(Homepage)
Comments (0)
This post does not have any comments. Be the first to leave a comment below.
Featured Product
ST Robotics Develops the Workspace Sentry for Collaborative Robotics
The ST Robotics Workspace Sentry robot and area safety system are based on a small module that sends an infrared beam across the workspace. If the user puts his hand (or any other object) in the workspace, the robot stops using programmable emergency deceleration. Each module has three beams at different angles and the distance a beam reaches is adjustable. Two or more modules can be daisy chained to watch a wider area. "A robot that is tuned to stop on impact may not be safe. Robots where the trip torque can be set at low thresholds are too slow for any practical industrial application. The best system is where the work area has proximity detectors so the robot stops before impact and that is the approach ST Robotics has taken," states President and CEO of ST Robotics David Sands.
