aMule Forum
English => Compilation problems => Topic started by: Coronas on September 07, 2007, 09:26:12 PM
-
Hi all,
since 20070904, one can specify a --with-toolkit value, but as there seems to be no option for wxbase, configure stops with an error:
...
checking whether we need the GUI... no
checking for using IP2Country class...
checking for the --with-toolkit option... will be automatically detected
checking for the --with-wxshared option... will be automatically detected
checking for the --with-wxdebug option... will be automatically detected
checking for the --with-wxversion option... will be automatically detected
checking for wx-config... /home/tux/dreambox/root/cdkroot/bin/wx-config
checking for wxWidgets version >= 2.8.0 (--unicode=yes)... yes (version 2.8.5)
checking for wxWidgets static library... yes
checking if wxWidgets was built in DEBUG mode... no
checking if wxWidgets was built in STATIC mode... yes
checking which wxWidgets toolkit was selected... configure: error:
Cannot detect the currently installed wxWidgets port !
Please check your 'wx-config --cxxflags'...
make: *** [.amule] Fehler 1
Output from previous versions:
...
checking for using IP2Country class...
checking for wx-config... /home/tux/dreambox/root/cdkroot/bin/wx-config
checking for wxWidgets version >= 2.8.0... yes (version 2.8.5)
checking for wxWidgets static library... yes
checking that wxWidgets has support for large files... yes
checking that wxWidgets was compiled with unicode support... yes
checking whether to use embedded Crypto... yes
checking for bfd headers... cross-compilation detected, checking only the header
checking bfd.h usability... no
...
Output of wx-config --cxxflags
[tux@asus bin]$ ./wx-config --cxxflags
-I/lib/wx/include/powerpc-tuxbox-linux-gnu-base-unicode-release-static-2.8 -I/include/wx-2.8 -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D_LARGEFILE_SOURCE=1 -DwxUSE_GUI=0 -pthread
[tux@asus bin]$
-
Same problem here. I found a dirty workaround :
open amule configure file with your editor, go to line 8753 and make it look like this...
if test "$TOOLKIT" = "auto" ; then
# { echo "$as_me:$LINENO: checking which wxWidgets toolkit was selected" >&5
#echo $ECHO_N "checking which wxWidgets toolkit was selected... $ECHO_C" >&6; }
#
# WX_GTKPORT1=$(expr "$WX_SELECTEDCONFIG" : ".*gtk1.*")
# WX_GTKPORT2=$(expr "$WX_SELECTEDCONFIG" : ".*gtk2.*")
# WX_MSWPORT=$(expr "$WX_SELECTEDCONFIG" : ".*msw.*")
# WX_MOTIFPORT=$(expr "$WX_SELECTEDCONFIG" : ".*motif.*")
# WX_MACPORT=$(expr "$WX_SELECTEDCONFIG" : ".*mac.*")
# WX_X11PORT=$(expr "$WX_SELECTEDCONFIG" : ".*x11.*")
# WX_MGLPORT=$(expr "$WX_SELECTEDCONFIG" : ".*mgl.*")
# WX_DFBPORT=$(expr "$WX_SELECTEDCONFIG" : ".*dfb.*")
#
WX_PORT="gtk2"
# if test "$WX_GTKPORT1" != "0"; then WX_PORT="gtk1"; fi
# if test "$WX_GTKPORT2" != "0"; then WX_PORT="gtk2"; fi
# if test "$WX_MSWPORT" != "0"; then WX_PORT="msw"; fi
# if test "$WX_MOTIFPORT" != "0"; then WX_PORT="motif"; fi
# if test "$WX_MACPORT" != "0"; then WX_PORT="mac"; fi
# if test "$WX_X11PORT" != "0"; then WX_PORT="x11"; fi
# if test "$WX_MGLPORT" != "0"; then WX_PORT="mgl"; fi
# if test "$WX_DFBPORT" != "0"; then WX_PORT="dfb"; fi
#
#
# if test "$WX_PORT" = "unknown" ; then
# { { echo "$as_me:$LINENO: error:
# Cannot detect the currently installed wxWidgets port !
# Please check your 'wx-config --cxxflags'...
# " >&5
#echo "$as_me: error:
# Cannot detect the currently installed wxWidgets port !
# Please check your 'wx-config --cxxflags'...
# " >&2;}
# { (exit 1); exit 1; }; }
# fi
{ echo "$as_me:$LINENO: result: $WX_PORT" >&5
echo "${ECHO_T}$WX_PORT" >&6; }
else
In this way you're disabling the wx port check, pretending to have gtk2... amuled works fine :)
-
Thanks soulfire for your suggestion. Meanwhile I found some time to dig into the code as well. Anyway, I added the base in the list of valid toolkit-options, thus you can call configure with the argument --with-toolkit=base, and everyting works as it used to be. Here the diff:
diff -Naur amule-cvs.orig/configure amule-cvs/configure
--- amule-cvs.orig/configure 2007-09-13 06:01:13.000000000 +0100
+++ amule-cvs/configure 2007-09-13 20:05:12.714543250 +0100
@@ -7368,12 +7368,13 @@
if test "$TOOLKIT" != "gtk1" -a "$TOOLKIT" != "gtk2" -a \
"$TOOLKIT" != "msw" -a "$TOOLKIT" != "motif" -a \
"$TOOLKIT" != "x11" -a "$TOOLKIT" != "mac" -a \
- "$TOOLKIT" != "mgl" -a "$TOOLKIT" != "dfb" ; then
+ "$TOOLKIT" != "mgl" -a "$TOOLKIT" != "dfb" -a \
+ "$TOOLKIT" != "base" ; then
{ { echo "$as_me:$LINENO: error:
- Unrecognized option value (allowed values: auto, gtk1, gtk2, msw, motif, x11, mac, mgl, dfb)
+ Unrecognized option value (allowed values: auto, gtk1, gtk2, msw, motif, x11, mac, mgl, dfb, base)
" >&5
echo "$as_me: error:
- Unrecognized option value (allowed values: auto, gtk1, gtk2, msw, motif, x11, mac, mgl, dfb)
+ Unrecognized option value (allowed values: auto, gtk1, gtk2, msw, motif, x11, mac, mgl, dfb, base)
" >&2;}
{ (exit 1); exit 1; }; }
fi
Could any of the official developers have look at the patch, please?
-
I've committed your fix, thanks a lot.
-
Merci :)