SIO2 and iPhone OS 3.0

I've not even begun to fully explore what sio2 can do, but I was wondering just how/what items from OS 3.0 would work in sio2?

I know Apple only announced it yesterday and the beta has only just been made available too - but just wondered if there are any plans to integrate the new features? Or if they wont really affect sio2 in any way?

Things that seem interesting are (lifted from http://developer.apple.com/iphone/program/sdk.html):

• In App Purchases
  
• Peer to Peer connectivity (I know SIO2 has networking - and I really should look at this before asking a question about networking!)
  

This *is* interesting. If you hear about any more of these features, please post them.


Best,
-j

The official announcement (from that page linked in my first post) states:

• In Application Purchases
  
• Apple Push Notification Services (so it can send out information to those who have downloaded your app, even if your app isnt running)
  
• The "Game Kit" which has peer-to-peer networking with bluetooth, and voice communication
  
• Access to the iPod library
  
• Map Kit Framework - to get to use GoogleMaps and the GPS etc
  

Gizmodo has a whole roundup of iPhone OS 3.0 images and what a lot of the new features are:
http://i.gizmodo.com/5172807/iphone-30-beta-os-impressions-and-walkthrough-gallery
Most of them seem fairly "normal" such as landscape SMS typing and the long awaited cut-and-paste functionality.

Still going to hold off installing the new firmware, in case it does things differently and risk losing any backwards compatibility - seeing as how 3.0 is only in Beta.

From what I've seen this is not touching the OpenGL ES functionality and integration so its like 100% sure that SIO2 will run flawless on 3.0

Engine runs flawless on SDK 3. Noticed a few warnings when recompiling to static lib... but doesn't affect anything.

I haven't upgrade yet can you paste the warnings?

tks!

Goldfrapp wrote:Engine runs flawless on SDK 3. Noticed a few warnings when recompiling to static lib... but doesn't affect anything.

Excellent news!
I wussed out with upgrading, will wait for the full release.

sio2interactive wrote:From what I've seen this is not touching the OpenGL ES functionality and integration so its like 100% sure that SIO2 will run flawless on 3.0

Thought as much, but just wanted to ask!

Can someone send me the console output of SIO2 when run on 3.0??? Just to check the extensions of GL|ES and OpenAL? (just to check if it worth me to upgrade now or not )

Tks in advance!

Its basically this warning found 96 times:

Projects/SIO2_StaticLibrary/src/sio2/sio2_resource.cc:1507: warning: deprecated conversion from string constant to 'char*'


Everywhere its found.

I'm trying to build sio2 for OS 3 b3. It builds without issue for the simulator. Trying to build for device results in all of those deprecated conversion warnings, but also an error: library not found for -lstdc++-static. Is it telling me it can't find the standard c++ library? I had no problems building the same project for 2.1 device and sim.

Not super familiar with xcode, so if anyone has any suggestions I would greatly appreciate it.


By the way, thanks for all the great work on the engine Mr SIO2

Switching the C++ Standard Library Type to dynamic under linking in project settings seems to be a workaround, but I'm seeing a pretty significant framerate hit (particularly in debug mode)... not sure if that is OS 3 or the switch to dynamic, or both...

Hopefully this is addressed in 1.3.6 - with the recent release of beta 5 of the 3.0 sdk, all new app's submitted to the store for approval must test against the OS 3.0.

SIO2 is independent of the iPhone OS... Only the I/O are OS specifics...

Sio2:

I was referring more to the template code compatibility with the 3.0 SDK. I just transitioned myself and ran into the same "library not found for -lstdc++-static" error in 1.3.5 referred to above. Selecting 'dynamic' didn't seem to help - I'll try a few other things and report back.

*Edit: The static stdc++ libraries are no longer found in the 3.0 SDK - you can get around this by copying them from 2.2.1 or switching to Dynamic as mentioned above.



- RMS

When build on 3.0 SDK I have error too: library not found for -lstdc++-static
Simulator work correctly.

Guys,

How exactly did you make your app work in a 3.0 device?

We're trying to build our game in 3.0 beta 5 and we're getting two strange phenomena:

a) while building with Dynamic linking, codesign complains saying "invalid object"

b) while building with Static linking we get the infamous lstdc-static error.

Some of you mentioned copying the stdc static lib from 2.2.1. Exactly what do you copy?

Thanks for any help,

Hugo

Hugo, you need to find that library in the 2.2 SDK folders, then copy it to the same folder but in the 3.0 SDK... if that makes sense? You should be able to also go through the library list and "add" the library to your project.

I'm not in front of my Mac so can't remember the procedure, but I remember it being fairly straight forward.

Jawdy wrote:Hugo, you need to find that library in the 2.2 SDK folders, then copy it to the same folder but in the 3.0 SDK... if that makes sense? You should be able to also go through the library list and "add" the library to your project.

I'm not in front of my Mac so can't remember the procedure, but I remember it being fairly straight forward.

Many thanks for your answer.

I'll give it a try and post feedback.

Hugo

compile for device 3.0
ld: warning: in src/sio2/libsio2_sim.a, file is not of required architecture
ld: warning: guard variable for btSoftBody::AJoint::IControl::Default()::defhas different visibility (default) in src/sio2/libsio2_dev.a(sio2.o) and (hidden) in /.../build/app.build/Release-iphoneos/app.build/Objects-normal/armv6/appDelegate.o
ld: warning: guard variable for btSoftBody::Body::xform() const::identityhas different visibility (default) in src/sio2/libsio2_dev.a(sio2.o) and (hidden) in /.../build/app.build/Release-iphoneos/app.build/Objects-normal/armv6/appDelegate.o
ld: warning: guard variable for btSoftBody::Body::invWorldInertia() const::iwihas different visibility (default) in src/sio2/libsio2_dev.a(sio2.o) and (hidden) in /.../build/app.build/Release-iphoneos/app.build/Objects-normal/armv6/appDelegate.o
ld: warning: _sio2Normalize has different visibility (default) in /src/sio2/libsio2_dev.a(sio2.o) and (hidden) in /..../build/app.build/Release-iphoneos/app.build/Objects-normal/armv6/app.o
ld: warning: btAlignedObjectArray<btSparseSdf<3>::Cell*>::clear() has different visibility (default) in src/sio2/libsio2_dev.a(sio2.o) and (hidden) in /.../build/app.build/Release-iphoneos/app.build/Objects-normal/armv6/btSoftRigidDynamicsWorld.o
ld: warning: _sio2StringTok has different visibility (default) in src/sio2/libsio2_dev.a(sio2.o) and (hidden) in /.../build/app.build/Release-iphoneos/app.build/Objects-normal/armv6/sio2_image.o
ld: warning: _sio2StringToUpper has different visibility (default) in src/sio2/libsio2_dev.a(sio2.o) and (hidden) in /.../build/app.build/Release-iphoneos/app.build/Objects-normal/armv6/sio2_image.o
error: Could not compile reconstructed dtrace script:
ld: error creating dtrace DOF section
However, compilation for device 2.2 occurs without errors, but includes warnings.
Tried to compile cocos2D for device 3.0 - without errors.
PS sio2 app, that is compiled for device 2.2 runs under OS 3.0 very good

I can assure you that the next version is already compiling without no warning on 3.0, the reason of the warning is that the lib have been linked against 2.2.1... It will still run perfectly on 2.2 firmware as well as 3.0 don't worry

OpenGL ES 2.0 makes shaders more accessible (much like what OpenGL 2.0 did for GLSL). Are there plans to make shader attachment part of the engine?

I already have a shader framework prototype up and running Im just waiting to have a device and an SDK that support shader to be able to use integrate / tweak it for SIO2

Hello!
Installed SDK 3.0
compilation for simulator occurs without errors, but for Iphone device 3.0 -

library not found for -lstdc++-static

SDK - 9m2736
could you help me?

Just change the C++ Library to be dynamic and not static... that's all...

yeap, I tried, but changed for one project and ran another(backuped) project that has not been changed =))
thanks