Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-filesystems][PATCH 1/1] aufs-util: add new recipe
Date: Sat, 18 Jan 2014 12:29:40 +0100	[thread overview]
Message-ID: <lbdoim$e43$1@ger.gmane.org> (raw)
In-Reply-To: <d81dfc5a3416ffd765d53e5ea4089b7f2018d94f.1389979930.git.paul.eggleton@linux.intel.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Paul Eggleton schreef op 17-01-14 18:36:
/recipes-utils/aufs-util/aufs-util_git.bb
b/meta-filesystems/recipes-utils/aufs-util/aufs-util_git.bb
> new file mode 100644 index 0000000..cea3636 --- /dev/null +++
> b/meta-filesystems/recipes-utils/aufs-util/aufs-util_git.bb @@ -0,0 +1,48
> @@ +SUMMARY = "Tools for managing AUFS mounts" +SECTION = "base" 
> +HOMEPAGE = "http://http://aufs.sourceforge.net/" +LICENSE = "GPLv2" 
> +LIC_FILES_CHKSUM =
> "file://COPYING;md5=892f569a555ba9c07a568a7c0c4fa63a" + +DEPENDS =
> "aufs-util-native" +DEPENDS_class-native = "" + +SRCREV =
> "f29056fe396d56fc2a06a96312feabaebbe14c59" +SRC_URI =
> "git://git.code.sf.net/p/aufs/aufs-util;protocol=git;branch=aufs3.x-rcN
> \ +           file://aufs-util-don-t-strip-executables.patch \ +
> file://include/linux/aufs_type.h \ +
> file://aufs-util-add-tool-concept-to-Makefile-for-cross-com.patch \ +" + 
> +PV = "3.x-rcN+git${SRCPV}"

This is a new low for upstream versioning :/ I've looked at the git repo for
aufs-util and it seems 3.x-rcN is identical to 3.9, could we use that for
the aufs-utils recipe to avoid using that horrid, horrid PV above?


> + +S = "${WORKDIR}/git/" + +do_configure_append () { +	if [ "${PN}" !=
> "aufs-util-native" ]; then +		for i in ver c2sh c2tmac; do +			cp
> ${STAGING_BINDIR_NATIVE}/aufs-util-${PV}/$i ./ +		done +	fi +}


Change to do_configure_append_class-target ?

> + +do_compile () { +	oe_runmake CPPFLAGS="-I${WORKDIR}/include
> -I${S}/libau" +} + +do_compile_class-native () { +	oe_runmake tools
> CPPFLAGS="-I${WORKDIR}/include -I${S}/libau" +} + +do_install () { +
> oe_runmake 'DESTDIR=${D}' install_sbin install_ubin install_etc +} + 
> +do_install_class-native () { +	install -d ${D}${bindir}/aufs-util-${PV} 
> +	for i in ver c2sh c2tmac; do +		install -m 755 $i
> ${D}${bindir}/aufs-util-${PV}/$i +	done +}

And you'll probably want a

RRECOMMENDS_${PN} = "kernel-module-aufs"

here to drag in the aufs modules.

> +BBCLASSEXTEND = "native"

regards,

Koen

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org

iD8DBQFS2mWkMkyGM64RGpERAshzAJ9nGpCEOIKCbecMf8Bv8AMAhjl9+ACfRX9U
ti6UhcFJhgfQuos3XrxSCJQ=
=6cZo
-----END PGP SIGNATURE-----



  reply	other threads:[~2014-01-18 11:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-17 17:36 [meta-filesystems][PATCH 0/1] Add aufs-util Paul Eggleton
2014-01-17 17:36 ` [meta-filesystems][PATCH 1/1] aufs-util: add new recipe Paul Eggleton
2014-01-18 11:29   ` Koen Kooi [this message]
2014-01-21 10:30     ` Paul Eggleton
2014-01-18 12:05   ` Martin Jansa
2014-01-21 10:20     ` Paul Eggleton
2014-01-22 14:31   ` Otavio Salvador
2014-01-22 14:34     ` Otavio Salvador

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='lbdoim$e43$1@ger.gmane.org' \
    --to=koen@dominion.thruhere.net \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox