Aspen simulator works only on Intel Macs - which means it is dependent (together with its frameworks) to x86 processors (when compiling in Xcode, there is an option - compile for ARM(the iPhone processor) or Aspen simulator (x86 processor)).

The point is: when you replace original frameworks on your iPhone with those copied from SDK folder, they won't work (and will render your iPhone unable to boot), because they're compiled for different processor architecture.

If I am wrong, then someone please correct me

Cheers!

Just look at your Developers/Platform folder....
There are 2:
AspenSimulator
Aspen

AspenSimulator contains frameworks and Apps compiled for x86 and Aspen contains binarys for ARM...

cYa ~Neo

Okay, i am toying around with the SDK now, and found some strange and interesting stuff. When i try to build a new framework-clean binary, using the "Debug" build configuration, Xcode spits out:

"Codesign error: no certificate for identifier "iPhone Developer" was found in your keychain"

And the build "fails", however, the binary is actually produced. There is little difference between the release build (which builds without any errors) and the debug build. I looked at them both in a hex editor (unfortunately i don't have an ARM disassembler ), and there is practically no difference, apart from some extra code i would guess, that allows breakpoints, and GDB to connect to the process and such.

Now here comes the fun part, the binary is actually running perfectly on the iPhone. There is no encryption, whatsoever. It is a perfectly fine ARM6 binary, that can be executed without problems. Of course this was to be suspected, but you never know

So, that leaves us at having to find simple way to load the 1.2 frameworks from the SDK dynamically when a SDK compiled application is loaded.

By the way, does someone know an ARM disassembler for OS X?

Just to sum up: A binary compiled using the official SDK can run on 1.1.4

Cheers!

Oh, and if anyone knows some good resources on how OS X/iPhone handles frameworks, please give me a shout. I'm pretty shure it must be relatively simple to make a seperate copy of the 1.2 frameworks and binaries that the a pre 1.2 iphone can use for running SDK compiled apps.

I assume they are handled just like any other dynamically loaded library. Not sure this applies to the iPhone, but you can change the path's for OS X.

From "man dyld" :

DYLD_FRAMEWORK_PATH
This is a colon separated list of directories that contain
frameworks. The dynamic linker searches these directories
before it searches for the framework by its install name. It
allows you to test new versions of existing frameworks. (A
framework is a library install name that ends in the form
XXX.framework/Versions/YYY/XXX or XXX.framework/XXX, where XXX
and YYY are any name.)

For each framework that a program uses, the dynamic linker looks
for the framework in each directory in DYLD_FRAMEWORK_PATH in
turn. If it looks in all the directories and can't find the
framework, it searches the directories in DYLD_LIBRARY_PATH in
turn. If it still can't find the framework, it then searches
DYLD_FALLBACK_FRAMEWORK_PATH and DYLD_FALLBACK_LIBRARY_PATH in
turn.

Is it possible to do a static link when compiling from xcode? I would guess not

rad

Originally Posted by nfotx

Just to sum up: A binary compiled using the official SDK can run on 1.1.4

This is a great piece of information. I have 1.1.3 on my Touch and the sample app that I have built doesn't run.

Questions:
- do I need to upgrade at 1.1.4 to run my own apps?
- where do you get the exe? Under the build folder by default 2 folders are produced and only one seems to have the .app file.

thx for your post, it shed some light in my dark brain.

Originally Posted by radical

I assume they are handled just like any other dynamically loaded library. Not sure this applies to the iPhone, but you can change the path's for OS X.

From "man dyld" :
...
Is it possible to do a static link when compiling from xcode? I would guess not
rad

I can report a partial success using the specified environment variables.
I copied the files from Aspen1.2.sdk/System/Library und Aspen1.2.sdk/usr/lib to
/var/root/Aspen/{Library,usr}. In addition I hat do symlink all *.dylb's in the Frameworks to usr/lib because dyld was unable to locate them inside the frameworks.
Then I did the following:

Code:

# export DYLD_FRAMEWORK_PATH=/var/root/Aspen/Library
# export DYLD_LIBRARY_PATH=/var/root/Aspen/usr/lib                                  
# /Applications/hello.app/hello                                                           
dyld: Symbol not found: ___kCFVolatileDomainCallBacks
  Referenced from: /System/Library/Frameworks/Foundation.framework/Foundation
  Expected in: /var/root/Aspen/Library/Frameworks/CoreFoundation.framework/CoreFoundation

zsh: trace trap  /Applications/hello.app/hello

As you can see dyld gets past the ObjC part but encounters some relocation error in the core Frameworks.
This may also be a result of my quick-hack-style testing attempt but at least it looks like running 1.2.0 apps with a seperate library and framework root is not totally impossible

nfotx, are you planning to write a little tutorial? I also know this is pushing it, but did the debug build run properly with the debugger on the computer?

True, a mini tutorial would be just great!
I'm comfortable with code, but totally new to the mac development world. However your post has very good hints!

Originally Posted by nfotx

Also, in a vain attempt, i tried replacing the frameworks on the iPhone with the ones from the SDK, no luck

This may somehow work. A lot of the frameoworks are now in PrivateFrameworks but symlinked to Frameworks, and I assume you didn't do the symlink nor chmod 777 the new frameworks