From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] swig: add symlink to /usr/bin/swig2.0
Date: Mon, 22 Sep 2014 10:00:24 +0200 [thread overview]
Message-ID: <20140922100024.5fed686e@free-electrons.com> (raw)
In-Reply-To: <1125534742.25538251.1411371509741.JavaMail.root@openwide.fr>
Hello,
On Mon, 22 Sep 2014 09:38:29 +0200 (CEST), Jeremy Rosen wrote:
> The line in FindSwig.mk (part of the cmake package, not swig package)
>
> find_program(SWIG_EXECUTABLE NAMES swig2.0 swig)
>
>
> This will look in PATH for
>
> * an executable called "swig2.0"
> * if it is not found, an executable called "swig"
>
> so if there is a "swig2.0" in /usr/bin it will be used instead of the
> one called "swig" in $(HOST_DIR)/usr/bin even if the PATH order says
> otherwise.
>
> currently, host-swig only installs $(HOST_DIR)/usr/bin/swig and the
> debian package on my host only installs /usr/bin/swig2.0 thus the
> problem.
Are you sure we cannot tell CMake explicitly where our swig binary is?
Like -DSWIG_EXECUTABLE=/path/to/swig.
Cc'ing Samuel, who should be able to give some hints about this.
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 8:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-19 7:13 [Buildroot] [PATCH] cmake : bump to version 3.0.2 Jérémy Rosen
2014-09-19 7:13 ` [Buildroot] [PATCH] swig : bump to version 2.0.12 Jérémy Rosen
2014-09-21 18:06 ` Thomas Petazzoni
2014-09-19 7:13 ` [Buildroot] [PATCH] swig: add symlink to /usr/bin/swig2.0 Jérémy Rosen
2014-09-21 18:07 ` Thomas Petazzoni
2014-09-22 7:38 ` Jeremy Rosen
2014-09-22 8:00 ` Thomas Petazzoni [this message]
2014-09-19 7:27 ` [Buildroot] [PATCH] cmake : bump to version 3.0.2 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=20140922100024.5fed686e@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