Bas Wijnen

> you can do a quick'n'dirty merge of all the boards.txt files using awk: This doesn't work. Files referenced from hardware/foo/boards.txt are supposed to be in hardware/foo/\* (unless they are...

On Mon, May 26, 2014 at 10:04:27PM -0700, Sudar wrote: > I agree that we should make the makefile as platform independent as possible. > But at the same time...

@sej7278 I'm using Debian myself. I want my project to contain a Makefile that looks like: ``` BOARD_TAG = uno include $ARDUINO_MAKEFILE ``` This currently doesn't work on my system...

@sej7278 I think you're misunderstanding me. What I want: distribute my projects to people who aren't programmers, before it is really released (in other words, before I distribute it as...

@tinyladi I'm talking about ARDUINO_MAKEFILE, defined when installing the Makefile, which points to the install location. It makes sure that "include $ARDUINO_MAKEFILE" will work. I can tell my users to...

To be more clear: this is what I want to get rid of: ``` ### This is an example Makefile and it MUST be configured to suit your needs. ```

Yes, I noticed that my comment wasn't as clear as I wanted. > it has to be configured because I use some specific software such as avr-gcc-4.8 and the location...

> i just don't see how you can do "include $ARDUINO_MAKEFILE" without defining it somehow. Of course it should be defined. That's what I'm asking for: please make "define ARDUINO_MAKEFILE...

> The thing is, when you want to use a makefile, you prepare yourself for some hardcore sh*t and that's what fun about it. Yes, _I_ like it, and I...

I'm expecting people to download the zipfile rather than checking out the repository. The submodule approach won't work then, I think. Plus I want to make my code a Debian...