FindQt4 and Mac support

[Andreas Pakulat]

On 02.12.09 11:13:41, Mike Arthur wrote:
> I'm just wondering how someone would go about replacing some of our
> modules with those provided in upstream versions of CMake. FindQt4.cmake
> for example pretty radically different from the latest CMake versions and
> fails in lots of ways on OSX 10.6. I don't think we have enough manpower
> to watch the CMake changes and backport everyone individually and it
> seems like a massive duplication of effort to me.

Alex tried to port lots of changes from 2.6.x FindQt4.cmake (and I think
also from 2.8) into our FindQt4.cmake.
 
> I'm sure I'm oversimplifying this but I'd really like to see us eliminate
> some of this duplication by merging our fixes upstream, fixing the
> modules outside of the Find*.cmake files whenever possible, removing the
> versions that our provided by the minimum version of CMake we depend on
> (assuming they work fine) and/or replacing them with the upstream CMake
> versions to provide some easier merging.
> 
> Any thoughts/suggestions on this? Can anyone suggest a step-by-step guide
> that I can use to do this?
> 
> I'm not on kde-buildsystem any more so please CC me in our your replies.

Thats easy: Create a diff, find out why the changes are needed, report an
upstream bug in cmake's bugtracker with the patch(es). Then wait until a
CMake release is available with the fixes. 

And at that point comes the problem: You need to convince everybody that we
need to depend on the new cmake version. Thats a requirement you cannot
easily change, we've only raised that requirement once since the KDE 4.0
release. Also you'd need to make sure that the changes in upstream don't
break KDE's buildsystem...

Andreas

-- 
It's all in the mind, ya know.