osd-contiki/examples/hello-world/Makefile

#Note to AVR Raven users: Output goes to UART1, not the LCD. To see it,
#make TARGET=avr-raven hello-world.elf
#Load the .elf in AVR Studio and connect a hapsim terminal to the 1284p simulation.

CONTIKI_PROJECT = hello-world
all: $(CONTIKI_PROJECT)

#UIP_CONF_IPV6=1

CONTIKI = ../..
include $(CONTIKI)/Makefile.include
Allow non-ipv6 build, e.g. Hello World 2010-11-12 18:15:00 +01:00			`#Note to AVR Raven users: Output goes to UART1, not the LCD. To see it,`
			`#make TARGET=avr-raven hello-world.elf`
			`#Load the .elf in AVR Studio and connect a hapsim terminal to the 1284p simulation.`

Many project Makefiles build just one Contiki binary. Up to now the name of this binary was only available to the 'all' goal as prerequisite. So it was possible to create a non-project-specific rule to i.e. load that binary into the target device. Therefore I introduced the make variable CONTIKI_PROJECT. Now a typical project Makefile starts with: CONTIKI_PROJECT = hello-world all: $(CONTIKI_PROJECT) 2008-05-26 09:37:24 +02:00			`CONTIKI_PROJECT = hello-world`
			`all: $(CONTIKI_PROJECT)`
A really simple Contiki program, intended to show how the build system works and how to write simple Contiki programs 2006-10-02 23:46:46 +02:00
Allow non-ipv6 build, e.g. Hello World 2010-11-12 18:15:00 +01:00			`#UIP_CONF_IPV6=1`

Many project Makefiles build just one Contiki binary. Up to now the name of this binary was only available to the 'all' goal as prerequisite. So it was possible to create a non-project-specific rule to i.e. load that binary into the target device. Therefore I introduced the make variable CONTIKI_PROJECT. Now a typical project Makefile starts with: CONTIKI_PROJECT = hello-world all: $(CONTIKI_PROJECT) 2008-05-26 09:37:24 +02:00			`CONTIKI = ../..`
A really simple Contiki program, intended to show how the build system works and how to write simple Contiki programs 2006-10-02 23:46:46 +02:00			`include $(CONTIKI)/Makefile.include`