[cmake-developers] [CMake 0011641]: Feature request: extend QT_WRAP_UI

Mantis Bug Tracker mantis at public.kitware.com
Thu Dec 23 07:54:20 EST 2010


The following issue has been SUBMITTED. 
====================================================================== 
http://public.kitware.com/Bug/view.php?id=11641 
====================================================================== 
Reported By:                Ofri Sadowsky
Assigned To:                
====================================================================== 
Project:                    CMake
Issue ID:                   11641
Category:                   Modules
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     new
====================================================================== 
Date Submitted:             2010-12-23 07:54 EST
Last Modified:              2010-12-23 07:54 EST
====================================================================== 
Summary:                    Feature request: extend QT_WRAP_UI
Description: 
I would enjoy an extension to the QT_WRAP_UI macro in parallel with
QT4_GENERATE_MOC, where the caller can specify the path/name of the output file.

The reason is, I am trying to wrap an existing project where the files are
organized in a different way than the default QT_WRAP_UI output.  Rather than go
into the source files which #include the uic-generated headers and edit them to
use the new files, I'd rather create the uic output in the format/location
specified in the existing sources.

I could well go and create my own macros for this based on the existing
Qt4Macros; but a more standardized feature would be better.
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-12-23 07:54 Ofri Sadowsky  New Issue                                    
======================================================================




More information about the cmake-developers mailing list