[Buildroot] Pre-RFC: clean integration of unclean packages

[Arnout Vandecappelle <arnout@mind.be>]

On Monday 05 December 2011 10:58:11 Thomas De Schampheleire wrote:
> On Mon, Dec 5, 2011 at 10:46 AM, Arnout Vandecappelle <arnout@mind.be> wrote:
[snip]
> > A second problem is that TI uses a horrible self-cooked build system. It
> > makes assumptions about file locations that are difficult to satisfy. In
> > addition, some packages don't even have a Makefile. And finally, they
> > generate libraries with names like 'cmem.a470MV' instead of the usual
> > 'libcmem.a'. To overcome all this, I wrote a custom 'Makefile.ti' that is
> > used by buildroot instead of the packages' Makefiles. Does everybody agree
> > that this is a good idea, or does someone have a better suggestion?
> 
> Where is the Makefile.ti located and how does it get there? Is it
> created by patching the source tree, or is it directly present in the
> buildroot sources?

 It's in the packages/ti directory and is used by calling 
$(MAKE) -f packages/ti/Makefile.ti -C $(@D)

 I prefer that way to patching the actual source tree because of clarity.
Note that the same Makefile.ti is used for all ti packages.

> > A third problem is that some packages depend on 'xdctools'. This is a system
> > to ease integration of embedded components into Eclipse. One small part of
> > it is a header file that defines some standard types (basically stdint.h and
> > stdbool.h but with different names). The whole xdctools package is a source
> > tree of about half a gig, but for buildroot we just need this one 'std.h'
> > file out of it... So I decided to copy that file directly into buildroot.
> > Does everybody agree that this is a good idea, or does someone have a better
> > suggestion?
> 
> How is this achieved? Is there a dummy xdctools package that just
> installs one file into staging? How is the file copied, is it directly
> present in buildroot, or by patching?
> Or did you add a patch adding that file to each of the packages that
> depend on xdctools?

 packages/ti/xdctools/std.h which has the following .mk file:

XDCTOOLS_SOURCE =
XDCTOOLS_VERSION = 1

XDCTOOLS_INSTALL_STAGING = YES
XDCTOOLS_INSTALL_TARGET = NO

define XDCTOOLS_INSTALL_STAGING_CMDS
	$(INSTALL) -D -m 0644 package/ti/xdctools/std.h $(STAGING_DIR)/usr/include/xdc/std.h
endef

define XDCTOOLS_UNINSTALL_STAGING_CMDS
	$(RM) $(STAGING_DIR)/usr/include/xdc/std.h
endef

$(eval $(call GENTARGETS))

 It also doesn't have a Config.in, it can only be used as a dependency.


 Thanks,
 Regards,
 Arnout

-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  31BB CF53 8660 6F88 345D  54CC A836 5879 20D7 CF43
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20111205/ded64422/attachment-0001.html>