aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: Understanding OS X dev of aMule [Part 1: SDK & GCC]  (Read 3800 times)

mirko.g

  • Global Moderator
  • Full Member
  • *****
  • Karma: 6
  • Offline Offline
  • Posts: 188
  • Grattatio pallorum omnia mala repellent!
    • Personal WebSite
Understanding OS X dev of aMule [Part 1: SDK & GCC]
« on: August 26, 2009, 01:14:37 PM »

I suppose the most of these questions will be answered by gtoso  ;) but everyone who want to understand something more on building aMule on Mac OS is welcome.

SDK & GCC
I'm confused about SDK, architectures and target OS...
I'm pretty sure of the outcome without further flags specifications. If your starting OS is Leopard you must use SDK version 10.4 to run your app on both Leopard and Tiger. If you start from Tiger SDK 10.4 will be automatically used...
If you want your app running on a different architecture you have to build aMule Universal Binary. Some questions will come on this, but I have one before:

What if I aMule with gcc-3.3? AFAIK it's able to compile only PPC apps. Could it allow cross-compilation?

Moreover: what about needed libraries and tools? I suppose wxWidgets needs to be compiled with the same flags I will use for aMule (I mean same SDK and variant). My doubt is about MacPorts: it automatically uses SDK and variant of the host system... Starting from Leopard, should I set universal_target=10.4 and universal_sysroot=/Developer/SDKs/MacOSX10.4u.sdk  into macports.conf to have aMule running on Tiger?

And: what if I use gcc-4.2? Does it limit the app retro-compatibility?

Other question coming...  ;)
« Last Edit: September 11, 2009, 10:21:40 AM by mirko.g »
Logged