Re: [riot-devel] [PROJECT][RIOT-OS][STM32-L152RE]

2015-02-24 Thread Thomas Eichinger
Hi Tararaina, for helping you with your problem, could share a link to your code with us? Or/and could you run `make` with command line option `QUIET=0` and paste the output to pastepin [1] or a gist [2]? Best, Thomas [1] pastebin.com [2] gist.github.com On 24 Feb 2015, at 15:19 CET(+0100),

Re: [riot-devel] Repository for Docker builds

2015-02-24 Thread Matthias Waehlisch
Hi, +1 for riotdocker, riotbuild is confusing. Cheers matthias On Tue, 24 Feb 2015, Joakim Gebart wrote: riotdocker is more descriptive for the github repo name, I like it. Best regards, Joakim On Feb 24, 2015 8:20 AM, Oleg Hahm oliver.h...@inria.fr wrote: Hi Joakim!

Re: [riot-devel] Repository for Docker builds

2015-02-24 Thread Joakim Gebart
riotdocker is more descriptive for the github repo name, I like it. Best regards, Joakim On Feb 24, 2015 8:20 AM, Oleg Hahm oliver.h...@inria.fr wrote: Hi Joakim! What is a suitable name for the new repo? I have been using riotbuild for my Docker development at

Re: [riot-devel] RPL (and more generally, networking) on border router

2015-02-24 Thread Lotte Steenbrink
Hi Emmanuel, hi all, Am 23.02.2015 um 17:42 schrieb Emmanuel Baccelli emmanuel.bacce...@inria.fr: Hi Lotte, on your blog posts for watr.li you mention using R-idge + 6LoWPAN on a Pi, and you mention using RPL (or AODV) on top of that, in the near future, which is a very interesting

Re: [riot-devel] Changing the workflow.

2015-02-24 Thread Attilio Dona
Just for add a bit of documentation for helping discovering the best workflow: http://nvie.com/posts/a-successful-git-branching-model/ The post contains some good points in my opinion, for example the guideline that a feature branch have to exists in developer repo and not in origin. ciao

Re: [riot-devel] Changing the workflow.

2015-02-24 Thread Martine Lenders
Hi Attilio, 2015-02-24 16:30 GMT+01:00 Attilio Dona attilio.d...@gmail.com: Just for add a bit of documentation for helping discovering the best workflow: http://nvie.com/posts/a-successful-git-branching-model/ The post contains some good points in my opinion, for example the guideline

Re: [riot-devel] [PROJECT][RIOT-OS][STM32-L152RE]

2015-02-24 Thread Jan Wagner
Hi Tara, how was the lib.a created? - maybe you can use arm-none-linux-gnueabi-readelf to get more info about the library. to understand your problem better - so you used the mbed export to gcc functionality and now you get errors like in this post fe. (different cpu etc)

Re: [riot-devel] Changing the workflow.

2015-02-24 Thread Oleg Hahm
Hi Martine! In general I like the concept and I think various people (including myself) proposed a similar workflow already in the past, but it was always rejected (IMO for good reasons), because of the introduced overhead and missing personal resources. I don't get this argument: With my

Re: [riot-devel] Changing the workflow.

2015-02-24 Thread Martine Lenders
Hi, 2015-02-21 20:06 GMT+01:00 Ludwig Ortmann ludwig.ortm...@fu-berlin.de: Hi, On Sat, Feb 21, 2015 at 07:02:58PM +0100, Martine Lenders wrote: This is why I propose we change to a slightly adapted topic branch workflow (also known as feature branch) workflow [1]: - the main

Re: [riot-devel] [PROJECT][RIOT-OS][STM32-L152RE]

2015-02-24 Thread Martine Lenders
Hi Tara, have you tried to include your external library as an external module [1]? Kind regards, Martine [1] https://github.com/RIOT-OS/RIOT/wiki/Creating-external-modules 2015-02-24 15:19 GMT+01:00 Tararaina Klipffel tei...@gmail.com: Hello, We are 4 French students in engineering school.

Re: [riot-devel] Switch to BSD?

2015-02-24 Thread Oleg Hahm
Dear RIOTers, I just found the eCos license: [1] http://ecos.sourceware.org/license-overview.html It's basically a modified version of the GPL with linker exception. The interesting point: it is officially recognised as a GPL-compatible Free Software License:

Re: [riot-devel] [PROJECT][RIOT-OS][STM32-L152RE]

2015-02-24 Thread Martine Lenders
Hi Tara, [quotet from your digest reply]: I tried to include my external library as an external module, but it doesn't work ! I have still the same issue. When we're trying to compile it, it seems that the makefile isn't able to find the functions include in this libmbed.a. As you can see in

Re: [riot-devel] [PROJECT][RIOT-OS][STM32-L152RE]

2015-02-24 Thread Martine Lenders
Hi again 2015-02-24 20:16 GMT+01:00 Martine Lenders authmille...@gmail.com: […] 2 things: Have you added the Makefile.base to the directory YOUR_PATH/RIOT-master/examples/test? Sorry I meant the Makefile, not the Makefile.base here. ___ devel

Re: [riot-devel] Switch to BSD?

2015-02-24 Thread Matthias Waehlisch
Hi Oleg, On Wed, 25 Feb 2015, Oleg Hahm wrote: I thought that we already decided to exclude exotic licenses. Yes. GPL + Linker Exception is not exotic. but the name (or license branding). We had this discussion before. Rather unknown licenses need to be explained. Using eCos license

Re: [riot-devel] Switch to BSD?

2015-02-24 Thread Adam Hunt
I'd be willing to bet that GNU Classpath is one of the oldest projects licensed under the GPL with a linking exception. Classpath is distributed under the terms of the GNU General Public License with the following clarification and special exception. Linking this library statically or

Re: [riot-devel] Changing the workflow.

2015-02-24 Thread Adam Hunt
I really like the idea of task force branches (OTA, net, filesystem, platform, etc..). They seem somewhat reminiscent of Linux's *net, net-next* and similar trees. Would they be implemented as git branches within the main repository (e.g https://github.com/RIOT-OS/RIOT/OTA) or fully independent

Re: [riot-devel] Switch to BSD?

2015-02-24 Thread Oleg Hahm
Hi Matthias! I thought that we already decided to exclude exotic licenses. Yes. GPL + Linker Exception is not exotic. With respect to this specific license: (1) We cannot use the license because the license text is specific to eCos (e.g., eCos is distributed [...]). And original

Re: [riot-devel] Switch to BSD?

2015-02-24 Thread Matthias Waehlisch
Hi Oleg, I thought that we already decided to exclude exotic licenses. With respect to this specific license: (1) We cannot use the license because the license text is specific to eCos (e.g., eCos is distributed [...]). (2) We should not use the license because it is not approved by