Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[mirko.g]

Errata corrige: I tried again on another machine, with wxWidgets r61983 and make succeeds! I don't know if it depends either on the machine or the wx revision: it worked with no more errors.
So, we need 7 patches (you can grab them either all around this thread or here) to have aMule r9817 successfully built on Snow Leopard.

Now I would like to understand what either mac_packager does or should do. I emptied aMule.app/Contents/Frameworks before building aMule and it's still empty after compiling and running mac_packager script. This way aMule suddenly crashes since it has none of the needed libraries:

Code: [Select]

Process:         amule [50941]
Path:            /Users/mirko/Desktop/TEMP/aMule-SVN-r9817/aMule.app/Contents/MacOS/amule
Identifier:      org.amule.aMule
Version:         ??? (???)
Code Type:       X86-64 (Native)
Parent Process:  launchd [78]

Date/Time:       2009-09-21 15:28:27.516 +0200
OS Version:      Mac OS X 10.6 (10A432)
Report Version:  6

Interval Since Last Report:          1329003 sec
Crashes Since Last Report:           26
Per-App Crashes Since Last Report:   10
Anonymous UUID:                      1D1B6006-D4A9-4737-871D-F22242E669A8

Exception Type:  EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Crashed Thread:  0

Dyld Error Message:
  Library not loaded: @executable_path/../Frameworks/libupnp.3.dylib
  Referenced from: /Users/mirko/Desktop/TEMP/aMule-SVN-r9817/aMule.app/Contents/MacOS/amule
  Reason: image not found

Model: iMac6,1, BootROM IM61.0093.B07, 2 processors, Intel Core 2 Duo, 2.16 GHz, 2 GB, SMC 1.10f3
Graphics: NVIDIA GeForce 7300 GT, NVIDIA GeForce 7300 GT, PCIe, 128 MB
Memory Module: global_name
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x87), Broadcom BCM43xx 1.0 (5.10.91.19)
Bluetooth: Version 2.2.0f18, 2 service, 0 devices, 1 incoming serial ports
Network Service: Ethernet, Ethernet, en0
Network Service: AirPort, AirPort, en1
Serial ATA Device: ST3250824AS  Q, 232,89 GB
Parallel ATA Device: MATSHITADVD-R   UJ-85J
USB Device: Built-in iSight, 0x05ac  (Apple Inc.), 0x8501, 0xfd400000
USB Device: Keyboard Hub, 0x05ac  (Apple Inc.), 0x1006, 0xfd300000
USB Device: USB-PS/2 Optical Mouse, 0x046d  (Logitech Inc.), 0xc00e, 0xfd310000
USB Device: Apple Keyboard, 0x05ac  (Apple Inc.), 0x0221, 0xfd320000
USB Device: Bluetooth USB Host Controller, 0x05ac  (Apple Inc.), 0x8206, 0x7d100000
USB Device: IR Receiver, 0x05ac  (Apple Inc.), 0x8240, 0x7d200000


[GonoszTopi]

The attached files a 0-sized... but don't mind, I know what they should contain.

I have all your patches prepared to be committed, however, there's one thing I don't understand. Namely: why does it work at all? I know why the last patches (for amule.h and amuled.cpp) didn't work for you first, the thing I don't understand is why did it work on the other machine.

The thing is, we're checking for __WXMAC__ being defined, but the last error output shows that you have __WXOSX_COCOA__ defined instead - which is right, and explains why the patch didn't work. Seems like that for the different frameworks on Mac wx (wx-svn-61995) now can have one of __WXMAC__, __WXCOCOA__, __WXOSX_CARBON__ or __WXOSX_COCOA__ defined.

Now what? Should we check for all these, is someone out there willing to try what works with which, or just wait until wx developers finally decide what means what?

[mirko.g]

the thing I don't understand is why did it work on the other machine.

I went back to the first machine and tried again... I figured out that it worked since I used a brand new aMule source and started from scratch.

The thing is, we're checking for __WXMAC__ being defined, but the last error output shows that you have __WXOSX_COCOA__ defined instead - which is right, and explains why the patch didn't work. Seems like that for the different frameworks on Mac wx (wx-svn-61995) now can have one of __WXMAC__, __WXCOCOA__, __WXOSX_CARBON__ or __WXOSX_COCOA__ defined.

Now what? Should we check for all these, is someone out there willing to try what works with which, or just wait until wx developers finally decide what means what?

I think thay really decided.
I trust in your opinion: if you think it's better to wait for a wxMac release I'll wait for it and focus on aMule 2.2.6 for Mac - btw, I'm working on aMule 2.2.6 for Mac too and I plan (hope) to release it in a couple of days -; otherwise, as I previously said, if you think this work is preparatory to the introduction of wx 3.0 I'll continue trying... 

[GonoszTopi]

I'm working on aMule 2.2.6 for Mac too and I plan (hope) to release it in a couple of days

Many are the hopers of your success.

if you think this work is preparatory to the introduction of wx 3.0 I'll continue trying... 

Sure it is. It will a) preprare aMule for wx-3.0; b) help identify bugs in wx before 3.0 released.

[mirko.g]

Many are the hopers of your success.

&

Sure it is. It will a) preprare aMule for wx-3.0; b) help identify bugs in wx before 3.0 released.

Both of these need me to understand where mac_packager point to. I'm more skilled on bash scripting than on Mac OS development for sure... hope I can help a little bit more with that...
I noticed a built aMule misses most of its libraries... and so happens with aMuleGUI and all other tools... why doesn't mac_packager take care of them?

UPDATE: with the patches from above I'm able now to build aMule SVN with wx2.9 and native 64-bit support. Using the official mac_packager aMule doesn't find some libraries... I tried to add libraries by hand but aMule doesn't correctly start and crashes with no crashlog... I will build aMule with debug option tomorrow.

[Kry]

I am the poor sod that made the mac_packager script. mac_packager should obviously take care of copying the needed libs and updating the pointed libraries path with otool.

Can you actually give me a full list of the steps you followed and what exactly I would need to build aMule in Snow Leopard? Don't get me wrong, I can do it by myself but it seems a waste of time for me to investigate when you could just tell me the exact steps you followed (what to install, what configure options to use, etc) and save me some of my extremely valuable time. Then I can fix mac_packager.

[Kry]

You should probably write all in a wiki article about Snow Leopard compilation.

[Stu Redman]

Can you actually give me a full list of the steps you followed and what exactly I would need to build aMule in Snow Leopard?

@Mirko: The best way to do that would be to make a wiki article for it. Don't bother about the code patches of course, these will be committed.

[mirko.g]

These are my notes on SnowLeopard: http://www.mac-factory.org/redmine/wiki/macmule/Snow_Leopard
It's a "work in progress" of course. But I can modify it for the official wiki if you agree.

[GonoszTopi]

--with-wxdir=../wxWidgets_r00000/wx-config

I bet you'd either use

• --with-wx-config=../wxWidgets_r00000/wx-config, or
• --with-wxdir=../wxWidgets_r00000

[mirko.g]

I bet you'd either use

• --with-wx-config=../wxWidgets_r00000/wx-config, or
• --with-wxdir=../wxWidgets_r00000

lol... I twisted them...

[Stu Redman]

But I can modify it for the official wiki if you agree.

Sure, go ahead. Best make a new page for it (copied from the MacOSX page) and link it on the compile page.