All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-oe][PATCH] vim: use empty PACKAGECONFIG for vim-native
Date: Sun, 24 Feb 2019 09:56:50 +0000	[thread overview]
Message-ID: <20190224095650.32036-1-Martin.Jansa@gmail.com> (raw)

* otherwise it depends on gtk+-native and we don't need gtkgui enabled
  in native builds as vim-native was introduced only for xxd-native in:

  commit 1dff2351aa6cdafa5a501e8956cb853ab17ed9ae
  Author: Martin Jansa <Martin.Jansa@gmail.com>
  Date:   Fri Mar 10 11:55:44 2017 +0100

    vim: add native BBCLASSEXTEND

    * some recipes might use xxd
    * with stricter host binaries available in PATH:
      http://lists.openembedded.org/pipermail/openembedded-core/2017-March/133886.html
      we cannot use xxd from host and it's not so common to add it into
      HOSTTOOL_NONFATAL
    * there is also smaller solution for xxd -i (which is what I need):
      https://github.com/gregkh/xxdi
      but after creating xxdi-native recipe for this I've discovered that
      perl on my host as well as perlnative doesn't provide File::Slurp
      used by this, so adding BBCLASSEXTEND here is easier solution

    Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>

Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
---
 meta-oe/recipes-support/vim/vim_8.1.0347.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta-oe/recipes-support/vim/vim_8.1.0347.bb b/meta-oe/recipes-support/vim/vim_8.1.0347.bb
index 0705831584..2a3d14a2ce 100644
--- a/meta-oe/recipes-support/vim/vim_8.1.0347.bb
+++ b/meta-oe/recipes-support/vim/vim_8.1.0347.bb
@@ -40,6 +40,7 @@ PACKAGECONFIG += " \
     ${@bb.utils.filter('DISTRO_FEATURES', 'acl selinux', d)} \
     ${@bb.utils.contains('DISTRO_FEATURES', 'x11', 'x11 gtkgui', '', d)} \
 "
+PACKAGECONFIG_class-native = ""
 
 PACKAGECONFIG[gtkgui] = "--enable-gui=gtk2,--enable-gui=no,gtk+,"
 PACKAGECONFIG[acl] = "--enable-acl,--disable-acl,acl,"
-- 
2.17.1



                 reply	other threads:[~2019-02-24  9:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20190224095650.32036-1-Martin.Jansa@gmail.com \
    --to=martin.jansa@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.