[nanomsg] Re: NNG & modern CMake

  • From: "Böszörményi Zoltán" <dmarc-noreply@xxxxxxxxxxxxx> (Redacted sender "zboszor" for DMARC)
  • To: nanomsg@xxxxxxxxxxxxx, Garrett D'Amore <garrett@xxxxxxxxxx>
  • Date: Fri, 3 Jan 2020 10:28:17 +0100

2020. 01. 03. 2:11 keltezéssel, Garrett D'Amore írta:

https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-devtools/cmake

I see CMake 3.16 in there.  That’s about as new as it gets. 😊

Only on the master branch.

Here's the list for the last few stable releases:

Yocto 2.5 (Sumo): 3.10.3
Yocto 2.6 (Thud): 3.12.2
Yocto 2.7 (Warrior): 3.14.1
Yocto 3.0 (Zeus): 3.15.3


I’m not sure if that answers the question, but I hope so.

  * Garrett

Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10

*From: *Cody Piersall <mailto:cody.piersall@xxxxxxxxx>
*Sent: *Thursday, January 2, 2020 3:03 PM
*To: *nanomsg@xxxxxxxxxxxxx <mailto:nanomsg@xxxxxxxxxxxxx>
*Subject: *[nanomsg] Re: NNG & modern CMake

The only place where the requirement *might* be onerous for me

personally would be when I'm building distributions for SoC boards

with the Yocto project.  I'm not sure what version of CMake is used

for each different Yocto release, and a quick Google search didn't

reveal anything.

For those unfamiliar with the Yocto project, it is a toolchain for

building entire custom Linux distributions, including the bootloader,

Linux kernel, and all of userspace. Each Yocto release pins versions

of all the build software it uses to get (closer to) deterministic

builds, including the host gcc, host libc, etc.  So each Yocto release

will have a specific version of CMake that it uses to cross-compile

everything.

Does anyone else know which version of CMake the various Yocto

releases use, or how to find out?  And how easy it is to use a

different host version?  Changing the CMake version would potentially

have unexpected side effects elsewhere.

Cody

On Wed, Jan 1, 2020 at 7:22 PM Garrett D'Amore <garrett@xxxxxxxxxx> wrote:

 >

 > All,

 >

 >

 >

> This is a heads up (and a request for objections if any) that at some point soon a future release of NNG (possibly starting with v1.3) will require significantly newer CMake versions.  I’m contemplating requiring at least 3.13, and probably more like 3.14 or even 3.15.

 >

 >

 >

> There are a number of features that more recent CMake brings to the table, which potentially reduce the effort required to have easily supportable, flexible configuration.  At present we are working around limitations in older releases, but it’s becoming somewhat annoying to have to keep doing so.  Note that CMake binaries are packaged and freely and readily available for Ubuntu 16.x and newer, RedHat 7.x and newer, Windows, and macOS.  Recent Visual Studio 2019 even *includes* cmake 3.15.

 >

 >

 >

> This might make things slightly more annoying for folks using CMake on non-mainstream platforms, but even on those platforms bootstrapping CMake is generally a very simple task.  (Note also that modern CMake can cross compile easily, so even if your target environment is not mainstream, you won’t be impacted as long as your *development* system isn’t too far off the beaten path.)

 >

 >

 >

 > If this is going to cause anyone undue stress, please let me know.

 >

 >

 >

 > Garrett

Sent to you because via the nanomsg@xxxxxxxxxxxxx mailing list.

The nanomsg home page is www.nanomsg.org.

To unsubscribe, use the web interface at www.freelists.org.


Sent to you because via the nanomsg@xxxxxxxxxxxxx mailing list.
The nanomsg home page is www.nanomsg.org.
To unsubscribe, use the web interface at www.freelists.org.

Other related posts: