Help wanted: CMake to compile Qt .ui files about avrdude HOT 7 CLOSED

In that case you'd need to have a separate custom command for each .ui file, and a single custom target to aggregate all of those, something like:

SET(SOURCES file1.ui file2.ui file3.ui)
set(UI_GENERATION_COMMANDS)
foreach(SOURCE SOURCES)
    set(OUTPUT_FILE "${CMAKE_CURRENT_BINARY_DIR}/${SOURCE}.py")
    add_custom_command(
        OUTPUT "${OUTPUT_FILE}"
        COMMAND "uic -g python -o ${OUTPUT_FILE} ${SOURCE}"
        COMMENT "Generating ${SOURCE} -> ${OUTPUT_FILE}"
    )
    list(APPEND UI_GENERATION_COMMANDS "${OUTPUT_FILE}")
endforeach()
add_custom_target(GenerateUIToPy ALL DEPENDS ${UI_GENERATION_COMMANDS})

from avrdude.

OK, thanks a lot for the explanation.
Alas, I just noticed that there appears to be a lot of confusion about the uic command for PySide. In the past, the command was called pyside2-uic. Older versions of uic only supported Java and C++ as generator targets, yet the silently accepted -g python – and generated C++ code. :-o Then, the Qt5 in Ubuntu22.04 has dropped pyside2-uic entirely (probably because it was based on Python 2.7 still), but did not upgrade their Qt to a recent enough version that would support Python code generation.
So bottom line, this would probably prevent many people from experimenting with it, and I decided to rather load the .ui files at run-time instead.
But it's nevertheless good to know the solution! The issue tracker will record it for eternity. ;-)

from avrdude.

@Youw

Just wondering if you can provide a quick tip here. Thanks.

from avrdude.

Either set CMAKE_AUTOUIC to TRUE before creating a target (a library or executable) or set the AUTOUIC property of the target to TRUE.
Then add your .ui files to your target as if it is a regular cpp source.

Sample:

set(CMAKE_AUTOUIC ON)
add_library(testLib
    mainwindow.cpp
    mainwindow.h
    mainwindow.ui
)

or

add_library(testLib
    mainwindow.cpp
    mainwindow.h
    mainwindow.ui
)
set_target_properties(testLib
    PROPERTIES AUTOUIC ON
)

from avrdude.

there're other ways to achieve the same, but the one above is the most convenient

and the one you've tried to use (manyally invoking the uic) is probably the least convenient/recommended

from avrdude.

I tried CMAKE_AUTOUIC, to no avail.
Problem here: it's not C++, it's Python. I do not need to compile anything but only the .ui files. As far as I could see, CMAKE_AUTOUIC only seems to parse C++ implementation files – which I don't have.
I don't even know how I would setup a CMake target for something that isn't going to be a classic compilation result. (A couple of steps later, it might become one: when trying to create a portable bundle out of all the Python files.)
It's not that I'd object to using C++, but the purpose of all this is to demonstrate a Python wrapper around our backend library.

from avrdude.

Besides, your example is also valuable in case we'd have a need for running any similar custom command in future.

from avrdude.