From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Yegor Yefremov <yegorslists@googlemail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/open62541: bump to version 1.5.10
Date: Sun, 1 Nov 2026 23:32:57 +0100 [thread overview]
Message-ID: <aue91nxT0wYa99RD@windsurf> (raw)
In-Reply-To: <20261030102647.927989-1-yegorslists@googlemail.com>
On Fri, Oct 30, 2026 at 11:26:47AM +0100, Yegor Yefremov via buildroot wrote:
> Release notes:
> https://github.com/open62541/open62541/releases/tag/v1.4.0
> https://github.com/open62541/open62541/releases/tag/v1.5.0
> https://github.com/open62541/open62541/releases/tag/v1.5.10
>
> The UA_ENABLE_PUBSUB_DELTAFRAMES, UA_ENABLE_PUBSUB_INFORMATIONMODEL_METHODS
> and UA_ENABLE_PUBSUB_ETH_UADP CMake options were removed in 1.4.0: the
> information model methods are now always built with the PubSub
> information model, and Ethernet support is part of the POSIX event loop
> on Linux. Drop the corresponding Buildroot options and add legacy
> entries for them.
Actually in this case, Config.in.legacy entries are not needed, since
the features in question are now always compiled in. So anyone who had
those options enabled will continue to have those features in.
Applied to master with this change. Thanks!
Best regards,
Thomas
--
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
prev parent reply other threads:[~2026-11-01 22:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 10:26 [Buildroot] [PATCH] package/open62541: bump to version 1.5.10 Yegor Yefremov via buildroot
2026-11-01 22:32 ` Thomas Petazzoni via buildroot [this message]
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=aue91nxT0wYa99RD@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox