I want to port moc to generate directly from tqt sources. Any suggestions? Can be possible to using convert_qt_tqt3?
I want to port moc to generate directly from tqt sources. Any suggestions? Can be possible to using convert_qt_tqt3?
While it may be possible, I wouldn't advise it as moc is a core Qt tool which will change from release to release. The TQT system is supposed to sit in between the Qt public API and the Trinity codebase, not modify existing Qt libraries or binaries.
If you would like to assist with the creation of the TQT interface itself that would be of much greater help right now. ;-)
Thanks!
Tim
On Friday 10 September 2010 03:25:25 Timothy Pearson wrote:
I want to port moc to generate directly from tqt sources. Any suggestions? Can be possible to using convert_qt_tqt3?
While it may be possible, I wouldn't advise it as moc is a core Qt tool which will change from release to release. The TQT system is supposed to sit in between the Qt public API and the Trinity codebase, not modify existing Qt libraries or binaries.
I see. In this case we need a little better wrapper over moc. Right now the problem is that cmake macros must be hacked for using moc-tqt and I want to avoid this.
If you would like to assist with the creation of the TQT interface itself that would be of much greater help right now. ;-)
For sure I will, after finishing cmake scripts for kdelibs.
Thanks!
Tim
On Friday 10 September 2010 15:02:08 Serghei Amelian wrote: [...]
While it may be possible, I wouldn't advise it as moc is a core Qt tool which will change from release to release. The TQT system is supposed to sit in between the Qt public API and the Trinity codebase, not modify existing Qt libraries or binaries.
I see. In this case we need a little better wrapper over moc. Right now the problem is that cmake macros must be hacked for using moc-tqt and I want to avoid this.
For moment I using a very simple script, like this:
if [ -z "$1" ]; then echo "Usage: tmoc <input_file> [args]" else input_file="$1" shift @TQT_REPLACE_STREAM@ "${input_file}" | @QT_MOC_EXECUTABLE@ $@ fi
On Friday 10 September 2010 15:02:08 Serghei Amelian wrote: [...]
While it may be possible, I wouldn't advise it as moc is a core Qt
tool
which will change from release to release. The TQT system is supposed
to
sit in between the Qt public API and the Trinity codebase, not modify existing Qt libraries or binaries.
I see. In this case we need a little better wrapper over moc. Right now the problem is that cmake macros must be hacked for using moc-tqt and I want to avoid this.
For moment I using a very simple script, like this:
if [ -z "$1" ]; then echo "Usage: tmoc <input_file> [args]" else input_file="$1" shift @TQT_REPLACE_STREAM@ "${input_file}" | @QT_MOC_EXECUTABLE@ $@ fi
-- Serghei
If it works then use it! You can add any needed wrapper scripts, like this one, in parallel with the original Automake-based scripts. Just tack on a _cmake suffix or similar to differentiate them from the existing files. When all of Trinity has been ported to CMake the original scripts can be removed.
Thanks!
Tim
On Saturday 11 September 2010 02:04:53 Timothy Pearson wrote: [...]
For moment I using a very simple script, like this:
if [ -z "$1" ]; then echo "Usage: tmoc <input_file> [args]" else input_file="$1" shift @TQT_REPLACE_STREAM@ "${input_file}" | @QT_MOC_EXECUTABLE@ $@ fi
If it works then use it!
Works in most cases, but unfortunately broke the compilation of kdebase/kdeui. Right now i'm back to moc-tqt, I will investigate this issue later.
You can add any needed wrapper scripts, like this one, in parallel with the original Automake-based scripts. Just tack on a _cmake suffix or similar to differentiate them from the existing files.
Yes, I did.
Thanks!
Tim