From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] swig: add symlink to /usr/bin/swig2.0
Date: Mon, 22 Sep 2014 14:23:39 +0200 [thread overview]
Message-ID: <20140922142339.5d50bdfa@free-electrons.com> (raw)
In-Reply-To: <1411385468-24878-2-git-send-email-jeremy.rosen@openwide.fr>
Hello,
On Mon, 22 Sep 2014 13:31:08 +0200, J?r?my Rosen wrote:
> diff --git a/package/swig/swig.mk b/package/swig/swig.mk
> index e9ef521..07f0548 100644
> --- a/package/swig/swig.mk
> +++ b/package/swig/swig.mk
> @@ -4,7 +4,8 @@
> #
> ################################################################################
>
> -SWIG_VERSION = 2.0.12
> +SWIG_MAJOR = 2.0
> +SWIG_VERSION = $(SWIG_MAJOR).12
> SWIG_SITE = http://downloads.sourceforge.net/project/swig/swig/swig-$(SWIG_VERSION)
> SWIG_DEPENDENCIES = host-bison
> HOST_SWIG_CONF_OPT = \
> @@ -14,4 +15,10 @@ HOST_SWIG_CONF_OPT = \
> SWIG_LICENSE = GPLv3+ BSD-2c BSD-3c
> SWIG_LICENSE_FILES = LICENSE LICENSE-GPL LICENSE-UNIVERSITIES
>
> +define HOST_SWIG_INSTALL_SYMLINK
> + ln -fs $(HOST_DIR)/usr/bin/swig $(HOST_DIR)/usr/bin/swig$(SWIG_MAJOR)
> +endef
> +
> +HOST_SWIG_POST_INSTALL_HOOKS += HOST_SWIG_INSTALL_SYMLINK
Samuel, can you tell us if we can explicitly tell to CMake the path to
Swig, knowing that it is detected by CMake using find_program() ?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-09-22 12:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 11:31 [Buildroot] [PATCH v2] cmake : bump to version 3.0.2 Jérémy Rosen
2014-09-22 11:31 ` [Buildroot] [PATCH v2] swig: add symlink to /usr/bin/swig2.0 Jérémy Rosen
2014-09-22 12:23 ` Thomas Petazzoni [this message]
2014-09-22 14:12 ` Samuel Martin
2014-09-22 17:29 ` Thomas Petazzoni
2014-09-22 17:08 ` [Buildroot] [PATCH v2] cmake : bump to version 3.0.2 Thomas Petazzoni
2014-09-23 6:51 ` Jeremy Rosen
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=20140922142339.5d50bdfa@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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