One caveat here. I found that thectags for macOS on the Arduino github releases page is not 64-bit, however, the ctags binary distributed in the Arduino app is... so I also had to:

cp /Applications/Arduino.app/Contents/Java/tools-builder/ctags/5.8-arduino11/ctags ~/.Arduino_Core_STM32_dl/d726370579d207be3e43211ba220e5b1/dist/ctags

I'm not sure if a 64-bit ctags binary is available outside of the Arduino installer, but this would be a better solution.

Fromcmake_host_system_information, redirecting toCMAKE_HOST_SYSTEM_NAME:

Name of the OS CMake is running on.

On systems that have the uname command, this variable is set to the output of uname -s. Linux,
Windows, and Darwin for macOS are the values found on the big three operating systems.

Did you really observe the value "macOS"?! (That's fine, but it would mean the docs are confusing...)

As for the caveat you outline:ctags-5.8-arduino11-x86_64-apple-darwin.zip is what you're looking for, no? Or do you mean they packaged a 32-bits app with a 64-bits name?

As an extra information: which Mac-OS version you used ?

MacOS version is Ventura13.4.1

And yes,@massonal, thex86_64 zip contains an i386 executable:

$ wget https://github.com/arduino/ctags/releases/download/5.8-arduino11/ctags-5.8-arduino11-x86_64-apple-darwin.zip$ unzip ctags-5.8-arduino11-x86_64-apple-darwinArchive:  ctags-5.8-arduino11-x86_64-apple-darwin.zip  inflating: ctags$ file ctagsctags: Mach-O executable i386

vs. The correct, 64-bit version included with the arduino app:

$ file /Applications/Arduino.app/Contents/Java/tools-builder/ctags/5.8-arduino11/ctags/Applications/Arduino.app/Contents/Java/tools-builder/ctags/5.8-arduino11/ctags: Mach-O 64-bit executable x86_64

@nathantsoi you don't answer this question from@massonal

Did you really observe the value "macOS"?! (That's fine, but it would mean the docs are confusing...)

On our side a MacBook Pro with Monterey v12.6.1 is used to validate and result ofuname -s isDarwin.
It seems strange the result was changed and CMAKE documentation was not updated.
Looking on Ventura, it is always based on Darwin kernel. Ventura version 13.4.1 is based on 22.5.0 Darwin kernel.

Correct, I get the stringmacOS:

(Snippet fromFindArduinoCtags.cmake)

cmake_host_system_information(  RESULT HOSTINFO  QUERY OS_NAME OS_PLATFORM)list(GET HOSTINFO 0 HOST_OS)list(GET HOSTINFO 1 HOST_ARCH)message(HOST_OS=${HOST_OS})

Results in:

HOST_OS=macOS

Thanks for the confirmation@nathantsoi.
Then, it seems like it's a bug on CMake side (they probably forgot to update the doc at some point? 🤷 )
I suggest you raise a ticket by them...https://github.com/Kitware/CMake#reporting-bugs

As for the issue you have with ctags, do you see any functional impact from the 32-bits version?
I think here we'll try to stick to official releases as much as possible...
You can nonetheless raise an issue there too to ask for clarification!https://github.com/arduino/ctags

My final take on this PR: it does not introduce anybug, so it may be merged safely.
I'll let@fpistm decide on whether to merge it or wait on upstream fixes in the tools.

Re. the macOS string, I'll open a ticket w/ cmake.

Re. ctags, I should clarify that the 32-bit version of ctags will not run on macOS 13.x.

Using thehttps://github.com/arduino/ctags binary results in this error:

/bin/sh: /Users/ntsoi/.Arduino_Core_STM32_dl/d726370579d207be3e43211ba220e5b1/dist/ctags/ctags: Bad CPU type in executable

Hence the need to copy in the 64-bit version from the Arduino.app

Perhaps this can be noted in the cmake setup documentation for now? I am happy to do this if you would like.

Actually,@massonal, I just checked

message(CMAKE_HOST_SYSTEM_NAME=${CMAKE_HOST_SYSTEM_NAME})

And this does yield the documented result:CMAKE_HOST_SYSTEM_NAME=Darwin

Note, this is different from the snippets inensure_core_deps.cmake andFindArduinoCtags.cmake (#2060 (comment))

That last item withCMAKE_HOST_SYSTEM_NAME really is confusing...cmake_host_system_information does redirect to it.

OS_NAME
New in version 3.10.

SeeCMAKE_HOST_SYSTEM_NAME

Definitely mention that in the ticket you write to CMake!

Perhaps this can be noted in the cmake setup documentation for now? I am happy to do this if you would like.

Feel free to submit a PR for that 😉