[oe-commits] [openembedded-core] 03/07: libjpeg-turbo: Support building on non intel targets.

[git at git.openembedded.org]

This is an automated email from the git hooks/post-receive script.

rpurdie pushed a commit to branch master-next
in repository openembedded-core.

commit 4c1571eb30af1d04035e28e53f743d5bede8d4cd
Author: Tristan Van Berkom <tristan.vanberkom at codethink.co.uk>
AuthorDate: Fri Mar 24 15:37:36 2017 +0000

    libjpeg-turbo: Support building on non intel targets.
    
    nasm is intel specific, however libjpeg-turbo is still desirable
    on other architectures.
    
    Without this patch, it would seem that nasm is built on an intel
    host and then ignored when compiling libjpeg-turbo for an arm target,
    however it has libjpeg-turbo requiring nasm be built when building
    on an arm/aarch64 host.
    
    This fixes the issue so that nasm-native is not required on the host
    when building for an aarch64 target.
    
    Signed-off-by: Tristan Van Berkom <tristan.vanberkom at codethink.co.uk>
    Signed-off-by: Ross Burton <ross.burton at intel.com>
    Signed-off-by: Richard Purdie <richard.purdie at linuxfoundation.org>
---
 meta/recipes-graphics/jpeg/libjpeg-turbo_1.5.1.bb | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-graphics/jpeg/libjpeg-turbo_1.5.1.bb b/meta/recipes-graphics/jpeg/libjpeg-turbo_1.5.1.bb
index 70d38f4..a650d6a 100644
--- a/meta/recipes-graphics/jpeg/libjpeg-turbo_1.5.1.bb
+++ b/meta/recipes-graphics/jpeg/libjpeg-turbo_1.5.1.bb
@@ -7,7 +7,8 @@ LIC_FILES_CHKSUM = "file://cdjpeg.h;endline=13;md5=05bab7c7ad899d85bfba60da1a127
                     file://jpeglib.h;endline=16;md5=f67d70e547a2662c079781c72f877f72 \
                     file://djpeg.c;endline=11;md5=b90b6d2b4119f9e5807cd273f525d2af \
 "
-DEPENDS = "nasm-native"
+DEPENDS_append_x86-64 = " nasm-native"
+DEPENDS_append_x86    = " nasm-native"
 
 SRC_URI = "${SOURCEFORGE_MIRROR}/${BPN}/${BPN}-${PV}.tar.gz \
            file://fix-mips.patch"

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.