Well, apparently, compiling for iOS app versus iOS static lib treats the processing of the .pch diifferently. Moving some things out of .pch in the app build which are in the .pch of the lib build solved my problem. I would like to know more about this if anyone can shed some light.
-koko On Apr 28, 2011, at 9:34 PM, koko wrote: > I am refining my previous post. > > What could cause the cpp class keyword to not be recognized when compiling an > iOS app? > > > BMetaData.h:13 class BMetaData > > /Volumes/_working/_working/_iOS/DisplayEmbroidery/../../LibBase/LibBase/BMetaData.h:13:0 > > /Volumes/_working/_working/_iOS/DisplayEmbroidery/../../LibBase/LibBase/BMetaData.h:13: > > > error: expected '=', ',', ';', 'asm' or '__attribute__' before 'BMetaData' > > > > -koko > > _______________________________________________ > > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) > > Please do not post admin requests or moderator comments to the list. > Contact the moderators at cocoa-dev-admins(at)lists.apple.com > > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/cocoa-dev/koko%40highrolls.net > > This email sent to k...@highrolls.net > _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
