Qt-interest Archive, November 2007
Qt on Leopard with Tiger SDK
Message 1 in thread
I'm currently using Qt 4.3.2 and the 4.3.3 snapshots on the Mac. If I
build against the leopard SDK (-sdk /Developer/SDKs/MacOS10.5.sdk) all
is well. However if I try building against the Tiger SDK (which is
required because I still have to support Tiger!), using -sdk/Developer/
SDKs/MacOS10.4u.sdk, Qt builds for a while and then I get a linker
error:
ld: library not found for -lcrt1.10.5.o
(makes it until building Qt assistant before this happens during
link). This suspiciously looks like a leopard c-runtime library ;-)
I am building statically...
Can anyone confirm that they are also building statically and either
are or are not getting this? I also get this earlier (before the make
gets to assistant) when I include the qt3support library.
For the record, I can build Qt on another Tiger system, and then
"transplant" it... but this is a pain, especially because the Tiger
system is an old G4 and it takes all day to build the snapshot ;-)
Richard
--
[ signature omitted ]
Message 2 in thread
I think you should read here
http://lists.apple.com/archives/xcode-users/2007/Oct/msg00686.html
http://www.cocoabuilder.com/archive/message/xcode/2007/10/31/16396
-mmacosx-version-min=10.4 in order to build a binary that will link against
the 10.4u SDK and run on the 10.4 system.
"Richard S. Wright Jr." <rwright@xxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D8AEDA0C-515E-462E-A49C-0D9EF5445FCB@xxxxxxxxxxxxxxxxxxxxxxxx
> I'm currently using Qt 4.3.2 and the 4.3.3 snapshots on the Mac. If I
> build against the leopard SDK (-sdk /Developer/SDKs/MacOS10.5.sdk) all is
> well. However if I try building against the Tiger SDK (which is required
> because I still have to support Tiger!), using -sdk/Developer/
> SDKs/MacOS10.4u.sdk, Qt builds for a while and then I get a linker error:
>
> ld: library not found for -lcrt1.10.5.o
>
> (makes it until building Qt assistant before this happens during link).
> This suspiciously looks like a leopard c-runtime library ;-)
>
> I am building statically...
>
> Can anyone confirm that they are also building statically and either are
> or are not getting this? I also get this earlier (before the make gets to
> assistant) when I include the qt3support library.
>
> For the record, I can build Qt on another Tiger system, and then
> "transplant" it... but this is a pain, especially because the Tiger
> system is an old G4 and it takes all day to build the snapshot ;-)
>
> Richard
>
>
> --
> 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 3 in thread
Thanks!!
I presume the best way to do this is to edit
mkspecs/macx-xcode/qmake.conf
QMAKE_CFLAGS_PPC = -mmacosx-version-min=10.4
QMAKE_CFLAGS_X86 = -mmacosx-version-min=10.4
Then run configure and make...
Richard
On Nov 16, 2007, at 10:46 AM, Pat wrote:
> I think you should read here
>
> http://lists.apple.com/archives/xcode-users/2007/Oct/msg00686.html
> http://www.cocoabuilder.com/archive/message/xcode/2007/10/31/16396
>
> -mmacosx-version-min=10.4 in order to build a binary that will link
> against
> the 10.4u SDK and run on the 10.4 system.
>
>
> "Richard S. Wright Jr." <rwright@xxxxxxxxxxxxxxxxxxxxx> wrote in
> message
> news:D8AEDA0C-515E-462E-A49C-0D9EF5445FCB@xxxxxxxxxxxxxxxxxxxxxxxx
>> I'm currently using Qt 4.3.2 and the 4.3.3 snapshots on the Mac. If I
>> build against the leopard SDK (-sdk /Developer/SDKs/MacOS10.5.sdk)
>> all is
>> well. However if I try building against the Tiger SDK (which is
>> required
>> because I still have to support Tiger!), using -sdk/Developer/
>> SDKs/MacOS10.4u.sdk, Qt builds for a while and then I get a linker
>> error:
>>
>> ld: library not found for -lcrt1.10.5.o
>>
>> (makes it until building Qt assistant before this happens during
>> link).
>> This suspiciously looks like a leopard c-runtime library ;-)
>>
>> I am building statically...
>>
>> Can anyone confirm that they are also building statically and
>> either are
>> or are not getting this? I also get this earlier (before the make
>> gets to
>> assistant) when I include the qt3support library.
>>
>> For the record, I can build Qt on another Tiger system, and then
>> "transplant" it... but this is a pain, especially because the Tiger
>> system is an old G4 and it takes all day to build the snapshot ;-)
>>
>> Richard
>>
>>
>> --
>> 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 4 in thread
OK, I've tried multiple ways to add this command to the makespec, and/
or the .pro file. I'm still getting the error.
Can you throw me a bone?
Richard
On Nov 16, 2007, at 10:46 AM, Pat wrote:
> I think you should read here
>
> http://lists.apple.com/archives/xcode-users/2007/Oct/msg00686.html
> http://www.cocoabuilder.com/archive/message/xcode/2007/10/31/16396
>
> -mmacosx-version-min=10.4 in order to build a binary that will link
> against
> the 10.4u SDK and run on the 10.4 system.
>
>
> "Richard S. Wright Jr." <rwright@xxxxxxxxxxxxxxxxxxxxx> wrote in
> message
> news:D8AEDA0C-515E-462E-A49C-0D9EF5445FCB@xxxxxxxxxxxxxxxxxxxxxxxx
>> I'm currently using Qt 4.3.2 and the 4.3.3 snapshots on the Mac. If I
>> build against the leopard SDK (-sdk /Developer/SDKs/MacOS10.5.sdk)
>> all is
>> well. However if I try building against the Tiger SDK (which is
>> required
>> because I still have to support Tiger!), using -sdk/Developer/
>> SDKs/MacOS10.4u.sdk, Qt builds for a while and then I get a linker
>> error:
>>
>> ld: library not found for -lcrt1.10.5.o
>>
>> (makes it until building Qt assistant before this happens during
>> link).
>> This suspiciously looks like a leopard c-runtime library ;-)
>>
>> I am building statically...
>>
>> Can anyone confirm that they are also building statically and
>> either are
>> or are not getting this? I also get this earlier (before the make
>> gets to
>> assistant) when I include the qt3support library.
>>
>> For the record, I can build Qt on another Tiger system, and then
>> "transplant" it... but this is a pain, especially because the Tiger
>> system is an old G4 and it takes all day to build the snapshot ;-)
>>
>> Richard
>>
>>
>> --
>> 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 5 in thread
read here
http://doc.trolltech.com/4.3/deployment-mac.html
I think in your case woud be...
QMAKE_MACOSX_DEPLOYMENT_TARGET = 10.4
"Richard S. Wright Jr." <rwright@xxxxxxxxxxxxxxxxxxxxx> wrote in message
news:EF66CFDB-7266-4796-8314-AFA933EB0501@xxxxxxxxxxxxxxxxxxxxxxxx
> OK, I've tried multiple ways to add this command to the makespec, and/ or
> the .pro file. I'm still getting the error.
>
> Can you throw me a bone?
>
> Richard
>
> On Nov 16, 2007, at 10:46 AM, Pat wrote:
>
>> I think you should read here
>>
>> http://lists.apple.com/archives/xcode-users/2007/Oct/msg00686.html
>> http://www.cocoabuilder.com/archive/message/xcode/2007/10/31/16396
>>
>> -mmacosx-version-min=10.4 in order to build a binary that will link
>> against
>> the 10.4u SDK and run on the 10.4 system.
>>
>>
>> "Richard S. Wright Jr." <rwright@xxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:D8AEDA0C-515E-462E-A49C-0D9EF5445FCB@xxxxxxxxxxxxxxxxxxxxxxxx
>>> I'm currently using Qt 4.3.2 and the 4.3.3 snapshots on the Mac. If I
>>> build against the leopard SDK (-sdk /Developer/SDKs/MacOS10.5.sdk) all
>>> is
>>> well. However if I try building against the Tiger SDK (which is
>>> required
>>> because I still have to support Tiger!), using -sdk/Developer/
>>> SDKs/MacOS10.4u.sdk, Qt builds for a while and then I get a linker
>>> error:
>>>
>>> ld: library not found for -lcrt1.10.5.o
>>>
>>> (makes it until building Qt assistant before this happens during
>>> link).
>>> This suspiciously looks like a leopard c-runtime library ;-)
>>>
>>> I am building statically...
>>>
>>> Can anyone confirm that they are also building statically and either
>>> are
>>> or are not getting this? I also get this earlier (before the make gets
>>> to
>>> assistant) when I include the qt3support library.
>>>
>>> For the record, I can build Qt on another Tiger system, and then
>>> "transplant" it... but this is a pain, especially because the Tiger
>>> system is an old G4 and it takes all day to build the snapshot ;-)
>>>
>>> Richard
>>>
>>>
>>> --
>>> 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/
>>
>
> --
> 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 6 in thread
This does not work either... not in the .pro files, not when set as an
environment variable. Most of the Qt projects do build... it fails
after several components have already been built (fails on qt3support
or assistant) As in my first post, I suspect there is an error in the
Qt build script that is overriding the specified SDK, or is failing to
use the override provided.
Have you actually built Qt statically on Leopard using the Tiger
SDK... or have you just been sending me on a wild goose chase because
you think I don't know how to read documentation? I have been building
Qt for three years, on three different platforms fairly regularly.
This smells like a bug, but before I report it, I wanted to make sure
I wasn't the only one with the problem (in which case it most
assuredly is my own momentary stupidity). Your response led me to
believe you were answering my question (can anyone confirm that this
DOES work). I'm sorry for being cranky... but I've spent a couple of
days building Qt (well attempting to) every which way and it occurs to
me you didn't actually say you did get it to work. You have now
provided two different links to articles with two different solutions,
that should not apply to the Qt build system. It's reasonable for me
to think that you have not actually done this, but thought surely I
did not google enough before posting a silly question.
It seems to me the -sdk command line switch to configure ought to do
the trick... without any other gymnastics. That's what the build
system is for. Most of the projects do build... again fairly suspicious.
I would love to eat crow on this and look silly myself. The problem is
not getting Qt to link to other projects, the problem is getting Qt to
build. No matter what sdk/linker settings I use, it's own modules
should link against itself... I think I've just answered the question.
It's got to be a bug.
Richard
On Nov 16, 2007, at 4:46 PM, Pat wrote:
> read here
> http://doc.trolltech.com/4.3/deployment-mac.html
>
> I think in your case woud be...
> QMAKE_MACOSX_DEPLOYMENT_TARGET = 10.4
>
>
>
> "Richard S. Wright Jr." <rwright@xxxxxxxxxxxxxxxxxxxxx> wrote in
> message
> news:EF66CFDB-7266-4796-8314-AFA933EB0501@xxxxxxxxxxxxxxxxxxxxxxxx
>> OK, I've tried multiple ways to add this command to the makespec,
>> and/ or
>> the .pro file. I'm still getting the error.
>>
>> Can you throw me a bone?
>>
>> Richard
>>
>> On Nov 16, 2007, at 10:46 AM, Pat wrote:
>>
>>> I think you should read here
>>>
>>> http://lists.apple.com/archives/xcode-users/2007/Oct/msg00686.html
>>> http://www.cocoabuilder.com/archive/message/xcode/2007/10/31/16396
>>>
>>> -mmacosx-version-min=10.4 in order to build a binary that will link
>>> against
>>> the 10.4u SDK and run on the 10.4 system.
>>>
>>>
>>> "Richard S. Wright Jr." <rwright@xxxxxxxxxxxxxxxxxxxxx> wrote in
>>> message
>>> news:D8AEDA0C-515E-462E-A49C-0D9EF5445FCB@xxxxxxxxxxxxxxxxxxxxxxxx
>>>> I'm currently using Qt 4.3.2 and the 4.3.3 snapshots on the Mac.
>>>> If I
>>>> build against the leopard SDK (-sdk /Developer/SDKs/
>>>> MacOS10.5.sdk) all
>>>> is
>>>> well. However if I try building against the Tiger SDK (which is
>>>> required
>>>> because I still have to support Tiger!), using -sdk/Developer/
>>>> SDKs/MacOS10.4u.sdk, Qt builds for a while and then I get a linker
>>>> error:
>>>>
>>>> ld: library not found for -lcrt1.10.5.o
>>>>
>>>> (makes it until building Qt assistant before this happens during
>>>> link).
>>>> This suspiciously looks like a leopard c-runtime library ;-)
>>>>
>>>> I am building statically...
>>>>
>>>> Can anyone confirm that they are also building statically and
>>>> either
>>>> are
>>>> or are not getting this? I also get this earlier (before the
>>>> make gets
>>>> to
>>>> assistant) when I include the qt3support library.
>>>>
>>>> For the record, I can build Qt on another Tiger system, and then
>>>> "transplant" it... but this is a pain, especially because the Tiger
>>>> system is an old G4 and it takes all day to build the snapshot ;-)
>>>>
>>>> Richard
>>>>
>>>>
>>>> --
>>>> 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/
>>>
>>
>> --
>> 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 7 in thread
> Have you actually built Qt statically on Leopard using the Tiger SDK...
I haven't yet
>or have you just been sending me on a wild goose chase because you think I
>don't know how to read documentation?
I think I do not deserve your comment... I was just trying to help you with
the info I've got
that for sure was more that the info you've read...
Pat
"Richard S. Wright Jr." <rwright@xxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D97AC60F-AE53-4CA5-933E-188B7F9E211B@xxxxxxxxxxxxxxxxxxxxxxxx
> This does not work either... not in the .pro files, not when set as an
> environment variable. Most of the Qt projects do build... it fails after
> several components have already been built (fails on qt3support or
> assistant) As in my first post, I suspect there is an error in the Qt
> build script that is overriding the specified SDK, or is failing to use
> the override provided.
>
> Have you actually built Qt statically on Leopard using the Tiger SDK...
> or have you just been sending me on a wild goose chase because you think
> I don't know how to read documentation? I have been building Qt for three
> years, on three different platforms fairly regularly. This smells like a
> bug, but before I report it, I wanted to make sure I wasn't the only one
> with the problem (in which case it most assuredly is my own momentary
> stupidity). Your response led me to believe you were answering my
> question (can anyone confirm that this DOES work). I'm sorry for being
> cranky... but I've spent a couple of days building Qt (well attempting
> to) every which way and it occurs to me you didn't actually say you did
> get it to work. You have now provided two different links to articles
> with two different solutions, that should not apply to the Qt build
> system. It's reasonable for me to think that you have not actually done
> this, but thought surely I did not google enough before posting a silly
> question.
>
> It seems to me the -sdk command line switch to configure ought to do the
> trick... without any other gymnastics. That's what the build system is
> for. Most of the projects do build... again fairly suspicious.
>
> I would love to eat crow on this and look silly myself. The problem is
> not getting Qt to link to other projects, the problem is getting Qt to
> build. No matter what sdk/linker settings I use, it's own modules should
> link against itself... I think I've just answered the question. It's got
> to be a bug.
>
> Richard
>
>
>
> On Nov 16, 2007, at 4:46 PM, Pat wrote:
>
>> read here
>> http://doc.trolltech.com/4.3/deployment-mac.html
>>
>> I think in your case woud be...
>> QMAKE_MACOSX_DEPLOYMENT_TARGET = 10.4
>>
>>
>>
>> "Richard S. Wright Jr." <rwright@xxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:EF66CFDB-7266-4796-8314-AFA933EB0501@xxxxxxxxxxxxxxxxxxxxxxxx
>>> OK, I've tried multiple ways to add this command to the makespec, and/
>>> or
>>> the .pro file. I'm still getting the error.
>>>
>>> Can you throw me a bone?
>>>
>>> Richard
>>>
>>> On Nov 16, 2007, at 10:46 AM, Pat wrote:
>>>
>>>> I think you should read here
>>>>
>>>> http://lists.apple.com/archives/xcode-users/2007/Oct/msg00686.html
>>>> http://www.cocoabuilder.com/archive/message/xcode/2007/10/31/16396
>>>>
>>>> -mmacosx-version-min=10.4 in order to build a binary that will link
>>>> against
>>>> the 10.4u SDK and run on the 10.4 system.
>>>>
>>>>
>>>> "Richard S. Wright Jr." <rwright@xxxxxxxxxxxxxxxxxxxxx> wrote in
>>>> message
>>>> news:D8AEDA0C-515E-462E-A49C-0D9EF5445FCB@xxxxxxxxxxxxxxxxxxxxxxxx
>>>>> I'm currently using Qt 4.3.2 and the 4.3.3 snapshots on the Mac. If I
>>>>> build against the leopard SDK (-sdk /Developer/SDKs/ MacOS10.5.sdk)
>>>>> all
>>>>> is
>>>>> well. However if I try building against the Tiger SDK (which is
>>>>> required
>>>>> because I still have to support Tiger!), using -sdk/Developer/
>>>>> SDKs/MacOS10.4u.sdk, Qt builds for a while and then I get a linker
>>>>> error:
>>>>>
>>>>> ld: library not found for -lcrt1.10.5.o
>>>>>
>>>>> (makes it until building Qt assistant before this happens during
>>>>> link).
>>>>> This suspiciously looks like a leopard c-runtime library ;-)
>>>>>
>>>>> I am building statically...
>>>>>
>>>>> Can anyone confirm that they are also building statically and either
>>>>> are
>>>>> or are not getting this? I also get this earlier (before the make
>>>>> gets
>>>>> to
>>>>> assistant) when I include the qt3support library.
>>>>>
>>>>> For the record, I can build Qt on another Tiger system, and then
>>>>> "transplant" it... but this is a pain, especially because the Tiger
>>>>> system is an old G4 and it takes all day to build the snapshot ;-)
>>>>>
>>>>> Richard
>>>>>
>>>>>
>>>>> --
>>>>> 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/
>>>>
>>>
>>> --
>>> 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/
>>
>
> --
> 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 8 in thread
Alright... I didn't mean to be insulting. Let's just call it a draw.
I'll take some blame for not being more explicit with my post, and for
misinterpreting your response.
This list certainly doesn't need people getting their heads bit off
for just trying to help.
Richard
On Nov 17, 2007, at 9:07 AM, Pat wrote:
>> Have you actually built Qt statically on Leopard using the Tiger
>> SDK...
> I haven't yet
>
>> or have you just been sending me on a wild goose chase because you
>> think I
>> don't know how to read documentation?
> I think I do not deserve your comment... I was just trying to help
> you with
> the info I've got
> that for sure was more that the info you've read...
>
> Pat
>
>
>
> "Richard S. Wright Jr." <rwright@xxxxxxxxxxxxxxxxxxxxx> wrote in
> message
> news:D97AC60F-AE53-4CA5-933E-188B7F9E211B@xxxxxxxxxxxxxxxxxxxxxxxx
>> This does not work either... not in the .pro files, not when set as
>> an
>> environment variable. Most of the Qt projects do build... it fails
>> after
>> several components have already been built (fails on qt3support or
>> assistant) As in my first post, I suspect there is an error in the
>> Qt
>> build script that is overriding the specified SDK, or is failing
>> to use
>> the override provided.
>>
>> Have you actually built Qt statically on Leopard using the Tiger
>> SDK...
>> or have you just been sending me on a wild goose chase because you
>> think
>> I don't know how to read documentation? I have been building Qt
>> for three
>> years, on three different platforms fairly regularly. This smells
>> like a
>> bug, but before I report it, I wanted to make sure I wasn't the
>> only one
>> with the problem (in which case it most assuredly is my own
>> momentary
>> stupidity). Your response led me to believe you were answering my
>> question (can anyone confirm that this DOES work). I'm sorry for
>> being
>> cranky... but I've spent a couple of days building Qt (well
>> attempting
>> to) every which way and it occurs to me you didn't actually say
>> you did
>> get it to work. You have now provided two different links to
>> articles
>> with two different solutions, that should not apply to the Qt build
>> system. It's reasonable for me to think that you have not actually
>> done
>> this, but thought surely I did not google enough before posting a
>> silly
>> question.
>>
>> It seems to me the -sdk command line switch to configure ought to
>> do the
>> trick... without any other gymnastics. That's what the build
>> system is
>> for. Most of the projects do build... again fairly suspicious.
>>
>> I would love to eat crow on this and look silly myself. The problem
>> is
>> not getting Qt to link to other projects, the problem is getting Qt
>> to
>> build. No matter what sdk/linker settings I use, it's own modules
>> should
>> link against itself... I think I've just answered the question.
>> It's got
>> to be a bug.
>>
>> Richard
>>
>>
>>
>> On Nov 16, 2007, at 4:46 PM, Pat wrote:
>>
>>> read here
>>> http://doc.trolltech.com/4.3/deployment-mac.html
>>>
>>> I think in your case woud be...
>>> QMAKE_MACOSX_DEPLOYMENT_TARGET = 10.4
>>>
>>>
>>>
>>> "Richard S. Wright Jr." <rwright@xxxxxxxxxxxxxxxxxxxxx> wrote in
>>> message
>>> news:EF66CFDB-7266-4796-8314-AFA933EB0501@xxxxxxxxxxxxxxxxxxxxxxxx
>>>> OK, I've tried multiple ways to add this command to the
>>>> makespec, and/
>>>> or
>>>> the .pro file. I'm still getting the error.
>>>>
>>>> Can you throw me a bone?
>>>>
>>>> Richard
>>>>
>>>> On Nov 16, 2007, at 10:46 AM, Pat wrote:
>>>>
>>>>> I think you should read here
>>>>>
>>>>> http://lists.apple.com/archives/xcode-users/2007/Oct/msg00686.html
>>>>> http://www.cocoabuilder.com/archive/message/xcode/2007/10/31/16396
>>>>>
>>>>> -mmacosx-version-min=10.4 in order to build a binary that will
>>>>> link
>>>>> against
>>>>> the 10.4u SDK and run on the 10.4 system.
>>>>>
>>>>>
>>>>> "Richard S. Wright Jr." <rwright@xxxxxxxxxxxxxxxxxxxxx> wrote in
>>>>> message
>>>>> news:D8AEDA0C-515E-462E-A49C-0D9EF5445FCB@xxxxxxxxxxxxxxxxxxxxxxxx
>>>>>> I'm currently using Qt 4.3.2 and the 4.3.3 snapshots on the
>>>>>> Mac. If I
>>>>>> build against the leopard SDK (-sdk /Developer/SDKs/
>>>>>> MacOS10.5.sdk)
>>>>>> all
>>>>>> is
>>>>>> well. However if I try building against the Tiger SDK (which is
>>>>>> required
>>>>>> because I still have to support Tiger!), using -sdk/Developer/
>>>>>> SDKs/MacOS10.4u.sdk, Qt builds for a while and then I get a
>>>>>> linker
>>>>>> error:
>>>>>>
>>>>>> ld: library not found for -lcrt1.10.5.o
>>>>>>
>>>>>> (makes it until building Qt assistant before this happens during
>>>>>> link).
>>>>>> This suspiciously looks like a leopard c-runtime library ;-)
>>>>>>
>>>>>> I am building statically...
>>>>>>
>>>>>> Can anyone confirm that they are also building statically and
>>>>>> either
>>>>>> are
>>>>>> or are not getting this? I also get this earlier (before the
>>>>>> make
>>>>>> gets
>>>>>> to
>>>>>> assistant) when I include the qt3support library.
>>>>>>
>>>>>> For the record, I can build Qt on another Tiger system, and then
>>>>>> "transplant" it... but this is a pain, especially because the
>>>>>> Tiger
>>>>>> system is an old G4 and it takes all day to build the
>>>>>> snapshot ;-)
>>>>>>
>>>>>> Richard
>>>>>>
>>>>>>
>>>>>> --
>>>>>> 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/
>>>>>
>>>>
>>>> --
>>>> 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/
>>>
>>
>> --
>> 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 9 in thread
Richard S. Wright Jr. wrote:
> It seems to me the -sdk command line switch to configure ought to do the
> trick... without any other gymnastics. That's what the build system is
> for. Most of the projects do build... again fairly suspicious.
Hi Richard, in case you are still struggling with this: I was able to
get Qt built with your configuration by adding -mmacosx-version-min=10.4
to each linker line or by exporting MACOSX_DEPLOYMENT_TARGET="10.4".
I agree that the build system should take care of this when you specify
-sdk at the configure line, we'll get this fixed in a future Qt release.
- Morten
--
[ signature omitted ]
Message 10 in thread
Thanks very much, that did the trick!
Richard
On Nov 20, 2007, at 3:31 AM, Morten Sørvig wrote:
> Richard S. Wright Jr. wrote:
>> It seems to me the -sdk command line switch to configure ought to
>> do the trick... without any other gymnastics. That's what the build
>> system is for. Most of the projects do build... again fairly
>> suspicious.
>
> Hi Richard, in case you are still struggling with this: I was able
> to get Qt built with your configuration by adding -mmacosx-version-
> min=10.4 to each linker line or by exporting
> MACOSX_DEPLOYMENT_TARGET="10.4".
>
> I agree that the build system should take care of this when you
> specify -sdk at the configure line, we'll get this fixed in a future
> Qt release.
>
> - Morten
>
> --
> 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 11 in thread
On Nov 17, 2007 12:43 AM, Richard S. Wright Jr.
<rwright@xxxxxxxxxxxxxxxxxxxxx> wrote:
> Have you actually built Qt statically on Leopard using the Tiger
> SDK... or have you just been sending me on a wild goose chase because
> you think I don't know how to read documentation? I have been building
Just as an aside to the meat of this conversation -- statically
linking on OSX, while possible, is not supported by Apple, and is
entirely Use At Your Own Risk:
http://developer.apple.com/qa/qa2001/qa1118.html
Your best bet is to build as frameworks and use @executable_path/...
to find the Qt dynamic libraries, it would make your software more
supportable (easy to point to debug libraries!), and save you a lot of
issues in the future.
--
[ signature omitted ]
Message 12 in thread
That article is about trying to link to the OS X _runtime_ statically.
I agree this is a bad idea on the Mac (but not necessarily on Windows).
It is my understanding that using the -static flag creates static Qt
libraries, but does not link statically to the OS X runtime. My XCode
projects are linking statically to Qt, but dynamically to the OS X
runtime and other frameworks. Mixing static and dynamic libraries (or
frameworks) is a recipe for disaster... but again, I don't think that
is what is actually happening. I doubt I'd even be able to link my
application if this was the case (or that I would have gotten away
with it for over three years and dozens of projects).
I also partially make this "assumption" because this is the behavior
on Windows (on which, I have far far more experience). Using -static
makes static libraries that are also linked against the DLL runtimes.
In fact, if you want to use the static runtime, you have to modify the
makespecs manually before running configure (which I do, against
Microsoft's advice... but I know many experienced Windows developers
who do the same... you just need to watch your DLL dependencies).
There are lots of good reasons to link in libraries statically. DLL's/
Frameworks have their uses, but like choice of programming language,
one size does not fit all.
Richard
On Nov 20, 2007, at 10:43 PM, Benjamin Reed wrote:
> On Nov 17, 2007 12:43 AM, Richard S. Wright Jr.
> <rwright@xxxxxxxxxxxxxxxxxxxxx> wrote:
>
>> Have you actually built Qt statically on Leopard using the Tiger
>> SDK... or have you just been sending me on a wild goose chase because
>> you think I don't know how to read documentation? I have been
>> building
>
> Just as an aside to the meat of this conversation -- statically
> linking on OSX, while possible, is not supported by Apple, and is
> entirely Use At Your Own Risk:
>
> http://developer.apple.com/qa/qa2001/qa1118.html
>
> Your best bet is to build as frameworks and use @executable_path/...
> to find the Qt dynamic libraries, it would make your software more
> supportable (easy to point to debug libraries!), and save you a lot of
> issues in the future.
>
> --
> 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 ]
