kaspar, it works if all include are in the root folder otherwise there
is linking problem ("undefined reference to" function, error).Attilio, yes it works thanks, but I think we shouldn't have to create a module for that. Anyway, let's see if someone can provide another solution. Cheers, 2015-10-14 12:25 GMT+02:00 Attilio Dona <attilio.d...@gmail.com>: > In app/Makefile: > > DIRS += thingsA thingsB > > INCLUDES += -I$(CURDIR)/thingsA -I$(CURDIR)/thingsB > > USEMODULE += thingsA thingsB > > in thingsA and thingsB directory add a Makefile: > > include $(RIOTBASE)/Makefile.base > > > Something like that should work ... but if there is a better solution nice > to know! > > greetings > Attilio > > > On Fri, Oct 9, 2015 at 4:50 PM, Baptiste Clenet <bapcle...@gmail.com> wrote: >> >> Hi all, >> >> I'm building an example (let's called it "app") for RIOT with the >> following structure: >> app/*.c >> app/include/*.h >> app/thingA/*.c >> app/thingA/include*.h >> app/thingB/*.c >> app/thingB/include*.h >> >> How to add the required path in the Makefile? Should I add >> Makefile.base in each folder or is there another way to do it with >> RIOT Makefile ? I couldn't find any example of this structure. >> >> Cheers, >> >> >> -- >> Baptiste >> _______________________________________________ >> devel mailing list >> devel@riot-os.org >> https://lists.riot-os.org/mailman/listinfo/devel > > > > _______________________________________________ > devel mailing list > devel@riot-os.org > https://lists.riot-os.org/mailman/listinfo/devel > -- Baptiste _______________________________________________ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
