Using CMake (was "fake Qt installation")

jsulm

@mzimmers It tells you that xtensa-esp32-elf-gcc.exe compiler can't compile a simple program. Is this the compiler you want to use?

mzimmers

@jsulm yes it is; that's in the toolchain for the ESP-IDF.

jsulm

@mzimmers Actually it is not compiler failing, but linker: xtensa-esp32-elf/bin/ld.exe: unrecognized option '--major-image-version'

mzimmers

@jsulm I see. So, whereabouts should I look for that option? I don't see it in any of my Creator options.

jsulm

@mzimmers I don't know.
What is actually the compiler version?

mzimmers

@jsulm presumably 8.2.0:

mzimmers

I found this which seems to do a pretty good job of describing how to translate a qmake file into a CMake file. But what it doesn't say is how to "tell" Creator that a particular project to use CMake instead of qmake. How do I do that?

Thanks...

sierdzio

You need to close your (qmake) project and then open your new CMakeLists.txt in Qt Creator.

mzimmers

Thanks, sierdzio. I also resolved the problem with that TARGET_VERSION_MAJOR -- it turns out that it's just a symbol that the ESP32 toolchain expects to have. I just defined them in my CMakeLists.txt file:

SET(TARGET_VERSION_MAJOR 0)
SET(TARGET_VERSION_MINOR 0)

And that eliminated that error.

So now, how do I inform CMake that my sources are in a directory main under the root-level directory?

sierdzio

https://doc.qt.io/qt-5/cmake-get-started.html

You specify the sources in add_executable call (if you are building an executable).

mzimmers

@sierdzio thank you for the link. I understand that there needs to be an entry for every source file somewhere. The CMakeLists.txt file in the main directory has that already. So, what is the correct entry in the CMakeLists.txt file for the top-level (above main/) to tell the build to look in main for these sources? Surely I don't need a SET_SOURCES to re-list those files? So, what's the second argument to add_executable()?

Thank you.

sierdzio

@mzimmers said in Using CMake (was "fake Qt installation"):

@sierdzio thank you for the link. I understand that there needs to be an entry for every source file somewhere. The CMakeLists.txt file in the main directory has that already. So, what is the correct entry in the CMakeLists.txt file for the top-level (above main/) to tell the build to look in main for these sources?

include or add_subdirectory, depending on your needs.

Surely I don't need a SET_SOURCES to re-list those files? So, what's the second argument to add_executable()?

First argument is the executable name. All subsequent arguments are files which cmake should consider during build.

kuzulis

Try QBS instead of CMake and do not suffer (if no any special requirements). In this case you don't need in this hard manipulations (with CMake you need in a custom toolchain file, in a separate Make or Ninja utilities and so on)...

PS: F.e. I use QBS with ESP8266 && non-os-sdk and all fine. :)

jsulm

@kuzulis Isn't QBS dying and CMake will be default in Qt6?

kuzulis

QBS is still not dead, it is now being actively developed by the open source community and has a many changes.

For QBS, it’s not a problem that CMake is the default Qt build system, it still supports in QtCreator. QBS is not only for Qt, but for everything else, especially for a bare metal programming (especially it is a best choose for a DIY projects, because it support a lot of architectures and toolchains).

jsulm

@kuzulis OK, didn't know QBS is actively developed

kuzulis

@jsulm ,

Surprize:

:))

mzimmers

@kuzulis thank you for the suggestion. The application I've written makes full use of the ESP IDF, which I believe is exclusively CMake. I don't think converting the entire build system to QBS is the right way to go. I'll continue to plod ahead with the CMake effort, since it appears to be the wave of the future. I do appreciate the suggestion, though.