[ilikenwf]

It's not ready yet, it's still baking I'm upgrading it to use xulrunner 6.0 and this thread does not in the least bit apply to it whatsoever.

[ilikenwf]

If you want, pull down the nightingale-1.8 branch from my git tree, and run build.sh. That SHOULD work as long as you're running linux.

You could (for faster downloading) just get the tarball: https://github.com/ilikenwf/nightingale-...ingale-1.8

The git tree is here:
https://github.com/ilikenwf/nightingale-...ingale-1.8

But I'd like to have other people try this one, so that I can make sure it builds well on everyone's distro/architecture.

Notes:
*To build, you need to have all of the gstreamer0.10 packages for your distro, svn, wget, and git (if pulling the tree down) installed, as well as the usual dependencies for building software upon your distro.

*If it gets python errors, make sure you have python2 installed, and try the build.sh script again.

*If it doesn't play music, you'll need to copy /usr/lib/gstreamer0.10/* into compiled-dist-linux-[your arch]/dist/gst-plugins and then rerun nightingale. It should then play music.

[Ezekiel000]

I had a go at compiling nightingale 1.8 a few comments before I started:
- build.sh is not set to executable.
- it is probably better to list subversion rather than svn as a requirement.
I'm building on Debian Wheezy/testing/7.0 amd64

I had to install a few packages I didn't already have installed like libdbus-glib-1-dev & libgstreamer-plugins-base0.10-dev. Nightingale compiled fine after installing missing packages but I did have to copy the files from:
/usr/lib/gstreamer-0.10/ (not /usr/lib/gstreamer0.10/) to gst-plugins to get it to play music.

If the current version needs the files in gst-plugins why not add symbolic links in the compile process?

Edit: I decided to test if nightingale would accept a symlink, which it did. I created a symlink with this in the compiled dist folder:
ln --symbolic /usr/lib/gstreamer-0.10/ gst-plugins

[Timmythepirate]

The 1.8 build builds and works perfectly on LMDE 64-bit. No symbolic links were necessary.

[ilikenwf]

(09-27-2011, 08:27 AM)Timmythepirate Wrote: The 1.8 build builds and works perfectly on LMDE 64-bit. No symbolic links were necessary.

I just fixed the gstreamer library locations thing, as well as making build.sh executable. You shouldn't need to symlink anymore, but if you do, please let me know the path for your gstreamer libs directory.

[ilikenwf]

Okies, the gstreamer stuff SHOULD be permanently fixed. For some reason, songbird isn't always locating the gstreamer libs, so I automatically add code to the launcher after the build, which will automatically locate the gstreamer libs on each launch.

[Ezekiel000]

With the latest commits Nightingale 1.8 compiled and worked fine.

The debian / ubuntu specific packages that you added to the readme based on my comments above are not a full list of non-default packages that need to be installed as I already had a load of dev packages installed to compile other programs. I just installed packages as and when the build process said it couldn't find things.

[ilikenwf]

We'll have to figure those out eventually, the less adept at building will complain if we don't.

[Timmythepirate]

I managed to port geekshadow's modified version of purplerain to Nightingale. I managed to incorporate it into ilikenwf's source code, but the latest source wouldn't build and I didn't have the original tarball on hand so the source file is really big but it builds correctly on LMDE x64. If anyone wants to take a look, feel free.

https://github.com/Timmythepirate/Nighti....8_2011.10

[ilikenwf]

Yeah, the master branch won't be ready for 2-3 more weeks I figure.

Provided it builds on my end I'll push the skin to the nightingale-1.8 branch, since it's currently our "stable" version...

We need to start thinking about extensions and compatibility too...not sure we should worry with it on ngale 1.8, but for 1.10 i was thinking about continuing to use the songbird namespace so that songbird extensions and skins will be easier to port - we'll just have to make sure they work with xulrunner 6+.