On Sep 21, 2012, at 10:01 PM, Michael Dickens wrote:
> So, long story to get to the reasons of the change; I hope that all
> makes sense. I will take a look at your ticket's issue & see what I can
> figure out. - MLD
Thanks, Michael, for your detailed explanations! :)
I hope you can figure out w
On Sep 21, 2012, at 1:47 PM, mk-macpo...@techno.ms wrote:
> please fill me in - since I'm not an expert of MacOSX-specific development -
> I have a question:
> What is the reason for this Framework stuff? Why did you move from lib to
> Library/Frameworks?
> This ticket shows the trouble I ran int
Hi Michael,
please fill me in - since I'm not an expert of MacOSX-specific development - I
have a question:
What is the reason for this Framework stuff? Why did you move from lib
to Library/Frameworks?
This ticket shows the trouble I ran into due to the move to frameworks:
https://tra
On Sep 19, 2012, at 10:28 PM, Ryan Schmidt
wrote:
> As for moving to a framework-always install, that seems like a good idea to
> me. If there are a few ports that have problems with it hopefully they can be
> patched.
Well, the internals would be compiled as frameworks, and when QMake is
execu
On Sep 19, 2012, at 16:48, Frank Schima wrote:
> Ideally actually would be to move the +examples and +demos variants into
> sub-ports - qt4-mac-examples and qt4-mac-demos.
I was going to suggest the same but you beat me to it!
As for moving to a framework-always install, that seems like a goo
On Sep 19, 2012, at 10:30 AM, Michael Dickens wrote:
> On Sep 19, 2012, at 12:02 PM, Craig Treleaven
> wrote:
>> Appreciate all the effort you have and continue to put into making Qt as
>> painless as possible!
>
> Thanks! And, that's the goal: as painless as possible. qt4-mac is a BIG
> com
On Sep 19, 2012, at 8:44 AM, Michael Dickens wrote:
> After some thinking about the amount of effort I've put into relocating
> Qt's frameworks from ${prefix}/lib to ${prefix}/Library/Frameworks, and
> how much more will need to be done -- e.g., for CMake, and pretty much
> any CMake-using port t
On Sep 19, 2012, at 12:02 PM, Craig Treleaven
wrote:
> Appreciate all the effort you have and continue to put into making Qt as
> painless as possible!
Thanks! And, that's the goal: as painless as possible. qt4-mac is a BIG
compile, so I try hard to avoid requiring a recompile any more often
th
At 11:44 AM -0400 9/19/12, Michael Dickens wrote:
After some thinking about the amount of effort I've put into relocating
Qt's frameworks from ${prefix}/lib to ${prefix}/Library/Frameworks, and
how much more will need to be done -- e.g., for CMake, and pretty much
any CMake-using port that tries
After some thinking about the amount of effort I've put into relocating
Qt's frameworks from ${prefix}/lib to ${prefix}/Library/Frameworks, and
how much more will need to be done -- e.g., for CMake, and pretty much
any CMake-using port that tries to find Qt4, to work reliably when
trying to find "q
10 matches
Mail list logo