Re: qt4-mac : still dependent on Carbon.framework?

2014-03-17 Thread Michael Dickens
On Sun, Mar 16, 2014, at 09:36 PM, René J.V. Bertin wrote:
 On Sunday March 16 2014 18:42:53 you wrote:
  about for some project that's using QtGui via QMake, for which removing
  the linking with Carbon worked?  I've never tried the former, and the
  latter could easily work depending on the project. - MLD
 
 Yes, and we're talking about a number of the KDE apps I built manually.
 Of course, projects that use Carbon functions would need to link the
 framework, but it would appear that the other apps don't have that
 requirement. 

No great surprises there: If you project does not use Carbon, then you
don't need to link to it. If the project does use Carbon, it must be
included in linking.  That said, if you're linking a project with QtGui,
which in turn links with Carbon, then it won't hurt to also link the
project with Carbon too. None of the library description files (.la,
.prl, .pc) include Carbon in their dependency for linking with QtGui ...
so, I'm not sure where the dependency is coming from.  Anyway, hope this
helps. - MLD
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


qt4-mac : still dependent on Carbon.framework?

2014-03-16 Thread René J.V. Bertin
I see that Qt4-mac links against Carbon.framework (in QtGui.dylib) and even 
exports the dependency via qmake. But the times I tried to link without 
-framework Carbon everything worked just fine.
Is this dependency still valid, and is it really one that needs to be promoted 
from the Qt frameworks to clients using said frameworks (rather than just being 
a Qt internal dependency satisfied as long as the Qt frameworks are linked 
against Carbon)?

René
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Re: qt4-mac : still dependent on Carbon.framework?

2014-03-16 Thread Michael Dickens
Hi René - Are you saying that you removed the linking with -framework
Carbon from when QtGui is linked and that worked?  Or, are you talking
about for some project that's using QtGui via QMake, for which removing
the linking with Carbon worked?  I've never tried the former, and the
latter could easily work depending on the project. - MLD

On Sun, Mar 16, 2014, at 09:02 AM, René J.V. Bertin wrote:
 I see that Qt4-mac links against Carbon.framework (in QtGui.dylib) and
 even exports the dependency via qmake. But the times I tried to link
 without -framework Carbon everything worked just fine.
 Is this dependency still valid, and is it really one that needs to be
 promoted from the Qt frameworks to clients using said frameworks (rather
 than just being a Qt internal dependency satisfied as long as the Qt
 frameworks are linked against Carbon)?
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Re: qt4-mac : still dependent on Carbon.framework?

2014-03-16 Thread René J . V . Bertin
On Sunday March 16 2014 18:42:53 you wrote:
 Hi René - Are you saying that you removed the linking with -framework
 Carbon from when QtGui is linked and that worked?  Or, are you talking

No, unfortunately I didn't test that.

 about for some project that's using QtGui via QMake, for which removing
 the linking with Carbon worked?  I've never tried the former, and the
 latter could easily work depending on the project. - MLD

Yes, and we're talking about a number of the KDE apps I built manually. Of 
course, projects that use Carbon functions would need to link the framework, 
but it would appear that the other apps don't have that requirement. 

R.
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users