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]

Author Topic: change incoming folder  (Read 7245 times)

sulliwane

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 15
Re: change incoming folder
« Reply #15 on: June 23, 2010, 10:56:04 PM »

thanks a lot for your reply...

i downloaded and installed these .deb and their depedencies,

so it's better now, i got a new error :

Code: [Select]
checking which wxWidgets toolkit was selected... base
configure: error:
                The selected components need a wxWidgets library with GUI,
                but your installation is base-only.  Please install a GUI
                enabled version of wxWidgets and then retry.

 i work on a ubuntu server edition...i have no screen. is a GUI really usefull ? and so, how solve this new error message ?
Logged

Kry

  • Ex-developer
  • Retired admin
  • Hero Member
  • *****
  • Karma: -665
  • Offline Offline
  • Posts: 5795
Re: change incoming folder
« Reply #16 on: June 23, 2010, 11:05:21 PM »

In aMule's configure, disable everything that requires a GUI (this includes wxCas, etc). Most probably you only want amuled, amuleweb and amulecmd in your server.
Logged

sulliwane

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 15
Re: change incoming folder
« Reply #17 on: June 23, 2010, 11:12:47 PM »

hi,

i understand the aim of disabling everything that requires a GUI...but i just opened the file "configure" and there is a huge number of line....

do you really think it's possible to "disable everything that requires a GUI" ?? without spending 2 hours on the configure file ...? (where is wxcas, what do you mean by "etc", how to disable all of that...)

i'm really noob and think maybe it's easier to compile everything, and after disable amule and just let amuled running.

what do you think ? If so, how install WxWidget library with GUI ?

thanks
victor
« Last Edit: June 23, 2010, 11:19:59 PM by sulliwane »
Logged

Kry

  • Ex-developer
  • Retired admin
  • Hero Member
  • *****
  • Karma: -665
  • Offline Offline
  • Posts: 5795
Re: change incoming folder
« Reply #18 on: June 24, 2010, 01:13:47 AM »

When you run ./configure, you are telling the configure script to use the defaults for all values.

If you run "./configure --help" (without the quotes, of course), you will see a lot of options to fine-tune your aMule compilation. This is true for most applications you compile, not just aMule.

The important ones for you right now are:
Code: [Select]
 --disable-monolithic    disable building of the monolithic aMule app
  --enable-amule-daemon   compile aMule daemon version
  --enable-amulecmd       compile aMule command line client
  --enable-webserver      compile aMule WebServer
  --enable-amule-gui      compile aMule remote GUI (EXPERIMENTAL)
  --enable-cas            compile C aMule Statistics
  --enable-wxcas          compile aMule GUI Statistics
  --disable-ed2k          don't compile aMule ed2k links handler
  --enable-alc            compile aMuleLinkCreator GUI version
  --enable-alcc           compile aMuleLinkCreator for console
  --enable-xas            install xas XChat2 plugin
  --enable-fileview       compile aMule file viewer for console (EXPERIMENTAL)
  --enable-plasmamule     compile aMule plasma applet and engine

Now, those are the defaults. For example, aMule monolithic (full aMule) is enabled by default. You want to disable anything that needs a GUI, and only leave what you want. In your case,

Code: [Select]
./configure --disable-monolithic --enable-amule-daemon --enable-webserver

should disable the only GUI thing enabled by default (aMule) and enable amuled and amuleweb. You can add "--enable-amulecmd" if you want to that line. Everything else is disabled by default except ed2k, which is  a small app used for link handling and it doesn't matter much if you compile it or not in your server.
Logged

sulliwane

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 15
Re: change incoming folder
« Reply #19 on: June 25, 2010, 12:30:39 AM »

Hi kry,

thank you for your reply  (very clear !)

i'd like everything would work perfectly this time...but i encounter a new problem  (very sorry with all that trouble  >:(

Code: [Select]
checking for libupnp version >= 1.6.6... no (try to use --with-libupnp-prefix=PREFIX)
configure: WARNING:
        UPnP code has been disabled because libupnp >= 1.6.6 not found (try to use --with-libupnp-prefix=PREFIX).
checking for crypto++ version >= 5.1... no
configure: error:
        Could not find crypto++ header file "cryptlib.h".
        Please try again with --with-crypto-prefix=/my_crypto_prefix
        (replace /my_crypto_prefix with a valid path to your crypto++
        installation directory).

i don't find the file the error message is dealing with  (cryptlib.h)

Should i add a magic option to ./configure   ??

thank you again,

victor


[edit]  solve with

Code: [Select]
apt-get install libcrypto++-dev
that's it :o)
« Last Edit: June 25, 2010, 12:49:43 AM by sulliwane »
Logged

sulliwane

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 15
Re: change incoming folder
« Reply #20 on: June 25, 2010, 01:05:48 AM »

then
Code: [Select]
makethen
Code: [Select]
checkinstall
and it has failed to install the debian package compiled before....

is libupnp required ? i'm going to give up....don't uderstand why it failed, and only if someone wants it, i can post the bug report.

thank you all for your reply,

bye

victor
Logged

^marcell^

  • Developer
  • Hero Member
  • *****
  • Karma: 28
  • Offline Offline
  • Posts: 524
Re: change incoming folder
« Reply #21 on: June 25, 2010, 03:47:30 PM »

is libupnp required ? i'm going to give up....don't uderstand why it failed, and only if someone wants it, i can post the bug report.
Add --disable-upnp as parameter when calling "./configure" so the UPNP code will not be compiled.
Logged
Pages: 1 [2]