[Buildroot] Binary ATI driver package in buildroot

[Thomas Petazzoni <thomas.petazzoni@free-electrons.com>]

Hello Allan,

(It would be better to keep the Buildroot list CC'ed)

On Wed, 6 Apr 2011 16:34:42 +0200
Allan Nielsen <a@awn.dk> wrote:

> > However, your package does not use the GENTARGETS infrastructure,
> > which it should do. We don't include packages that don't rely on
> > one of the GENTARGETS, AUTOTARGETS or CMAKETARGETS infrastructure.
> 
> I'am converting it to GENTARGETS right now, but I'am having some
> problem with the extracting step, here is what I tried:
> 
> define FGLRX_EXTRACT_CMDS
>         mkdir -p $(@D)
>         sh $(DL_DIR)/$(FGLRX_SOURCE) --extract $(@D)
> endef
> 
> But for some reason this does not seems to have any effect, hare are a
> snippet from the output:
> 
> echo ">>> fglrx 11-2 "Extracting""
> mkdir -p /home/awn/git/buildroot/output/build/fglrx-11-2
> /home/awn/src/ati-driver-installer-11-2-x86.x86_64.run | tar
> --strip-components=1 -C
> /home/awn/git/buildroot/output/build/fglrx-11-2  -xf -
> chmod -R ug+rw /home/awn/git/buildroot/output/build/fglrx-11-2
> touch /home/awn/git/buildroot/output/build/fglrx-11-2/.stamp_extracted
> 
> Is this not the correct way to use GENTARGETS?

Unfortunately for the moment, it is not possible to override the
extraction step of a package by defining the <pkg>_EXTRACT_CMDS
variable. Buildroot asumes that each package is a tarball that can be
extracted as usual.

There are however several packages (usually non-open source stuff) with
strange extraction needs, so it would be great to be able to override
this step.

As a hack, you can do something like:

$(BUILD_DIR)/dhrystone-$(DHRYSTONE_VERSION)/.stamp_extracted:
        @$(call MESSAGE,"Extracting")
        $(Q)mkdir -p $(@D)
        $(Q)cd $(@D) && $(SHELL) $(DL_DIR)/$($(PKG)_SOURCE)
        $(Q)cp $($(PKG)_DIR_PREFIX)/dhrystone/Makefile $(@D)/
        $(Q)touch $@

(see package/dhrystone/dhryistone.mk)

Or if you want to do it the clean way, add the possibility of
overriding the extraction step in the package infrastructure.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com