On Wednesday, April 20, 2011 05:18:41 am Mike McQuaid wrote:
On 7 April 2011 18:17, Clinton Stimpson clin...@elemtech.com wrote:
I think you should *always* write out a qt.conf file.
The Qt libraries have hardcoded paths (used if there is no qt.conf file)
and if the target machine has a Qt
On 7 April 2011 16:41, Clinton Stimpson clin...@elemtech.com wrote:
I would put it in Qt4Macros.cmake and document it in FindQt4.cmake.
Cool, ok.
I would love some other people's input in this work.
I have put some work into it already and can give you the patches I have so
far.
When I
On 7 April 2011 17:17, Clinton Stimpson clin...@elemtech.com wrote:
That could be a good way to go first. If the need arises, we could introduce
more public functions for customization.
I guess we could do what fixup_bundle and get_prerequisites do in that
we have a very general function that
On 7 April 2011 18:23, David Cole david.c...@kitware.com wrote:
Absolutely: any general solution should configure a script into the build
tree, and use install(SCRIPT instead to avoid the escaping madness.
Is it acceptable to have a macro/function call INSTALL(CODE) though,
if it's literally a
On Thursday, April 07, 2011 10:03:45 am Mike McQuaid wrote:
On 7 April 2011 16:41, Clinton Stimpson clin...@elemtech.com wrote:
I would put it in Qt4Macros.cmake and document it in FindQt4.cmake.
Cool, ok.
I would love some other people's input in this work.
I have put some work into
On Thu, Apr 7, 2011 at 1:17 PM, Clinton Stimpson clin...@elemtech.comwrote:
On Thursday, April 07, 2011 10:29:41 am Mike McQuaid wrote:
On 7 April 2011 17:17, Clinton Stimpson clin...@elemtech.com wrote:
That could be a good way to go first. If the need arises, we could
introduce more
On Thu, Apr 7, 2011 at 1:23 PM, David Cole david.c...@kitware.com wrote:
On Thu, Apr 7, 2011 at 1:17 PM, Clinton Stimpson clin...@elemtech.comwrote:
On Thursday, April 07, 2011 10:29:41 am Mike McQuaid wrote:
On 7 April 2011 17:17, Clinton Stimpson clin...@elemtech.com wrote:
That could
