MyBB Internal: One or more warnings occurred. Please contact your administrator for assistance.
MyBB Internal: One or more warnings occurred. Please contact your administrator for assistance.
MyBB Internal: One or more warnings occurred. Please contact your administrator for assistance.
MyBB Internal: One or more warnings occurred. Please contact your administrator for assistance.
Nightingale Forums - Compile instructions?

Nightingale Forums

Full Version: Compile instructions?
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Okay, admittedly I'm much of a noob when it comes to compiling in Linux. If I can't just ./configure and make and makeinstall, then I'm confused. I'd like to be able to test Nightingale, but I just can't seem to figure out how to compile the source.

It would be nice if someone made instructions for compiling Nightingale. Or maybe a virtual build environment could be provided?
Nevermind, I'm an idiot. I found these instructions:

http://wiki.songbirdnest.com/Developer/A...bird#Linux

Unfortunately I'm trying to compile on 64-bit, so every time I try to compile I get:

Code:
make -C /home/benjamin/ngale/branches/Nightingale1.8/compiled
make[1]: Entering directory `/home/benjamin/ngale/branches/Nightingale1.8/compiled'
/home/benjamin/ngale/branches/Nightingale1.8/build/config.mk:44: *** Please check out or build vendor-binaries - see https://wiki.songbirdnest.com/Developer/Articles/Getting_Started/Core_Player_Development/Checkout_the_Code#Get_the_Dependencies.  Stop.
make[1]: Leaving directory `/home/benjamin/ngale/branches/Nightingale1.8/compiled'
make: *** [build] Error 2

If I try getting the vendor source/[/code]binaries, http://publicsvn.songbirdnest.com/vendor...nux-x86_64, it just doesn't exist. I guess POTI has decided to get rid of 64-bit. Sad
I know I'm not the person to ask, but if you wait a while, someone who does know will answer you.
Hmmm... I can't answer this, but it does bring up a good point: Will Nightingale have 64-bit support, or will we be stuck with a 32-bit version until a 64-bit version gets built? Or, vis versa? I don't know much about the programming of a 32-bit vs a 64-bit system, so I'm not sure how difficult it would be...
(10-18-2010, 07:59 AM)pope_face Wrote: [ -> ]Hmmm... I can't answer this, but it does bring up a good point: Will Nightingale have 64-bit support, or will we be stuck with a 32-bit version until a 64-bit version gets built? Or, vis versa? I don't know much about the programming of a 32-bit vs a 64-bit system, so I'm not sure how difficult it would be...

If we have all the source code, theoretically it shouldn't be any problem compiling a 64-bit version. I think.
(10-19-2010, 03:21 AM)Mozenrath Wrote: [ -> ]
(10-18-2010, 07:59 AM)pope_face Wrote: [ -> ]Hmmm... I can't answer this, but it does bring up a good point: Will Nightingale have 64-bit support, or will we be stuck with a 32-bit version until a 64-bit version gets built? Or, vis versa? I don't know much about the programming of a 32-bit vs a 64-bit system, so I'm not sure how difficult it would be...

If we have all the source code, theoretically it shouldn't be any problem compiling a 64-bit version. I think.

The issue is that 64-bit Linux packages require a separate set of libraries and dependencies (unlike Windows where one package can be built for both 32 and 64-bit). As mentioned above, Songbird did have an SVN repo with all the 64-bit dependencies, but it got removed at some point and they now only build 32-bit nightlies. I would think that it would be much easier to just depend on packages already available to distros, but from memory Songbird were making modifications to some of the libraries they used. At the very least, it would be nice to have a list of the libraries that they WERE using, if just to be able to find alternatives. Dunno if there is anywhere with a log of what was in that now-absent Songbird repo though.
Nightingale should not use it's own libraries, that's huge overhead. Instead Nightingale should depend on standard system libraries. We're on Linux, folks! Wink
I agree completely, and that allows for easier portability to different distros. But we still need to know what libraries Songbird required on 64-bit Linux in the first place. This may be documented somewhere, I don't know - I'm not starting work on this until mid-November, so haven't looked around the code much.
The 64bit dependencies are the same as the i686, I have them and will be checking them into the Nightingale repository as soon as possible. Nightingale will have both 32bit and 64bit versions available.
The question of system library dependencies usage to inbuilt library dependencies still hangs...
To stevo, has that decision been made?
It's not really something that can just be decided - as I mentioned earlier, Songbird has patched many of the libraries it uses. Now, I know that, as an example, pinfold now includes in it's source many of the patches Songbird has, but not all of them. To use system libraries, we would need to go through them one by one, work out what the Songbird patches are, see if they are included in the latest library version, and if not either remove the need for the patch or persuade the library maintainers to include the patch. For some libraries this is feasible; for others we will have to keep using inbuilt versions.