After a bit of googling it was apparent that the .ino file only differed from regular C++ files in that a preprocessor would run on it before compilation to insert a header include.
So lo and behold a file that looks like this:
myApp.inocan be converted into:
-------
void setup()
{
//do some setup
}
void loop()
{
//do cool stuff here
}
-------
main.cpp
-------
#include "application.h"
void setup()
{
//do some setup
}
void loop()
{
//do cool stuff here
}
-------
by simply renaming the file and adding the application.h include.
It is a little strange not to have a main method in this file but I assume the set up is similar to arduino where the main method is hidden away and you are only given the hooks into it by implementing setup() and loop()
hi. have u tried it before? like converting from blink test .ino to .cpp?
ReplyDeleteYes I have tried it with the blink test.
DeleteCreate a file blink.cpp with the following contents:
#######################################
#include "application.h"
int led1 = D0;
int led2 = D7;
void setup() {
pinMode(led1, OUTPUT);
pinMode(led2, OUTPUT);
}
void loop() {
digitalWrite(led1, HIGH);
digitalWrite(led2, HIGH);
delay(1000);
digitalWrite(led1, LOW);
digitalWrite(led2, LOW);
delay(1000);
}
#######################################
Notice the only difference with the .ino version is the additional include statement.
You can compile and flash this program as usual through the CLI.
Then you can see the light blinking away as usual.
More info here -> http://codefrieze.blogspot.co.uk/2015/08/using-particle-cli-on-ubuntu-1404.html