[VSDK] Framework prebinding

Eric Forget forgete at cafederic.com
Wed Dec 3 13:54:35 CST 2003


Ruslan,

I've found it. VSDK.framework was binded to 0x00000000 which is reserved for
application. That's where all the conflicts where coming from. To resolve
it, set the "Standard Build Settings:Linking:Other linker flags" of your
target build settings to:

    -seg1addr 0xB0000000

This is reserved for third-party framework.

Also, make sure you double check your difference between Build style and
Target settings. Build style always have precedence. E.g.:

    Setting                     Target          Build style

    Instruction scheduling:     PowerPC G4      None

Wrapper extension is useless in Target since you have a framework target
anyway.

Finally, "Optimization Level" should be set to "Fastest, smallest" for
"Deployment" build style. That setting normally increase the speed, since
the code is smaller: less VM paging work.

Éric
___________________________________________________________________

 Eric Forget                       Cafederic
 ForgetE at cafederic.com             <http://www.cafederic.com/>

 Fingerprint <86D5 38F5 E1FD 5D9C 71C3  BAA3 797E 70A4 6210 C684>




More information about the Valentina mailing list