I haven't done much ports work, but from an Arduino perspective this is
correct so ok jj@ if that has any worth.
Den 19 jun 2014 21:56 skrev "Daniel Bolgheroni" :
> On Thu, Jun 19, 2014 at 03:06:10PM +0100, Stuart Henderson wrote:
> >
> > Say the port is updated to 1.5.x, these -D lines will need
On Thu, Jun 19, 2014 at 03:06:10PM +0100, Stuart Henderson wrote:
>
> Say the port is updated to 1.5.x, these -D lines will need to be
> updated, right?
Until now, we are fine using ARDUINO=100 even if we update to 1.5.x.
This macro is being used, as of today, only to control the renaming
scheme f
On 2014/06/19 00:24, Daniel Bolgheroni wrote:
> On Wed, Jun 18, 2014 at 10:10:24AM +0100, Stuart Henderson wrote:
> >
> > This file is somewhat hidden in the port. What are the consequences of
> > it not being updated if the port is updated?
>
> I think the main issue here is that if we don't def
On Wed, Jun 18, 2014 at 10:10:24AM +0100, Stuart Henderson wrote:
>
> This file is somewhat hidden in the port. What are the consequences of
> it not being updated if the port is updated?
I think the main issue here is that if we don't define ARDUINO >= 100,
even libraries already in the current
On 2014/06/18 02:29, Daniel Bolgheroni wrote:
> Hi,
>
> In the revisions.txt file from Arduino source code, in the section
> related to changes from version 0022 to 1.0, there is this statement:
>
> * The WProgram.h file, which provides declarations for the Arduino API,
> has been renamed to Ar
Hi,
In the revisions.txt file from Arduino source code, in the section
related to changes from version 0022 to 1.0, there is this statement:
* The WProgram.h file, which provides declarations for the Arduino API,
has been renamed to Arduino.h. To create a library that will work in
both Arduin
