MansOS Makefiles - Revision history

Leo: /* Makefile basics */

2010-08-19T11:43:44Z

‎Makefile basics

Leo: /* Running the make */

2010-08-19T11:42:05Z

‎Running the make

Samofals: /* Creating the application Makefile */

2008-04-02T06:42:40Z

‎Creating the application Makefile

Leo: /* Running the make */

2008-03-31T08:00:35Z

‎Running the make

Leo: /* Running the make */

2008-03-31T07:56:17Z

‎Running the make

Leo: /* Running the make */

2008-03-30T23:52:06Z

‎Running the make

Leo at 23:35, 30 March 2008

2008-03-30T23:35:27Z

Leo: /* Makefile basics */

2008-03-30T23:33:26Z

‎Makefile basics

Leo: New page: == MansOS and Makefiles == MansOS has a makefile system to speed up the development of your applications and the development of MansOS itself === For application developers === ==== Runn...

2008-03-30T23:30:34Z

New page: == MansOS and Makefiles == MansOS has a makefile system to speed up the development of your applications and the development of MansOS itself === For application developers === ==== Runn...

New page

== MansOS and Makefiles ==

MansOS has a makefile system to speed up the development of
your applications and the development of MansOS itself

=== For application developers ===
==== Running make ====

The common targets of the makefile are as follows:
* '''build''' - (optional, default) build the module or application
* '''upload''' - upload the application
* '''<target>''' - targed platform, such as '''telosb'''

For example, if you want to build your system and then upload it to the telos mote:
make telosb
make telosb upload

==== Creating the application Makefile ====

You need just one Makefile in your project directory.
Examples can be found in the apps directory.
This makefile must define the following variables:

* '''SOURCES''' - a space-delimited list of source (.c) files. It is assumed that the include files reside in the same directory
* '''MODULE''' - the module name being developed. This could be the application name.
* '''PROJDIR''' - most likely the current directory $(CURDIR) containing the application files.

For example:
# My makefile
SOURCES = main.c
MODULE = MySystem
PROJDIR = $(CURDIR)

Optional:
* '''INCLUDES''' - space-delimited list of include file directories. The project directory itself is included by default.

The makefile must end with the definition of path to MansOS system MOSROOT and include of the main MansOS Makefile, like this:

ifndef MOSROOT
MOSROOT = /home/elo/c/elo/WSN/projects/MansOS/svn
endif

# Include the main makefile
include ${MOSROOT}/mos/make/Makefile

=== For MansOS developers ===

Add path(s) to the source files in the platform makefile.

== Makefile basics ==

For a general info on how to work with makefiles look here:

* [[http://www.cs.cmu.edu/cgi-bin/info2www?(make.info)Top]]

@@ Line 58: / Line 58: @@
 For a general info on how to work with makefiles look here:
+* [http://www.gnu.org/software/make/manual/make.html GNU Make manual]
 * [http://www.cs.cmu.edu/cgi-bin/info2www?(make.info)Top (make.info) at CMU]

@@ Line 10: / Line 10: @@
 * '''''<target>''''' - targed platform, such as '''telosb'''
 * '''clean''' - clear the generated object and other files.
-* '''cleanall''' - clear everything from the output (build/) directory
-* '''objs''' - compile only, generate all object files
-* '''printenv''' - print the major variables (for debugging make)
 For example, if you want to build your system and then upload it to the telos mote:
   make telosb
   make telosb upload
+Read on about the various [[MansOS_Platforms]] and options available for make.
 ==== Creating the application Makefile ====

@@ Line 49: / Line 49: @@
   include ${MOSROOT}/mos/make/Makefile
+Another way to setup MOSROOT, is to write in bash before executing make:
+   export MOSROOT=/home/raimonds/MansOS_Work
 == For MansOS developers ==

@@ Line 7: / Line 7: @@
 The common targets of the makefile are as follows:
 * '''build''' - (optional, default) build the module or application
-* '''upload''' - upload the application
+* '''upload''' - upload the application via hard wire (USB or COM). Make will upload to the first attached mote it finds.
 * '''''<target>''''' - targed platform, such as '''telosb'''
 * '''clean''' - clear the generated object and other files.

@@ Line 9: / Line 9: @@
 * '''upload''' - upload the application
 * '''''<target>''''' - targed platform, such as '''telosb'''
-* '''clean''' - clear the object and other generated files.
+* '''clean''' - clear the generated object and other files.
+* '''cleanall''' - clear everything from the output (build/) directory

@@ Line 1: / Line 1: @@
+'''MansOS''' has a makefile system to speed up the development of
-== MansOS and Makefiles ==
-MansOS has a makefile system to speed up the development of
 your applications and the development of MansOS itself
-=== For application developers ===
+== For application developers ==
-==== Running make ====
+==== Running the make ====
 The common targets of the makefile are as follows:
@@ Line 46: / Line 44: @@
-=== For MansOS developers ===
+== For MansOS developers ==
 Add path(s) to the source files in the platform makefile.

@@ Line 55: / Line 55: @@
 For a general info on how to work with makefiles look here:
-* [[http://www.cs.cmu.edu/cgi-bin/info2www?(make.info)Top]]
+* [http://www.cs.cmu.edu/cgi-bin/info2www?(make.info)Top (make.info) at CMU]
+Here is an example of a makefile system for Java development:
+* [http://geosoft.no/development/javamake.html Javamake at Geosoft]