I think a patch introducing a property to the cpp module that conditionally disables all rules would be acceptable.
________________________________________ From: Qbs <[email protected]> on behalf of Richard Weickelt <[email protected]> Sent: Thursday, November 27, 2025 10:21 AM To: [email protected] Subject: Re: [Qbs] Cpp application with external build command but working code model On 11/27/25 09:32, Christian Kandeler via Qbs wrote: > Why can't you use a different product type? Because I also want to debug the executable in QtCreator and that requires the product to be of type application. I am working around the problem by doing what you suggest and adding a second non-cpp product of type application which copies the .elf files from the ESP build folder into Qbs' build folder. It also seems like "application" must be the output of a rule and cannot be attached to source artifacts via Group. Another use-case would be post processing of ELF files produced by the linker. In that case we don't want to use the linker output directly, but still need the product type to be application. The limitation of the 2-product work-around is that one cannot easily re-use it as a single item "Esp32Application". _______________________________________________ Qbs mailing list [email protected] https://lists.qt-project.org/listinfo/qbs _______________________________________________ Qbs mailing list [email protected] https://lists.qt-project.org/listinfo/qbs
