macOS changing Base SDK in xcode started giving errors

H

hrishidev

macrumors regular

Original poster

Dec 3, 2007

107

4

• Apr 18, 2011

• #1

I have legacy codebase for which base SDK was set to 10.4 . Now I changed the base SDK project setting to 10.5 and tried to build the project.
I am getting following error

/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/QTKit.framework/Headers/QTMovieLayer.h:17: error: cannot find interface declaration for 'CALayer', superclass of 'QTMovieLayer'

Click to expand...

Please help me to resolve this issue . Is there any guideline document for updrading Base SDK in xcode

 

gnasher729

Suspended

Nov 25, 2005

17,980

5,565

• Apr 19, 2011

• #2

hrishidev said:

Please help me to resolve this issue . Is there any guideline document for updrading Base SDK in xcode

Click to expand...

Have a look at that error message. Which file does it complain about? What SDK does it belong to?

 

H

hrishidev

macrumors regular

Original poster

Dec 3, 2007

107

4

• Apr 19, 2011

• #3

Thanks for reply . It is obviously visible that the complaint is about 10.4 sdk

I was bit surprized by the error message having reference to 10.4 sdk but all the frameworks belong to to absolute path "/System/Library/Frameworks/***.framework"

(by clicking get Info button on individual frameworks)

 

gnasher729

Suspended

Nov 25, 2005

17,980

5,565

• Apr 19, 2011

• #4

hrishidev said:

Thanks for reply . It is obviously visible that the complaint is about 10.4 sdk

I was bit surprized by the error message having reference to 10.4 sdk but all the frameworks belong to to absolute path "/System/Library/Frameworks/***.framework"

(by clicking get Info button on individual frameworks)

Click to expand...

So find the source file giving the error, Preprocess, and check where and why it includes that header file.

And System frameworks should have Path Type = Relative to current SDK.

 

Last edited: Apr 19, 2011

H

hrishidev

macrumors regular

Original poster

Dec 3, 2007

107

4

• Apr 20, 2011

• #5

Thanks gnasher729 , your reply triggered me think alternately .

The problem resolved now , after changing the base SDK ,we need to change Framework Search path setting in target as well.