From: Martin Jansa <martin.jansa@gmail.com>
To: Matt Fleming <matt@console-pimps.org>
Cc: Raymond Danks <ray.danks@se-eng.com>,
Mihai Prica <mihai.prica@intel.com>,
Matt Fleming <matt.fleming@intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] recipes-extended: Add iasl recipe
Date: Wed, 13 Aug 2014 15:45:11 +0200 [thread overview]
Message-ID: <20140813134511.GV14848@jama> (raw)
In-Reply-To: <1407935023-9284-2-git-send-email-matt@console-pimps.org>
[-- Attachment #1: Type: text/plain, Size: 2256 bytes --]
On Wed, Aug 13, 2014 at 02:03:42PM +0100, Matt Fleming wrote:
> From: Matt Fleming <matt.fleming@intel.com>
>
> Import the Intel ACPI toolchain from the meta-virtualization layer.
>
> Cc: Mihai Prica <mihai.prica@intel.com>
> Cc: Raymond Danks <ray.danks@se-eng.com>
> Signed-off-by: Matt Fleming <matt.fleming@intel.com>
> ---
> meta/recipes-extended/iasl/iasl_20120215.bb | 27 +++++++++++++++++++++++++++
> 1 file changed, 27 insertions(+)
> create mode 100644 meta/recipes-extended/iasl/iasl_20120215.bb
>
> diff --git a/meta/recipes-extended/iasl/iasl_20120215.bb b/meta/recipes-extended/iasl/iasl_20120215.bb
> new file mode 100644
> index 0000000..a14d2ec
> --- /dev/null
> +++ b/meta/recipes-extended/iasl/iasl_20120215.bb
> @@ -0,0 +1,27 @@
> +DESCRIPTION = "This is a cross development C compiler, assembler and linker environment for the production of 8086 executables (Optionally MSDOS COM)"
> +HOMEPAGE = "http://www.acpica.org/"
> +LICENSE = "Intel-ACPI"
> +LIC_FILES_CHKSUM = "file://asldefine.h;endline=115;md5=d4d7cf809b8b5e03131327b3f718e8f0"
> +SECTION = "console/tools"
> +PR = "r1"
Drop PR
> +
> +DEPENDS = "flex-native bison-native"
> +
> +SRC_URI = "https://acpica.org/sites/acpica/files/acpica-unix-${PV}.tar.gz"
There is acpica-unix2 in meta-oe:
meta-oe/recipes-extended/acpica/acpica_20140424.bb:SRC_URI = "https://acpica.org/sites/acpica/files/acpica-unix2-${PV}.tar.gz \
can we use that one instead?
> +
> +SRC_URI[md5sum] = "324c89e5bb9002e2711e0494290ceacc"
> +SRC_URI[sha256sum] = "b2b497415f29ddbefe7be8b9429b62c1f1f6e1ec11456928e4e7da86578e5b8d"
> +
> +S = "${WORKDIR}/acpica-unix-${PV}/source/compiler"
> +
> +NATIVE_INSTALL_WORKS = "1"
this variable isn't used by oe-core
> +BBCLASSEXTEND = "native"
> +
> +do_compile() {
> + CFLAGS="-Wno-error=redundant-decls" $MAKE
> +}
> +
> +do_install() {
> + mkdir -p ${D}${prefix}/bin
> + cp ${S}/iasl ${D}${prefix}/bin
> +}
> --
> 1.9.3
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2014-08-13 13:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 13:03 [PATCH 0/2] OVMF recipe Matt Fleming
2014-08-13 13:03 ` [PATCH 1/2] recipes-extended: Add iasl recipe Matt Fleming
2014-08-13 13:17 ` Richard Purdie
2014-08-13 13:24 ` Matt Fleming
2014-08-13 13:45 ` Martin Jansa [this message]
2014-08-13 19:41 ` Matt Fleming
2014-08-13 13:03 ` [PATCH v2 2/2] recipes-devtools: Add OVMF recipe Matt Fleming
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=20140813134511.GV14848@jama \
--to=martin.jansa@gmail.com \
--cc=matt.fleming@intel.com \
--cc=matt@console-pimps.org \
--cc=mihai.prica@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ray.danks@se-eng.com \
/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