On Mon, 2011-08-01 at 19:08 +0100, Richard Hughes wrote:
On 1 August 2011 15:24, Jaroslav Reznik jrez...@redhat.com wrote:
It's not very good idea to ship pre-generated moc files, better to
autogenerate them during the build-time. PackageKit is using automake,
so it's a little bit more
On lundi 01 août 2011 20:08:12 Richard Hughes wrote:
On 1 August 2011 15:24, Jaroslav Reznik jrez...@redhat.com wrote:
It's not very good idea to ship pre-generated moc files, better to
autogenerate them during the build-time. PackageKit is using automake,
so it's a little bit more
On 2 August 2011 14:54, Laurent Rineau
laurent.rineau__fed...@normalesup.org wrote:
Yes. MOC files are generated files like .o files. The difference is that it is
generated *source* files. MOC files are with a version of Qt is not guaranted
to be usable with another one x.y.z, even if only the
In F16 and rawhide the PackageKit koji build is failing with This
file was generated using the moc from 4.7.2. It cannot be used with
the include files from this version of Qt. (The moc has changed too
much.) when it gets to building the PackageKit-qt library.
See
Hi!
- Original Message -
In F16 and rawhide the PackageKit koji build is failing with This
file was generated using the moc from 4.7.2. It cannot be used with
the include files from this version of Qt. (The moc has changed too
much.) when it gets to building the PackageKit-qt library.
On 1 August 2011 15:24, Jaroslav Reznik jrez...@redhat.com wrote:
It's not very good idea to ship pre-generated moc files, better to
autogenerate them during the build-time. PackageKit is using automake,
so it's a little bit more difficult but possible, check for example [1].
Right, I *think*
