Message: previous - next
Month: June 2012

Re: [trinity-devel] TQt3 Name Change - Potential Problem - what about apps that Need moc?

From: Darrell Anderson <humanreadable@...>
Date: Wed, 20 Jun 2012 10:15:00 -0700 (PDT)
>   How will the TQt3 executable name change affect
> packages that look for Qt3 executable to build???
>   Example 'pinentry' needs qmoc to build with
> '--enable-pinentry-qt'. Will the name changes from moc or
> qxx.moc (whatever) to tqxx.moc break these supporting
> packages?
>   I never would have thought about the supporting
> packages, but I needed to rebuild pinentry and that provoked
> the thought.
>   What say the wizards? Will all supporting packages
> that rely on ..moc need to be hacked to look for ..tqmoc
> stuff? I have no idea how extensive this list is... Will it
> even matter or is this just an errant thought?

The common admin and cmake files have been updated, which get replicated to the other modules at the main server. Therefore anything looking for the old moc now looks for tqmoc, qmake for tqmake, etc.

Outside of the last day and half, I no longer am noticing related build failures. Should all just work.

Which package is pinentry built?