This is not really a bug, when compiling for iOS, the new iOS SDK gives many (hundreds in a complex project) warnings of type CPU_SUBTYPE_ARM_ALL deprecated. It woud be great if GLBasic was updated to use the new definition, becasue so many warnings difficults to find real warnings.
The other reason is because usually the state after deprecated is obsolete (maybe in iOS 5 SDK?), and then this will be errors not warnings.
I don't have Xcode installed at the moment but I believe this is probably a CPU target option in the project settings?
Yes. I am just unaware how to make that with my windows compiler.
Well, I see there is a general problem:
http://www.glbasic.com/forum/index.php?topic=6164.0 (http://www.glbasic.com/forum/index.php?topic=6164.0)
http://groups.google.com/group/harbour-devel/browse_thread/thread/78c14b7380406f35?fwc=1&pli=1 (http://groups.google.com/group/harbour-devel/browse_thread/thread/78c14b7380406f35?fwc=1&pli=1)
http://stackoverflow.com/questions/5755910/armv7-iphone-warnings (http://stackoverflow.com/questions/5755910/armv7-iphone-warnings)
maybe a solution?
https://trac.pjsip.org/repos/wiki/Getting-Started/iPhone#ProblemwithdeprecatedCPU_SUBTYPE_ARM_ALLsubtype (https://trac.pjsip.org/repos/wiki/Getting-Started/iPhone#ProblemwithdeprecatedCPU_SUBTYPE_ARM_ALLsubtype)
If I am not wrong (correct me), the idea of new SDKs is you to specify only armv7 with mcpu=cortex-a8 (the new on iPad and iPhone 4) to avoid these warnings. So I think when Apple wants will kick all not wanted users from their SDKs and it will be unavoidable, is the way Apple works, so if you want to target older systems, use older SDK, but you will not be able to use new features. Typical from Apple, split users from before (junk) and after (VIP).
If someone find a solution to remove the warnings without removing old devices targets (3.x), please put it here.
Any chance of the library files being updated to fix this issue? I'm building my first project at the moment and whilst the game runs with no problems, I am concerned about the approval process on the App Store.
I see if I can make a universal lib with the new compiler. Or even better: use the new compiler and dump X-Code totally.
Hi.
I too getting the same 96 warnings. Is there a workaround for this at the moment meantime?
Secondly - what is this about a new compiler and maybe not using Xcode? How would that work?
interesting...
Can anyone confirm if they have had an app approved even with these warnings.. Anyone?
There are quite a few GLBasic iPhone programs in the AppStore, so I presume they are :)
Quote from: MrTAToad on 2011-Dec-09
There are quite a few GLBasic iPhone programs in the AppStore, so I presume they are :)
They might be using older SDK's, I have both SDK's installed and have to use the older one for my JB'd iPhone but I have only submitted my apps using the old SDK myself. So do we know if the apps submitted with the newer SDK are ok for sure?
Bobble Heads uses the latest SDK.
Thanks for that.
Rock Crush got approved without any problems in the end - despite the 96 warnings.. (iOS5).
I don't know what has happened but since the latest iOS5 update I applied to xcode I can't get my apps to test correctly on my iPod Touch. I can do everything but save to disk, which completely screws everything up my testing. I'm trying to work out what I can do about this, perhaps just go back to the older version which was working great. In the meantime if anyone else gets a similar problem I'd be curious to hear about it.
Fixed the issue. The GDB debugger was preventing writing. Changing the settings or using the LLDB debugger instead works fine.
do we have a global solution for that?
if not what is the best way to solve this problem?
Michael
XCode uses GCC compiler, perhaps you or GLBasic can pass some parameter to the compiler and linker to disable a specific warning like -Wsomething. For example, -w parameter disable all compiler warnings. Or you can compile for ARMv7 only (iPhone 3GS/4/4S) like says the last link posted by Dark Schneider.