[LTP] [PATCH 2/3] Make system enhancements, Draft 1

[LTP] [PATCH 2/3] Make system enhancements, Draft 1

[Garrett Cooper]

[-- Attachment #1: Type: text/plain, Size: 958 bytes --]

1. Write up a document on how to use the new Make system
(README.mk-devel), so others may assist in the work that we're
spearheading at Cisco and contributing back to LTP, and we can begin
dropping the adhoc Makefiles.
2. Add master_rules.mk which contains canned rules for environment
setup, leaf directories, and trunk directories to reduce Make logic
noise in the existing LTP Makefile's. This is a more condensed and
straightforward version of the original master_rules.mk file
contributed and never integrated into LTP in the past.
3. Add master_include.mk, a file which stands as the defacto include
Makefile for all . This was created out of the comment provided by
Mike Frysinger w.r.t. a master include file.

Note: This patch has been largely tested, but some of the additional
functionality and rework in generic_trunk_target needs to be tested
more prior to commit; hence it's a Draft 1 patch.

Signed-off-by: Garrett Cooper <yanegomi@gmail.com>

[-- Attachment #2: Make-system-enhancements.diff --]
[-- Type: application/octet-stream, Size: 14696 bytes --]

Index: README.mk-devel
===================================================================
RCS file: README.mk-devel
diff -N README.mk-devel
--- /dev/null	1 Jan 1970 00:00:00 -0000
+++ README.mk-devel	6 Jul 2009 22:57:08 -0000
@@ -0,0 +1,127 @@
+==============================
+Introduction
+==============================
+
+The following document briefly describes the steps and methodologies used for
+the new and improved Makefile system.
+
+==============================
+The Problem
+==============================
+
+The problem with the old Makefile system is that it was very difficult to
+maintain and it lacked any sense of formal structure, thus developing for LTP
+and including new targets was very more difficult than it should have been
+(maintenance). Furthermore, cross-compilation was impossible due to the fact
+that the Makefiles didn't support a prefixing system, and the appropriate
+implicit / static rules hadn't been configured to compile into multiple object
+directories (easy of use / functionality). Finally, there wasn't a means to
+setup dependencies between components, such that if a component required
+libltp.a in order to compile, it would go off and compile libltp.a first
+(easy of use).
+
+These items needed to be fixed to reduce maintenance nightmares for the
+development community contributing to LTP.
+
+==============================
+Design
+==============================
+
+The system was designed such that including a single GNU Makefile compatible
+set in each new directory component is all that's essentially required to
+build the system. Here's an example of how one would accomplish that:
+
+.../foo/Makefile:
+#
+# Copyright disclaimer goes here -- please use GPLv2.
+#
+
+srcdir			?= ../
+
+include $(srcdir)/include/mk/master_include.mk
+
+$(eval $(generic_dir_target))
+
+.../foo/bar/Makefile:
+#
+# Copyright disclaimer goes here -- please use GPLv2.
+#
+
+srcdir			?= ../
+
+include $(srcdir)/include/mk/master_include.mk
+
+$(eval $(generic_leaf_target))
+
+==============================
+Make Rules and Make Variables
+==============================
+
+When using make rules, avoid writing adhoc rules like:
+
+[prog]: [dependencies]
+	cc -I../../include $(CFLAGS) $(CPPFLAGS) $(LDFLAGS) $(LOADLIBES) \
+	    -o [prog] [dependencies]
+
+etc. This makes cross-compilation and determinism difficult, if not impossible.
+Besides, implicit rules are your friends and as long as you use `MAKEOPTS=;' in
+the top-level caller, the compile will complete successfully, assuming all other
+prerequisites have been fulfilled (libraries, headers, etc).
+
+$(CC)			: The system compiler. Please avoid sending in options
+			  that should be in $(CFLAGS), 
+
+$(CFLAGS)		: What to pass in to $(CC)
+
+==============================
+Make System Variables
+==============================
+
+A series of variables are used within the make system that direct what actions
+need to be taken. Rather than me listing the variables here, please instead
+refer to the comments contained in `.../include/mk/master_rules.mk'.
+
+==============================
+Guidelines and Recommendations
+==============================
+
+Of course, the GNU Make manual is key to understanding the Make system, but
+here are the following sections and chapters I suggest reviewing:
+
+- implicit rules: http://www.gnu.org/software/make/manual/make.html#Implicit-Rules
+- variables and expansion: http://www.gnu.org/software/make/manual/make.html#Using-Variables
+- origin use: http://www.gnu.org/software/make/manual/make.html#Origin-Function
+- vpath use: http://www.gnu.org/software/make/manual/make.html#Directory-Search
+
+==============================
+Before Committing
+==============================
+
+One should rebuild from scratch before committing. Here's an example of how to
+do that:
+#!/bin/sh
+
+TOOLS_PATH=/path/to/tools
+
+# Replace [options] with any make specific options and variables, for each
+# step, example: -j 4, DESTDIR=/path/for/install, etc.
+make ac-clean ac-maintainer-clean distclean maintainer-clean [options]
+make \
+  ACLOCAL=$TOOLS_PATH/bin/aclocal \
+  AUTOCONF=$TOOLS_PATH/bin/autoconf \
+  AUTOHEADER=$TOOLS_PATH/bin/autoheader \
+  AUTOMAKE=$TOOLS_PATH/bin/automake \
+  autotools
+./configure [options]
+make all [options]
+make install [options]
+
+==============================
+Other Errata
+==============================
+
+- This system (in its current form) supports cross-compilation out of a single
+directory. Object directory support will be completed soon to properly enable
+cross-compilation. This is required to avoid sporadic Make-related errors.
+
+# vim:
Index: include/mk/master_include.mk
===================================================================
RCS file: include/mk/master_include.mk
diff -N include/mk/master_include.mk
--- /dev/null	1 Jan 1970 00:00:00 -0000
+++ include/mk/master_include.mk	6 Jul 2009 22:57:08 -0000
@@ -0,0 +1,28 @@
+#
+#    Master include Makefile.
+#
+#    Copyright (C) 2009, Cisco Systems Inc.
+#
+#    This program is free software; you can redistribute it and/or modify
+#    it under the terms of the GNU General Public License as published by
+#    the Free Software Foundation; either version 2 of the License, or
+#    (at your option) any later version.
+#
+#    This program is distributed in the hope that it will be useful,
+#    but WITHOUT ANY WARRANTY; without even the implied warranty of
+#    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+#    GNU General Public License for more details.
+#
+#    You should have received a copy of the GNU General Public License along
+#    with this program; if not, write to the Free Software Foundation, Inc.,
+#    51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+#
+# Garrett Cooper, July 2009
+#
+# Copyright (c) 2009 by Cisco Systems, Inc.
+# All rights reserved
+#
+
+# Only include config.mk for non-clean based targets.
+-include $(srcdir)/include/mk/config.mk
+-include $(srcdir)/include/mk/master_rules.mk
Index: include/mk/master_rules.mk
===================================================================
RCS file: include/mk/master_rules.mk
diff -N include/mk/master_rules.mk
--- /dev/null	1 Jan 1970 00:00:00 -0000
+++ include/mk/master_rules.mk	6 Jul 2009 22:57:08 -0000
@@ -0,0 +1,270 @@
+#
+#    Master rules Makefile.
+#
+#    Copyright (C) 2009, Cisco Systems Inc.
+#
+#    This program is free software; you can redistribute it and/or modify
+#    it under the terms of the GNU General Public License as published by
+#    the Free Software Foundation; either version 2 of the License, or
+#    (at your option) any later version.
+#
+#    This program is distributed in the hope that it will be useful,
+#    but WITHOUT ANY WARRANTY; without even the implied warranty of
+#    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+#    GNU General Public License for more details.
+#
+#    You should have received a copy of the GNU General Public License along
+#    with this program; if not, write to the Free Software Foundation, Inc.,
+#    51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+#
+# Garrett Cooper, July 2009
+#
+# Copyright (c) 2009 by Cisco Systems, Inc.
+# All rights reserved
+#
+
+# Get the absolute path for the source directory.
+ifeq ($(origin srcdir),undefined)
+$(error srcdir isn\'t defined.)
+endif
+
+# Where's the root source directory?
+srcdir				:= $(abspath $(srcdir))
+# Where's the root object directory?
+objroot				?= $(srcdir)
+# Where are we currently located in the object and source tree?
+relpath				:= $(subst $(objroot),,$(CURDIR))
+# Where are we going to install the files?
+INSTALL_DIR			?= $(CURDIR)
+
+# We can piece together where we're located in the source and object trees with
+# just these two vars and $(CURDIR).
+export srcdir objroot
+
+# Default source search path. Modify as necessary, but I would call that
+# poor software design if you need more than one search directory, and
+# would suggest creating a general purpose static library to that end.
+vpath	%.c			$(srcdir)/$(relpath)
+
+# .o -> .a lib pattern rule.
+%.a:
+ifeq ($^,)
+	$(error Cowardly refusing to create empty archive.)
+endif
+	$(AR) -rc $@ $^
+
+#
+# get_make_dirs
+#
+# Sets the make directories in $(SUBDIRS), and then subsequently filters out
+# the subdirectories based on $(FILTER_OUT_DIRS).
+#
+define get_make_dirs
+
+SUBDIRS				?= $$(patsubst %/Makefile,%,$$(wildcard */Makefile))
+
+ifneq ($$(strip $$(SUBDIRS)),)		# We have directories to parse.
+ifneq ($$(strip $$(FILTER_OUT_DIRS)),)	# We have directories to filter-out.
+SUBDIRS				:= $$(filter-out $$(FILTER_OUT_DIRS),$$(SUBDIRS))
+endif
+endif
+
+endef
+
+define generic_target_env_setup
+
+ifeq ($$(origin MAKE_TARGETS),undefined)
+MAKE_TARGETS			:= $$(notdir $$(patsubst %.c,%,$$(wildcard $$(srcdir)/$$(relpath)/*.c)))
+endif
+
+# Don't append $(MAKE_TARGETS) unless it is non-NUL length.
+ifneq ($$(strip $$(MAKE_TARGETS)),)
+
+$$(MAKE_TARGETS): $$(MAKE_DEPS)
+
+CLEAN_TARGETS			+= $$(MAKE_TARGETS) $$(addsuffix .o,$$(MAKE_TARGETS))
+INSTALL_TARGETS			+= $$(MAKE_TARGETS)
+
+endif
+
+INSTALL_MODE			?= 00775
+
+ifneq ($(filter-out %install,$(MAKECMDGOALS)),)
+ifeq ($$(origin INSTALL_DIR),undefined)	# Not set by the user
+$$(error INSTALL_DIR is not set)
+else
+ifeq ($$(strip $$(INSTALL_DIR)),)	# Set to a NUL-length string
+$$(error INSTALL_DIR is not set to a non-NUL string)
+endif					# END: INSTALL_DIR NUL-length string.
+endif					# END: undefined
+endif					# END: Not install
+
+INSTALL_FILES			:= $$(addprefix $$(DESTDIR)/$$(prefix)/$$(INSTALL_DIR)/,$$(notdir $$(INSTALL_TARGETS)))
+
+CLEAN_TARGETS			+= $$(INSTALL_FILES)
+
+$$(DESTDIR)/$$(prefix)/$$(INSTALL_DIR):
+	mkdir -p $$@
+
+endef
+
+#
+# generic_leaf_target
+#
+# Generate a set of basic targets (all, clean, install) for a leaf directory
+# (no subdirectories).
+#
+# In order to properly emulate pre- and post- behavior, a pre-install and
+# _install target are generated as well. The flow for install is as follows:
+#
+# pre-install -> $(INSTALL_FILES) -> install
+#
+# Helpful variables are:
+#
+# $(MAKE_DEPS)			: What to execute before all.
+# $(MAKE_TARGETS)		: What to execute as direct dependencies of
+# 				  all.
+# 				  1. Defaults to the basename of the targets
+# 				     produced by the %.c -> % implicit pattern
+# 				     rules, e.g. the MAKE_TARGET in a directory
+# 				     like the following:
+#
+#				  $$ ls /bar
+# 				  foo.c
+#
+#				     Would be `foo'. Similarly, the following
+#				     dir structure:
+#
+#				  $$ ls /bar
+# 				  foo.c zanzibar.c
+#
+#				     Would be `foo zanzibar'.
+#
+#				  2. If you define MAKE_TARGETS as an empty
+#				     string, this will override the defaults.
+#				     I did this to avoid providing too much
+#				     rope to hang one's self in the event of
+#				     unwanted behavior.
+#
+# $(CLEAN_TARGETS)		: What targets should be cleaned (must be
+#				  real files). This will automatically append
+#				  adds the .o suffix to all files referenced
+#				  by $(MAKE_TARGETS)) to CLEAN_TARGETS, if
+#				  MAKE_TARGETS wasn't defined (see
+#				  $(MAKE_TARGETS)).
+# $(PREINSTALL_DEPS)		: What to run as direct dependencies of
+# 				  pre-install.
+# $(INSTALL_DEPS)		: What to run as direct dependencies of
+# 				  the _install target. These must be real
+# 				  files.
+# $(POSTINSTALL_DEPS)		: What to install direct dependencies of
+# 				  the install target.
+# $(INSTALL_MODE)		: What mode should we using when calling
+# 				  install(1)?
+#
+# If you choose to cherrypick the logic contained here, by changing around the
+# dependencies for $(INSTALL_DEPS) and $(POSTINSTALL_DEPS), then you must also
+# emulate the $(INSTALL_DEPS): pre-install and install: $(POSTINSTALL_DEPS)
+# dependencies, if you _use_ them.
+#
+# Also, if you wish to change the installation directory, you must do something
+# like:
+#
+# INSTALL_DIR			:= /path/to/installdir/from/$(DESTDIR)/$(prefix)
+#
+# e.g. if I wanted to install my binaries in testcases/bin, I would do:
+#
+# INSTALL_DIR			:= testcases/bin
+#
+# in my calling Makefile.
+#
+define generic_leaf_target
+
+$$(eval $$(generic_target_env_setup))
+
+.PHONY: all clean _install install pre-install
+
+all: $$(MAKE_TARGETS)
+
+clean: $$(CLEAN_DEPS)
+	-$(RM) -f $$(CLEAN_TARGETS)
+
+pre-install: | $$(DESTDIR)/$$(prefix)/$$(INSTALL_DIR) $$(PREINSTALL_DEPS)
+
+$$(INSTALL_FILES): %: pre-install $$(INSTALL_DEPS)
+	install -m $$(INSTALL_MODE) "$$(notdir $$@)" "$$@"
+
+install: | $$(INSTALL_FILES) $$(POSTINSTALL_DEPS)
+
+endef
+
+#
+# generic_trunk_target
+#
+# Generate a set of recursive targets to apply over a trunk directory (has
+# directories) -- optionally with a set of trunk-based files.
+#
+# All variables in this canned define are essentially the same as
+# generic_leaf_target, with the exception that the install flow for local
+# targets is:
+#
+# pre-install -> $(INSTALL_FILES) -> trunk-install
+#
+# All recursive targets are traverse SUBDIRS as defined by the user, or if
+# undefined, defaults to any subdirectories where Makefile's are contained
+# within.
+#
+# generic_trunk_target specific variables are:
+#
+# RECURSIVE_TARGETS		: a list of targets to apply over an entire
+# 				  directory tree. This defaults to
+# 				  `all clean install'.
+#
+# See generic_leaf_target, generic_target_env_setup, and get_make_dirs for
+# more details and design notes.
+#
+define generic_trunk_target
+
+#
+# Doesn't need forced secondary expansion because $(CURDIR) isn't going to
+# change (or at least it bloody well shouldn't ;)...).
+#
+# Don't do this in generic_target_env_setup, because we only need to do this
+# by default for generic_dir_target.
+#
+$(eval $(get_make_dirs))
+
+RECURSIVE_TARGETS		?= all clean install
+
+.PHONY: $$(RECURSIVE_TARGETS) $$(addprefix trunk-,$$(RECURSIVE_TARGETS)) pre-install
+
+$$(eval $$(generic_target_env_setup))
+
+trunk-all: $$(MAKE_TARGETS)
+
+trunk-clean: $$(CLEAN_DEPS)
+	-$(RM) -f $$(CLEAN_TARGETS)
+
+pre-install: | $$(DESTDIR)/$$(prefix)/$$(INSTALL_DIR) $$(PREINSTALL_DEPS)
+
+$$(INSTALL_FILES): %: pre-install $$(INSTALL_DEPS)
+	install -m $$(INSTALL_MODE) "$$(notdir $$@)" "$$@"
+
+trunk-install: | $$(INSTALL_FILES) $$(POSTINSTALL_DEPS)
+
+# Avoid creating duplicate .PHONY references to all, clean, and install. IIRC,
+# I've seen some indeterministic behavior when one does this in the past with
+# GNU Make...
+.PHONY: $$(filter-out $$(RECURSIVE_TARGETS),all clean install)
+all: trunk-all
+
+clean: trunk-clean
+
+install: trunk-install
+
+$$(RECURSIVE_TARGETS): %:
+	@set -e; for dir in $$(SUBDIRS); do \
+	    $(MAKE) -C $$$$dir $$@; \
+	done
+
+endef

[-- Attachment #3: Type: text/plain, Size: 79 bytes --]

------------------------------------------------------------------------------

[-- Attachment #4: Type: text/plain, Size: 155 bytes --]

_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

Re: [LTP] [PATCH 2/3] Make system enhancements, Draft 1

[Mike Frysinger]

[-- Attachment #1.1: Type: text/plain, Size: 1688 bytes --]

On Monday 06 July 2009 19:02:50 Garrett Cooper wrote:
> 1. Write up a document on how to use the new Make system
> (README.mk-devel), so others may assist in the work that we're
> spearheading at Cisco and contributing back to LTP, and we can begin
> dropping the adhoc Makefiles.
> 2. Add master_rules.mk which contains canned rules for environment
> setup, leaf directories, and trunk directories to reduce Make logic
> noise in the existing LTP Makefile's. This is a more condensed and
> straightforward version of the original master_rules.mk file
> contributed and never integrated into LTP in the past.
> 3. Add master_include.mk, a file which stands as the defacto include
> Makefile for all . This was created out of the comment provided by
> Mike Frysinger w.r.t. a master include file.
>
> Note: This patch has been largely tested, but some of the additional
> functionality and rework in generic_trunk_target needs to be tested
> more prior to commit; hence it's a Draft 1 patch.

"srcdir" should refer to the current directory's source tree.  "top_srcdir" 
should refer to the top level source tree.  building in-tree means srcdir will 
be ".".  this is how autotools works and allows for easy out-of-tree 
compilation.  same goes for "builddir" and "top_builddir", not this "objxxx" 
convention.

for the toolchain, do you purposefully only document CC and CFLAGS ?

i'm not familiar with this "MAKEOPTS=';'" thing you refer to.  what's that all 
about ?

you list the copyright info twice

master_rules.mk shouldnt be a '-include' ... we want an error if that doesnt 
exist

your %.a rule is missing a call to ranlib on the archive
-mike

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 389 bytes --]

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time, 
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge

[-- Attachment #3: Type: text/plain, Size: 155 bytes --]

_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

Re: [LTP] [PATCH 2/3] Make system enhancements, Draft 1

[Garrett Cooper]

On Wed, Jul 8, 2009 at 4:24 PM, Mike Frysinger<vapier@gentoo.org> wrote:
> On Monday 06 July 2009 19:02:50 Garrett Cooper wrote:
>> 1. Write up a document on how to use the new Make system
>> (README.mk-devel), so others may assist in the work that we're
>> spearheading at Cisco and contributing back to LTP, and we can begin
>> dropping the adhoc Makefiles.
>> 2. Add master_rules.mk which contains canned rules for environment
>> setup, leaf directories, and trunk directories to reduce Make logic
>> noise in the existing LTP Makefile's. This is a more condensed and
>> straightforward version of the original master_rules.mk file
>> contributed and never integrated into LTP in the past.
>> 3. Add master_include.mk, a file which stands as the defacto include
>> Makefile for all . This was created out of the comment provided by
>> Mike Frysinger w.r.t. a master include file.
>>
>> Note: This patch has been largely tested, but some of the additional
>> functionality and rework in generic_trunk_target needs to be tested
>> more prior to commit; hence it's a Draft 1 patch.
>
> "srcdir" should refer to the current directory's source tree.  "top_srcdir"
> should refer to the top level source tree.  building in-tree means srcdir will
> be ".".  this is how autotools works and allows for easy out-of-tree
> compilation.  same goes for "builddir" and "top_builddir", not this "objxxx"
> convention.

Ah, ok. Will do -- thanks!

> for the toolchain, do you purposefully only document CC and CFLAGS ?

Where did I do that?

> i'm not familiar with this "MAKEOPTS=';'" thing you refer to.  what's that all
> about ?

       -r, --no-builtin-rules
            Eliminate use of the built-in implicit rules.  Also clear
out the default list of suffixes for suffix rules.

There isn't a way to disable -r in make-3.81 except by removing it
from MAKEOPTS (that's how it was enabled in our make system at Cisco
in my group). `MAKEOPTS=;' is the quick way out. Nasty PITA...

> you list the copyright info twice

Please see my other comment.

> master_rules.mk shouldnt be a '-include' ... we want an error if that doesnt
> exist

I only did that to ensure that this commit could go in, irrespective
of PATCH 3/4, but I agree, it should be enabled once both changes are
committed.

> your %.a rule is missing a call to ranlib on the archive

Ok. How do I do that call exactly?

ar [blah]
ranlib [blah]

maybe?

Thanks!
-Garrett

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time, 
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

Re: [LTP] [PATCH 2/3] Make system enhancements, Draft 1

[Mike Frysinger]

[-- Attachment #1.1: Type: text/plain, Size: 1438 bytes --]

On Wednesday 08 July 2009 20:26:37 Garrett Cooper wrote:
> On Wed, Jul 8, 2009 at 4:24 PM, Mike Frysinger<vapier@gentoo.org> wrote:
> > for the toolchain, do you purposefully only document CC and CFLAGS ?
>
> Where did I do that?

README.mk-devel

> > i'm not familiar with this "MAKEOPTS=';'" thing you refer to.  what's
> > that all about ?
>
>        -r, --no-builtin-rules
>             Eliminate use of the built-in implicit rules.  Also clear
> out the default list of suffixes for suffix rules.
>
> There isn't a way to disable -r in make-3.81 except by removing it
> from MAKEOPTS (that's how it was enabled in our make system at Cisco
> in my group). `MAKEOPTS=;' is the quick way out. Nasty PITA...

doesnt that clobber -j and -l and similar ?

rather than help the user, spank them for it.  in the .mk, you can add a 
findstring on the MAKEOPTS for "r" and $(error) out if found.

> > master_rules.mk shouldnt be a '-include' ... we want an error if that
> > doesnt exist
>
> I only did that to ensure that this commit could go in, irrespective
> of PATCH 3/4, but I agree, it should be enabled once both changes are
> committed.

dont worry about it ... assume they're going in as a set

> > your %.a rule is missing a call to ranlib on the archive
>
> Ok. How do I do that call exactly?
>
> ar [blah]
> ranlib [blah]
>
> maybe?

ranlib only needs one argument -- the archive
-mike

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 389 bytes --]

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time, 
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge

[-- Attachment #3: Type: text/plain, Size: 155 bytes --]

_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list