logo

Δ All posts

Museek+ client working on OS X Leopard (Howto)

1 February 2008

What is Museek (plus)?

Museek plus is a Soulseek client. It is far superior to other products available on OS X in terms of usability, coherence, and ability to specify preferences. Read more on the site. Unfortunately, its a bit difficult to get working on OS X because its native to Linux. Nevertheless, it can be done (and is well worth it.

Installing: a bit of a pain

With the help of Daelstorm I was able to get Museek working on my MacBook (intel), Leopard (OS X v 10.5). This should be a great relief to any Mac Users still stuck in using Nicotine, or god forbid SolarSeek--I'd rather use BearShare!! (oh, p2p humor... meh.)

Museeq (client)

So here goes:

Firstly, get X11 / MacPorts/ XCode Tools installed on your machine. Takes a while. A long while.

Then run sudo port install qt3 in an X11 terminal.

Also, get Fink installed. At the time of this writing I had to use this build but that will probably change, as Leopard apps are in rapid development all over.

You're going to have to add the fink stuff to your PATH (.bash_profile file) so you can run its packages from the command line. I believe I was prompted, at the end of the install, to run a little shell script which added the appropriate lines. At any rate, my .bash_profile looks like:

yeagos-magic-machine:museeq y$ cat ~/.bash_profile export PATH=${PATH}:~/Programming/tools #You don't need this line export PATH=${PATH}:/usr/local/bin export PATH=${PATH}:/opt/local/bin export PATH=${PATH}:/opt/local/sbin test -r /sw/bin/init.sh && . /sw/bin/init.sh

I hear the order of the things above counts, but I can't tell you why.

Also, get the latest version of Museek. And glance over this page because you're going to have to install a few more things mentioned there.

Daelstorm mentioned a Museeq QT4 port but I didn't do that.

Now, we will be using the SCons method to build this program with the following command scons QTDIR=/opt/local/lib/qt3 from the folder created by the Museeq tarball you downloaded earlier, pointing to the installation of QT3 you (hopefully) already installed. Oh, and get scons! (fink install scons)

This will probably fail due to missing dependencies. I got choked up on 'libxml++2' and 'vorbisfile'. That's where fink came in handy with fink install libxml++2 and fink install vorbistools libvorbis0 libvorbis0-shlibs (I'm honestly not sure which of these applied to my situation. Try them one at a time if you feel so inclined (and let me know >=] )

Anyway, I got myself into serious trouble at this point.

I started getting errors related to the trayicons one | two

running scons with MUSEEQTRAYICON=no and 0 did not help.

Daelstorm came up with a fix: edit /museeq/SConscript and remove the line "trayicon.cpp" Don't do this if you are stuck at something that has nothing to do with trayicon / trayicon.o.

Once I did this everything worked fine and I got the wonderful message from scons "done building targets". When this works, you've got a working installation of Museek, except its in the /workdir. To build a global copy at this point you simply go sudo scons install QTDIR=/opt/local/lib/qt3 MUSEEQTRAYICON=0 from the /originalMuseeqTarball/museeq directory and, viola, you have a working copy of Museeq!

If you had the trayicon problem, simply select a theme and restart X11 and your icons are fine!

Museekd (daemon)

Installs as described in INSTALL.scons

Comments

1 rubyinthedust says...

Good work! I tried this last year on Tiger and got it built but for some reason the window was stuck in the background and I couldn't bring it up, however the deamon and connection worked properly.

So I'm atempting again on a black MacBook (with QT4!) exactly for the reasons you mentioned - Nicotine, SolarSeek and soulseeX!

Well, I'm off to a great start, I can't get fink installed - curl appears to be broken and times out while trying to download packages. You didn't have this problem?

Posted at 10:29 p.m. on March 10, 2008

2 Yeago says...

Not sure why you can't get fink installed.... you tried the link I gave and it choked?

Posted at 10:31 p.m. on March 10, 2008

3 rubyinthedust says...

Fink is up. I got wget from MacPorts but needed to rename curl to force finks usage of wget.

Qt4 looks good, however museeq Qt4 is doesn't build with SCons and I'm having a time with it, so I think I have to find daelstorm and get some hints. Did he mention anything in particular about the Qt4 port or even encourage you to test it?

Another question, why did you install all the vorbis stuff?

Posted at 10:45 a.m. on March 20, 2008

4 Yeago says...

As you can see I used QT3.... I think it was because QT4 wouldn't work so well but maybe that's changed. I encourage you to find out (and to return with your results!)

I installed the vorbis stuff because they were depended on by other libraries and were choking.

Posted at 4:05 p.m. on March 20, 2008

5 butbut says...

what about soulseeX?

Posted at 8:16 p.m. on April 1, 2008

6 Yeago says...

What about soulseex? Its Abandonware.

It hasn't been updated since 2005 and only builds on PPC.

Posted at 10:11 p.m. on April 1, 2008

7 rubyinthedust says...

soulseeX is probably the most confusing/irritating app I've seen on any platform!

I still haven't gotten past qmake for Qt4 and haven't seen daelstorm around either, but I'll be sure to let you know when I've made an advance...

Posted at 11:39 p.m. on April 1, 2008

8 butbut says...

i hadn't tried it up until yesterday and was amazed how well it worked (though it's gui is really something). it sure is abondonware, but alot better than solarseek at this point (which is probably also becoming abandonware). and there is a universal binary available here: http://chris.schleifer.net/ssX/builds/ssX-06082006-2216.dmg get the latest build. i prefer it to museek.

Posted at 10:59 a.m. on April 2, 2008

9 Yeago says...

@butbut. I think you mean 'you prefer it to solarseek' =).

Its another thing to check out for those desperate, for sure. Neat that it works on intel. But slsk's most recent client has abandoned that server entirely in favor of a newer one. I'm going to keep trying museek =)

@rubyinthedust -- he's typically in the museek room later at night Eastern time. Maybe if we get this working we create a package installer for it? Also, you should show me how QT4 dies. Here's the <a href='/_files/daelstorm-museek-chat.html' rel="nofollow">soulseek chat log</a> with daelstorm I had--he has plenty to say about QT4. I never had a problem installing it.

Posted at 4:17 p.m. on April 2, 2008

10 butbut says...

what do you mean by this: "But slsk’s most recent client has abandoned that server entirely in favor of a newer one." ?

Posted at 11:07 p.m. on April 2, 2008

11 Yeago says...

If you look at the release notes of the last windows build it mentions a new server.

Posted at 11:53 p.m. on April 2, 2008

12 Jason says...

Thanks for the write up. After several grueling attempts I finally got it built. This slightly embarrassing question needs to be asked. How on earth do I start the application? How do I run it, where is it located?

Posted at 4:20 a.m. on April 29, 2008

13 Yeago says...

Well, did you get the daemon running? You run the daemon and then run museeq in X11 and you're set.

Posted at 9:23 p.m. on April 30, 2008

14 Jason says...

ok, I figured a couple of things out and seem to have it running, but now I cannot connect to the daemon.

  • am I supposed connect to "localhost:2240"?
  • If yes, do I use root password, user, or slsk account?

I am getting : "got login attempted SHA1" which I think a failure. Museeq is saying "Login error: INVPASS"

Posted at 12:03 a.m. on May 1, 2008

15 Yeago says...

Try creating new account instead?

You use your slsk account.

Posted at 12:18 a.m. on May 1, 2008

16 Jason says...

Holy crap! I got it working. I guess I need to set up my interface password. Yeago, thanks.

Would you mind if I used your instructions and added my own on my personal blog? There is nothing on my blog yet and I would like this to be the first entry. I also want to cite your instructions as a source for my instructions.

Posted at 12:30 a.m. on May 1, 2008

17 Yeago says...

Please do. Also, please make sure to mention what machine and version you're running. I haven't got it working perfectly yet (there are many odd bugs in the GUI). And link here so I can read. =)

Posted at 12:34 a.m. on May 1, 2008

18 mya says...

Hi.

I had xcode and x11 installed and downloaded macports. Created a .bash_profile file in ~ and the bash knows the port command now.

Unfortunately X11 doesn't. So "sudo port install qt3 " in the x11 Terminal just won't work (command not found error).

What I checked so far: x11 and x11 sdk have been installed, xcode has been reinstalled, there are no folders or files like X11/xinit/xinitrc in /etc/ present.

Anyone any advise? Thank you. :-)

mya

Posted at 11:56 a.m. on May 19, 2008

19 Yeago says...

If the command is choking at sudo, you've got something insanely wrong with your system. If its port (which I think you meant) then... hmm. Well I'm sure you've tried it but closing and opening the terminal is necessary.

Posted at 12:33 p.m. on May 19, 2008

20 mya says...

Hi.

I don't want to blow up this comment section, but just to reconfirm two things:

  1. the "sudo port install qt3" has to be executed in the X11 Terminal, not the OSX bash?

  2. Do you have the folders /etc/X11/xinit/xinitrc? (I don't have them, besides /etc I mean ;-) )

It's indeed the "sudo: port: command not found" error I get. (only in the X11 Terminal, the OSX Terminal knows the "port" command now)

BTW: afaik there is a confirmed bug at the installation of macports in Leopard. You have to edit the .bash_profile yourself or the OSX bash won't know the "port" command. It's pretty funny that you didn't encounter this problem.

Thx. for your help

mya

Posted at 3:24 p.m. on May 19, 2008

21 Yeago says...

I think I did encounter that bug, I just edited the bash_profile. I think the port command can be issued in regular bash. I could (and am probably) wrong but I think X11 is only used for the graphical aspects of these programs.

When I get home I'll inspect my setup, if you are still having problems.

PS: Don't worry about commenting here.

Posted at 3:30 p.m. on May 19, 2008

22 mya says...

Hi.

I'm still trying to get Museek to run.

As I mentioned before the X11 bash doesn't know the "port" or "scons" commands, so everything I do is in the OSX Shell.

BTW: The correct command is: fink install vorbis-tools libvorbis0 libvorbis0-shlibs I'm seriously wondering how you got it installed with the commands you are using above... ;-)

Anyway:

Trying to do this : "scons QTDIR=/opt/local/lib/qt3"

Results in this error: (I cut out a few hundred unnecessary lines) ;-)

Any idea what might have went wrong or what else to install?

Thank you Mya

MBA:museek+-0.1.13 m$ scons QTDIR=/opt/local/lib/qt3 scons: Reading SConscript files ... Using SCons version 0.97.0d20071212 Reading FLAGS from defaults.py and Command Line arguments BUILDING with CCFLAGS: -fPIC -Wall -pipe -g Checking for header file stdio.h... yes

I made a cut here : bla bla bla

Checking for C++ type uint32... no Compiling Muhelp, Mucipher, Museekal, Museek, Tools, museekd, doc, python-bindings, setup, python-clients and Mucous... and Murmur... and Museeq... Headers/Dependencies for Muhelp... Checking for libxml++... libxml++-2.6 Checking for C++ header file libxml++/libxml++.h... yes

Headers/Dependencies for Mucipher... WARNING: PyMucipher disabled, NOT building Python bindings for mucipher. Enable with: PYMUCIPHER=0 Looking for replacement (PyCrypto)... PyCrypto is not available, maybe you should install it?: No module named Crypto

Headers/Dependencies for Museekal... Checking for setsockopt() in C library socket... no Checking for gethostent() in C library nsl... no

Headers/Dependencies for Museek... Checking for inflate(0, Z_FINISH) in C++ library z... yes

Headers/Dependencies for Tools... Checking for ov_clear(0) in C++ library ... yes OGG Vorbis found, compiling into muscan. * muscan will be installed Checking for FAMOpen2(0,0) in C++ library fam... no

RuntimeError: maximum recursion depth exceeded: File "/Users/m/Downloads/museekya/museek+-0.1.13/SConstruct", line 381: SConscript(os.path.join(dir, 'SConscript'), build_dir = bd, duplicate = 1) File "/sw/lib/scons-0.97.0d20071212/SCons/Script/SConscript.py", line 596: return apply(method, args, kw) File "/sw/lib/scons-0.97.0d20071212/SCons/Script/SConscript.py", line 533: return apply(_SConscript, [self.fs,] + files, subst_kw) File "/sw/lib/scons-0.97.0d20071212/SCons/Script/SConscript.py", line 256: exec file in call_stack[-1].globals File "/Users/m/Downloads/museekya/museek+-0.1.13/workdir/museekd/SConscript", line 21: install = env_museekd.Install(env['DESTDIR'] + env['BINDIR'], [museekd]) File "/sw/lib/scons-0.97.0d20071212/SCons/Environment.py", line 178: return apply(self.method, nargs, kwargs) File "/sw/lib/scons-0.97.0d20071212/SCons/Tool/init.py", line 468: return apply(builder, args, kw) File "/sw/lib/scons-0.97.0d20071212/SCons/Environment.py", line 178: return apply(self.method, nargs, kwargs) File "/sw/lib/scons-0.97.0d20071212/SCons/Tool/init.py", line 468: return apply(builder, args, kw) File "/sw/lib/scons-0.97.0d20071212/SCons/Environment.py", line 178: return apply(self.method, nargs, kwargs) File "/sw/lib/scons-0.97.0d20071212/SCons/Tool/init.py", line 468: return apply(builder, args, kw) File "/sw/lib/scons-0.97.0d20071212/SCons/Environment.py", line 178: return apply(self.method, nargs, kwargs) File "/sw/lib/scons-0.97.0d20071212/SCons/Tool/init.py", line 468: return apply(builder, args, kw) File "/sw/lib/scons-0.97.0d20071212/SCons/Environment.py", line 178: return apply(self.method, nargs, kwargs) File "/sw/lib/scons-0.97.0d20071212/SCons/Tool/init.py", line 468: return apply(builder, args, kw) File "/sw/lib/scons-0.97.0d20071212/SCons/Environment.py", line 178:

I made a cut here : bla bla bla few hundred error lines ;-)

Posted at 6:51 a.m. on May 21, 2008

23 LHisnotBCN says...

when i try to put:

yeagos-magic-machine:museeq y$ cat ~/.bash_profile export PATH=${PATH}:~/Programming/tools #You don’t need this line export PATH=${PATH}:/usr/local/bin export PATH=${PATH}:/opt/local/bin export PATH=${PATH}:/opt/local/sbin test -r /sw/bin/init.sh &amp;&amp; . /sw/bin/init.sh

results in this error: museeq y$ cat ~/.bash_profile -bash: museeq: command not found

Posted at 5:09 p.m. on July 25, 2008

24 pau pau says...

I have the same problem as mya... i cant get the sudo run on X11... any idea? thanks pau pau

Posted at 8:23 p.m. on August 29, 2008

25 rubyinthedust says...

sudo doesn't work on a passwordless account - OSX lets you do this. If this is the case you'll need to add a password to your account.

Posted at 6:29 p.m. on September 4, 2008

26 rubyinthedust says...

I gave up for the moment. I had to reinstall OSX and lost some of my dependencies. I'm not really interested in spending time to get Qt3 apps to run and the Museek+ site says there is a new rewrite with Qt4 coming...

Posted at 6:41 p.m. on September 4, 2008

just realized how annoying linking twitter to facebook would make him on facebook. UNDO.

...twittered about 5 days ago

Latest projects