Qt-interest Archive, August 2007
OS X Deployment - Frameworks
Pages: Prev | 1 | 2 | Next
Message 16 in thread
I have said this a few times before on this list, so lets try it one more time:
If Trolltech would properly support the --rpath option in the configure
script deploying on OS X would be much easier. According to the
configure --help I should be able to set a custom rpath for the
libraries, but the makefiles just ignore the option when set on OS X.
This is a major over sight and seems to indicate that the maintainer of
that part of the build system does NOT have a proper understanding of
how to build frameworks on OS X. The same problem occurs for dylibs
built on OS X.
I should NOT have to run install_name_tool at all if the build
system would properly support the rpath option.
Mike Jackson
OS X Build specialist.
On 2007-08-09 16:48:26 -0400, ygor@xxxxxxxxxxx said:
> I had similar problems.
>
> Fortuneately, I have a spare Mac on which I could do a static build
> with the qmake spec set to mac-g++
>
> I keep my source in a CVS repository, so all I need do is check out the
> source to the static machine and build it.
>
> I'd love to see the bundled framework method work.
>
> -------------- Original message ----------------------
> From: "Willy P" <willy.lists@xxxxxxxxx>
>> Thanks for your responses.
>>
>> Seb,
>> It still doesn't work. To test it I am temporarily moving my system
>> installed QtFrameworks to another folder. Is this a good way to
>> quickly simulate a machine w/o qt?
>>
>> I typed exactly what you said and the same thing happened. Then I
>> started from scratch and still nothing.
>>
>> Any other ideas,
>>
>> Thanks again...
>> -Willy
>>
>>
>> On 8/9/07, Sebastian Breuers v <sebbreuers@xxxxxx> wrote:
>>>> #install_name_tool fun
>>>>
>>>> install_name_tool -id
>>>> @executable_path/../Frameworks/QtCore.framework/Versions/4.0/QtCore
>>>> myApp.app/Contents/Frameworks/QtCore.framework/Versions/4.0/QtCore
>>>>
>>>> install_name_tool -id
>>>> @executable_path/../Frameworks/QtGui.framework/Versions/4.0/QtGui
>>>> myApp.app/Contents/Frameworks/QtCore.framework/Versions/4.0/QtGui
>>>>
>>>
>>> possibly it's working when you do this instead of the following:
>>>
>>> install_name_tool -change
>>> QtCore.framework/Versions/4.0/QtCore
>>> @executable_path/../Frameworks/QtCore.framework/Versions/4.0/QtCore
>>> myApp.app/Contents/MacOS/myApp
>>>
>>> install_name_tool -change
>>> QtGui.framework/Versions/4.0/QtGui
>>> @executable_path/../Frameworks/QtGui.framework/Versions/4.0/QtGui
>>> myApp.app/Contents/MacOS/myApp
>>>
>>> install_name_tool -change
>>> QtCore.framework/Versions/4.0/QtCore
>>> @executable_path/../Frameworks/QtCore.framework/Versions/4.0/QtCore
>>> myApp.app/Contents/Frameworks/QtGui.framework/Versions/4.0/QtGui
>>>
>>> the second line has to look like the Framework path as it is given by
>>>
>>> otool -L myApp.app/Contents/MacOS/myApp
>>>
>>> in my case it looks like e.g.
>>>
>>> QtCore.framework/Versions/4.0/QtCore
>>>
>>> and not
>>>
>>> /Library/Frameworks/QtCore.framework/Versions/4.0/QtCore
>>>
>>>
>>>> install_name_tool -change
>>>> /Library/Frameworks/QtCore.framework/Versions/4.0/QtCore
>>>> @executable_path/../Frameworks/QtCore.framework/Versions/4.0/QtCore
>>>> myApp.app/Contents/MacOS/myApp
>>>>
>>>> install_name_tool -change
>>>> /Library/Frameworks/QtGui.framework/Versions/4.0/QtGui
>>>> @executable_path/../Frameworks/QtGui.framework/Versions/4.0/QtGui
>>>> myApp.app/Contents/MacOS/myApp
>>>>
>>>> install_name_tool -change
>>>> /Library/Frameworks/QtCore.framework/Versions/4.0/QtCore
>>>> @executable_path/../Frameworks/QtCore.framework/Versions/4.0/QtCore
>>>> myApp.app/Contents/Frameworks/QtGui.framework/Versions/4.0/QtGui
>>>>
>>>
>>>
>>> best regards
>>>
>>> seb
>>>
>>> --
>>> To unsubscribe - send a mail to qt-interest-request@xxxxxxxxxxxxx with
>> "unsubscribe" in the subject or the body.
>>> List archive and information: http://lists.trolltech.com/qt-interest/
>>>
>>>
>>
>> --
>> To unsubscribe - send a mail to qt-interest-request@xxxxxxxxxxxxx with
>> "unsubscribe" in the subject or the body.
>> List archive and information: http://lists.trolltech.com/qt-interest/
--
[ signature omitted ]
Message 17 in thread
Have you submitted this as a bug to Trolltech? I would love to see this work
BEFORE I need it. :)
Keith
**Please do not reply to me, reply to the list.**
On 08-10-2007 4:11 PM, "Mike Jackson" wrote:
> I have said this a few times before on this list, so lets try it one more
> time:
>
> If Trolltech would properly support the --rpath option in the configure
> script deploying on OS X would be much easier. According to the
> configure --help I should be able to set a custom rpath for the
> libraries, but the makefiles just ignore the option when set on OS X.
> This is a major over sight and seems to indicate that the maintainer of
> that part of the build system does NOT have a proper understanding of
> how to build frameworks on OS X. The same problem occurs for dylibs
> built on OS X.
> I should NOT have to run install_name_tool at all if the build
> system would properly support the rpath option.
>
> Mike Jackson
> OS X Build specialist.
--
[ signature omitted ]
Message 18 in thread
Submitted, again, as a bug. I won't hold my breath though.. ;-)
Mike "always the optimist" Jackson
On 2007-08-10 19:18:00 -0400, Keith Esau <keith.esau@xxxxxxx> said:
> Have you submitted this as a bug to Trolltech? I would love to see this work
> BEFORE I need it. :)
>
> Keith
> **Please do not reply to me, reply to the list.**
>
>
> On 08-10-2007 4:11 PM, "Mike Jackson" wrote:
>
>> I have said this a few times before on this list, so lets try it one more
>> time:
>>
>> If Trolltech would properly support the --rpath option in the configure
>> script deploying on OS X would be much easier. According to the
>> configure --help I should be able to set a custom rpath for the
>> libraries, but the makefiles just ignore the option when set on OS X.
>> This is a major over sight and seems to indicate that the maintainer of
>> that part of the build system does NOT have a proper understanding of
>> how to build frameworks on OS X. The same problem occurs for dylibs
>> built on OS X.
>> I should NOT have to run install_name_tool at all if the build
>> system would properly support the rpath option.
>>
>> Mike Jackson
>> OS X Build specialist.
--
[ signature omitted ]
Message 19 in thread
Bug #174979 Filed
On 2007-08-10 19:18:00 -0400, Keith Esau <keith.esau@xxxxxxx> said:
> Have you submitted this as a bug to Trolltech? I would love to see this work
> BEFORE I need it. :)
>
> Keith
> **Please do not reply to me, reply to the list.**
>
>
> On 08-10-2007 4:11 PM, "Mike Jackson" wrote:
>
>> I have said this a few times before on this list, so lets try it one more
>> time:
>>
>> If Trolltech would properly support the --rpath option in the configure
>> script deploying on OS X would be much easier. According to the
>> configure --help I should be able to set a custom rpath for the
>> libraries, but the makefiles just ignore the option when set on OS X.
>> This is a major over sight and seems to indicate that the maintainer of
>> that part of the build system does NOT have a proper understanding of
>> how to build frameworks on OS X. The same problem occurs for dylibs
>> built on OS X.
>> I should NOT have to run install_name_tool at all if the build
>> system would properly support the rpath option.
>>
>> Mike Jackson
>> OS X Build specialist.
--
[ signature omitted ]
