aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Pages: 1 [2] 3

Author Topic: How to Compile for Mac  (Read 38895 times)

Kry

  • Ex-developer
  • Retired admin
  • Hero Member
  • *****
  • Karma: -665
  • Offline Offline
  • Posts: 5795
Re: How to Compile for Mac
« Reply #15 on: March 06, 2005, 07:34:07 PM »
I compiled and run aMule in wxCocoa several times. But it's on TOO EARLY development.
Logged

zankty

  • Guest
Re: How to Compile for Mac
« Reply #16 on: March 31, 2005, 03:46:04 AM »
Hi,
I compiled it and all basic functions are working, but my scroll isn't working.

When I use the "./configure --disable-systray --disable-gtk --with-wx-config=/usr/local/bin/wx-config"
I get this message:

 "
....
checking for curl >= 7.9.5... yes (version 7.10.2)
checking for libpng-config... /sw/bin/libpng-config
checking for libpng version >= 1.2.0... yes (version 1.2.5)
checking gd.h usability... no
checking gd.h presence... no
checking for gd.h... no
configure:
        WARNING: libpng-devel >= 1.2.0 is needed for amuleweb
       
checking for gdlib-config... /sw/bin/gdlib-config
checking for gdlib version >= 2.0.0... yes (version 2.0.23)
checking for gd.h... (cached) no
configure:
        WARNING: gd-lib >= 2.0.0, or a functional gd.h (from gd-devel) not found.
        gd-lib is needed for fully funtional cas. If you don't have gd-lib,
        cas will be compiled, but you won't be able to create that cool
        status image (text mode however will work). Also note that you should
        upgrade to gd-lib >= 2.0.22 if you intend to use it, other versions have
        not been tested and therefore are unsupported at the moment.
        Please check that gdlib-config is in your default path, check out
        LD_LIBRARY_PATH or equivalent variable.
        Or this might also be that your gdlib-config has other name.
        Please try again with --with-gdlib-config=/usr/bin/gdlib-config
        (replace /usr/bin/gdlib-config with a valid path to your gdlib-config).
        If you use compiled packages check if you have devel pack installed.
        To download the lastest version check http://www.boutell.com/gd
        for sources.
       
checking whether we need the GUI... yes
checking for wx-config... /usr/local/bin/wx-config
checking for wxWidgets version >= 2.4.2... yes (version 2.5.4)
configure: WARNING: wxWidgets >=2.5.0: Using wx-config --libs base,net
checking if wxWidgets was linked with GTK2... no
checking for gtk-config... /sw/bin/gtk-config
checking for GTK - version >= 1.2.0... yes
checking if wxWidgets version >=2.5.0 ... yes
crypto check disabled, using embedded libs
checking for X... libraries /usr/X11R6/lib, headers /usr/X11R6/include
checking for working alloca.h... yes
checking for alloca... yes
checking for dirent.h that defines DIR... yes
checking for library containing opendir... none required
checking for ANSI C header files... (cached) yes
checking argz.h usability... no
checking argz.h presence... no

....

  Configured aMule 2.0.0rc8 for 'powerpc-apple-darwin7.8.0'.

  aMule enabled options:

  **** aMule Core ****
  Should aMule be compiled in debug mode?                  yes
  Should aMule be compiled with verbose console output?    no
  Should aMule be compiled with upload speed sense?        no
  Should aMule be compiled with profiling?                 no
  Should aMule be compiled with optimizations?             no
  Should aMule be compiled with systray?                   no
  Should aMule be compiled with UTF-8 systray?             no
  Should aMule be compiled with pure GTK code?             no
  Should aMule be linked against patched gsocket?          no
  Should aMule monolithic application be built?            yes
  Should aMule daemon version be built? (EXPERIMENTAL)     no
  Should aMule remote gui be built? (EXPERIMENTAL)         no
  Crypto++ library/headers style?                          embeded

  **** aMule TextClient ****
  Should aMule Command Line Client be built?               no
  Should aMule GUI Client be built?                        no

  **** aMule WebServer ****
  Should aMule WebServer be built?                         no
  Should aMule WebServer GUI be built?                     no

  **** aMule ED2K Links Handler ****
  Should aMule ED2K Links Handler be built?                yes

  **** aMuleLinkCreator ****
  Should aMuleLinkCreator GUI version (alc) be built?      yes
  Should aMuleLinkCreator for console (alcc) be built?     yes

  **** aMule Statistics ****
  Should C aMule Statistics (CAS) be built?                yes
  Should aMule GUI Statistics (wxCas) be built?            yes

  **** General Libraries and Tools ****
  Should ccache support be enabled?                        no
  Libraries aMule will use to build:
                                       wxWidgets          2.5.4
                                       GTK                1.2.10 (Not used)

"
Is that supposed to be like that????
Logged

ken

  • Hero Member
  • *****
  • Karma: 4
  • Offline Offline
  • Posts: 825
Re: How to Compile for Mac
« Reply #17 on: April 01, 2005, 08:16:53 AM »
zankty, that configure output looks fine.  The warnings are benign.

Quote
my scroll isn't working

Do you mean the scroll-wheel?  If that's what you mean, it's a known bug with wxMac that we're working on getting fixed.
Logged

bj575bd

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 21
WxMac 2.5.4 Compile Problem
« Reply #18 on: April 18, 2005, 02:03:16 PM »
Hi,
I have read the tutorial but when i compile WxMac 2.5.4 (typing make) anfter a while the shell freezes at the istruction "Derez".

I leave it alone for the enteire night but in the morning is still there.

Some suggestions ?

My mac:
PowerMac 2xG5 1.8
ATI Radeon 9800 XT 256Mb Ram
1Gb ram
2x80 Gb serial ata hd raid 0
MacOsx 10.3.9
Logged
******************
Warbird

bj575bd

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 21
WxMac 2.5.4 Compile Problem II
« Reply #19 on: April 18, 2005, 08:19:08 PM »
Here is the istruction that freezes:

/Developer/Tools/DeRez lib/libwx_mac-2.5.4.rsrc Carbon.r -useDF >lib/libwx_mac-2.5.4.r

I tried with the version 2.5.5 also but same problem.
Logged
******************
Warbird

ken

  • Hero Member
  • *****
  • Karma: 4
  • Offline Offline
  • Posts: 825
Re: How to Compile for Mac
« Reply #20 on: April 18, 2005, 09:21:35 PM »
Hmm.  There was just a thread about this problem on the wx-dev mailing list.  Let me see what I can remember...

First, more recent wxMac cvs snapshots have removed all requirements for resources.  So, this problem will have gone away.

Ah.  Found the problem in my mail trash.  There's a weird interaction between the DeRez program and the DISPLAY environment variable.  Is that variable set, or set improperly, for you?
Logged

bj575bd

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 21
Re: How to Compile for Mac
« Reply #21 on: April 19, 2005, 01:30:18 PM »
Thank you ken for your reply,
i'm at work now, but this night when i will be at home, i'll verify the display variable settings.
Logged
******************
Warbird

bj575bd

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 21
Re: How to Compile for Mac
« Reply #22 on: April 19, 2005, 09:05:36 PM »
The display variable is not set, what value should be present ?
Logged
******************
Warbird

ken

  • Hero Member
  • *****
  • Karma: 4
  • Offline Offline
  • Posts: 825
Re: How to Compile for Mac
« Reply #23 on: April 22, 2005, 02:22:02 AM »
Hmm.  If I remember the problem described on the mailing list, the problem was that the variable was set to something it shouldn't have been.  I think leaving it unset should be safe.

The problem also cropped up for people who logged into their Mac remotely with ssh to do the compile.  Were you doing that?  If so, you could try compiling when logged in at the Mac.  I think DeRez needs access to the display, which it can't normally get unless the user account running it is also logged in to the Mac GUI (and switched in, with respect to Fast User Switching).

Ultimately, you should probably just grab a more recent version of wxMac which doesn't use DeRez at all.  Version 2.6.0 was just released.
Logged

bj575bd

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 21
Re: How to Compile for Mac
« Reply #24 on: April 26, 2005, 01:16:30 PM »
Thank you Ken, the version 2.6.0 compile cleanly!
Logged
******************
Warbird

ken

  • Hero Member
  • *****
  • Karma: 4
  • Offline Offline
  • Posts: 825
Re: How to Compile for Mac
« Reply #25 on: April 26, 2005, 09:29:18 PM »
OK, good.  I'm glad you got it to work.  Enjoy!  :)
Logged

lionel77

  • Provider of Mac builds, Forum Mod
  • Hero Member
  • *****
  • Karma: 4
  • Offline Offline
  • Posts: 1107
  • Mac OS X 10.4 (Power Mac G5)
Re: How to Compile for Mac
« Reply #26 on: August 07, 2005, 10:29:51 PM »
Since the issues were getting rather specific I've moved DJ Nibu Aguiar's questions on how to install the DevTools and how to compile amule under 10.2 into a seperate thread: http://forum.amule.org/thread.php?threadid=7020
Logged
Current aMule CVS builds for OS X can be found here.

lillesvamp

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 8
Re: How to Compile for Mac
« Reply #27 on: July 01, 2007, 11:42:58 AM »
Just to be sure, I'll post this in this thread as well. With the latest cvs source, I get ./Scanner.l:191: error: 'yylex_destroy' was not declared in this scope.

OS X 10.4.10 , aMule-CVS-20070701, wxMac 2.8.4, flex 2.5.4
Logged

lionel77

  • Provider of Mac builds, Forum Mod
  • Hero Member
  • *****
  • Karma: 4
  • Offline Offline
  • Posts: 1107
  • Mac OS X 10.4 (Power Mac G5)
Re: How to Compile for Mac
« Reply #28 on: August 24, 2007, 09:09:07 AM »
I've updated the How to compile on Mac wiki page. I am using a slightly different setup myself, but I think the provided steps should work. It would be great if someone could provide some feedback.
Logged
Current aMule CVS builds for OS X can be found here.

eisa01

  • Full Member
  • ***
  • Karma: 0
  • Offline Offline
  • Posts: 100
Re: How to Compile for Mac
« Reply #29 on: August 24, 2007, 06:06:26 PM »
I followed the wiki, and it compiled fine as far as I can tell. Here's some feedback for making the guide even better:

The automake installed by Xcode works just fine (1.6.3), so it should be removed from the list of things you need to install.
Flex is also installed on my system, and I've never added it (2.5.4), I think it's included with Xcode. what's it used for?
Gettext is only needed if you want to build aMule with localisation support, right? That should be noted. I didn't need it.
The warning about Xcode 2.0 should really just be removed, and it should just state that you need at least 2.1, 2.4 preferably.
My configure status said it would use libgd to compile, is that a requirement? It's not stated anywhere at least.
I didn't have to add the special switch needed to run aMule CVS versions, so  that seems to be obsolete information.

I didn't make an Universal binary, so I didn't get to test that part out. The 45 minutes needed for a compile of wxMac is pretty much correct for my CPU, a 1.33 GHz G4. Didn't quite take the time on aMule itself, but I think it was between 20-30 minutes.
Logged
Pages: 1 [2] 3
« previous next »