From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Yegor Yefremov <yegorslists@googlemail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/swig: also create a swig4.0 symlink
Date: Sat, 3 Oct 2026 20:37:19 +0200 [thread overview]
Message-ID: <asFLWqOxU5fmhumS@windsurf> (raw)
In-Reply-To: <20260924131533.2302137-1-yegorslists@googlemail.com>
On Thu, Sep 24, 2026 at 03:15:33PM +0200, Yegor Yefremov via buildroot wrote:
> FindSWIG in CMake searches for swig4.0, swig3.0 and swig2.0 before it
> tries plain swig, and it searches the whole PATH for one name before
> moving on to the next. We only create swig3.0 and swig$(SWIG_VERSION_MAJOR)
> (swig4.5) symlinks in $(HOST_DIR)/bin, so a swig4.0 installed on the
> build machine, as Ubuntu 22.04 does with its swig4.0 package, takes
> precedence over our host-swig for every CMake package that does not pass
> SWIG_EXECUTABLE explicitly. With CMake 3.22.1, libftdi1 with Python
> bindings ends up with
>
> -- Found SWIG: /usr/bin/swig4.0 (found suitable version "4.0.2", ...)
>
> Also create a swig4.0 symlink, and update the comment accordingly.
>
> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
> Assisted-by: Claude:claude-opus-5
Applied to master, thanks!
Best regards,
Thomas Petazzoni
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-10-03 18:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 13:15 [Buildroot] [PATCH] package/swig: also create a swig4.0 symlink Yegor Yefremov via buildroot
2026-10-03 18:37 ` Thomas Petazzoni via buildroot [this message]
2026-10-10 9:23 ` Thomas Perale via buildroot
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=asFLWqOxU5fmhumS@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=yegorslists@googlemail.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 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.