weak linking to framework and dylib

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

CodeCracker - 22 Oct 2005 06:54 GMT

Hi,
I was already using he -weak_framework and -weak_dylib option in my
.lcf file in CodeWarrior 8.0 but when I changed to Codewarrrior 9.6 I
find that the same file is not working. Until CW 8.0 I was getting
call in my main() and I was able to handle and provide information to
the user that the dylib or framework is missing. But since I moved to
CW 9.6 I see that I am not getting control in my main(). The
application crashes before this happens.
Is there something special (or in addition to what I have already done)
I have to do in 9.6 to achieve the same.

Thanks,
CodeCracker

Reply to this Message

Greg - 27 Oct 2005 15:18 GMT

> Hi,
> I was already using he -weak_framework and -weak_dylib option in my
[quoted text clipped - 6 lines]
> Is there something special (or in addition to what I have already done)
> I have to do in 9.6 to achieve the same.

I would check the release notes to see if they mention anything about
the linker. Otherwise, you may want to perform your check for the
weakly-linked libraries before main() is called. You can define your
own start routine that calls the existing start routine and place your
check there.

It's possible that there is some global object that is dependent on
those weakly-linked frameworks that causes the crash. The crash log or
debugger should help pin the problem down.

Greg

Reply to this Message

Mac Forum / Programming / CodeWarrior / October 2005

weak linking to framework and dylib