museekd, and the clients, like Museeq. This means you can run museekd on one box on your network and run several instances of museeq or mucous from other computers on the network all using the same Soulseek ID.musetup spit
an error at me?040714.040528) needs a
config.xml file in ~/.museekd/~/.museekd/ directory and run
museekd.mkdir ~/.museekdtouch ~/.museekd/config.xmlmuseekdctrl-cmusetupmusetup and setup up shared directories.musetup. (musetup->3->1)museeq.museeq client, add
your Ethernet IP to interfaces listeners in musetup. (musetup->3->2->1)museekd with the same config, because they will
constantly disconnect each other due to using same soulseek
username unless you're using museek+ >= 0.1.4.PORTDIR_OVERLAY directory (usually /usr/local/portage, set in /etc/make.conf). emerge qsa and use the following command:
USE="qsa" emerge museekUSE="-qt" emerge museekemerge museekscons/scons.py (from the museek directory). If you are using svn version, you'll need to install scons yourself.Scons *** No tool named 'qt':
No module named qt
/opt/qt /usr/share/qt3 /usr/qt/qt3 /usr/share/qt3/include/qt.h:260:21:
qvfbhdr.h: No such file or directory you can try something
very evil.../usr/include/qt3/qt.h and comment
// out the line containing #include
<qvfbhdr.h>Checking for C++ header file qapplication.h... no
you'll need to set your QTDIR manually.scons QT_LIB=qt-mt QTDIR=/usr/share/qt3include directory or symlink to /usr/include/qt3 (Debian) in $QTDIR /usr/X11R6 (can someone verify that this works?)emerge qsa./configure --prefix=/usr; make; su -c
"make install"export
PKG_CONFIG_PATH="/usr/local/lib/pkgconfig:$PKG_CONFIG_PATH"emerge libxmlppapt-get install libxml++1.0 libxml++1.0-devpacman -S libxml++gcc (g++) or some other C++ compiler is
installed.config.log file in the museek build directory for detailed information about your error.
museekd was compiled with EPOLL enabled)-fPIC to your CCFLAGS. env.Append(CCFLAGS = ['-Wall', '-pipe'])env.Append(CCFLAGS = ['-fPIC', '-Wall', '-pipe' ]) (in this order) (thanks, loox)