Print

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

[wuischke]

Your version is old (I guess 6-12 months). Please get a more recent one.

[brainnolo]

I have compiled the UPnP 1.6.6 binaries which would be ok for distribution. However I was wondering if UPnP is now linked instead of dynamically loaded. In the first case you could remove those old files (the dylibs)

[gtoso]

I have compiled the UPnP 1.6.6 binaries which would be ok for distribution. However I was wondering if UPnP is now linked instead of dynamically loaded. In the first case you could remove those old files (the dylibs)

Yes, it's linked now (dinamically) so the 3 dylibs in the AppBundle Frameworks can be removed.

PS: I think it's time that someone rewrite the mac_packager script, too.
I have a my version, but the current one is too much personalized for my needs...

[brainnolo]

Ok, then is better if those files are removed. They are quite big! I will try to take a look at the packager but I my free time is really scarce at the moment

[brainnolo]

Ignore what is below, apparently it has been fixed already and was a problem in my copy (which is patched). There are still those dylib files in aMule.app/Contents/Frameworks to delete!

<old>
Ok there is an huge problem in compiling aMule for Mac with UPnP support. HFS+ is case insensitive and aMule UPnP.h is included where one would expect the real upnp.h is included. A fix would be to add to the include path just the prefix of UPnP and then include the files via <upnp/upnp.h> instead of "upnp.h". Another solution would be to rename UPnP.h to something else.
</old>