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 - How to build Nightingale

Nightingale Forums

Full Version: How to build Nightingale
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Quote:the guy with the username made of gibberish
is now for the third time registered here, and finally manages to post something somewhere else than IRC:

Quote:nightingale-1.8 branch:
First off, build.sh should work on Windows building with msys, provided you have it setup correctly, but it may not.
About the setup I use to build, there are two important things to be aware of:
First, the build system will fail to build anything if you use the "normal" Linux version of Nightingale.config. You must specify
Code:
ac_add_options --with-media-core=default
because we don't have gstreamer libs in a "normal" Windows environment.
Second thing is an issue with the output folders. I'm not quite sure what causes the behaviour, but because we'll change to 1.10 this issue is not that important now: there are two compiled folders ("compiled-release-" and "compiled-release-i686"), you need to junction one to the other one in order to get a correct build.
After those steps, the build is not completed yet, the gstreamer stuff is broken.
Copy libs and gst-plugins from the Songbird 1.8.0 release into the "compiled-release-i686/dist folder". After that, you can run "compiled-release-i686/dist/nightingale.exe".
As long as we have your working copy, I figure we'll be good until 1.10.
(10-17-2011, 12:57 AM)Timmythepirate Wrote: [ -> ]
Quote:Thanks, here are the last few lines.


## ----------- ##
## confdefs.h. ##
## ----------- ##

/* confdefs.h */
#define PACKAGE_NAME ""
#define PACKAGE_TARNAME ""
#define PACKAGE_VERSION ""
#define PACKAGE_STRING ""
#define PACKAGE_BUGREPORT ""
#define PACKAGE_URL ""
#define NDEBUG 1
#define XP_UNIX 1
#define _REENTRANT 1

configure: exit 1

What folder is confdefs.h in? Also I think there might be a bug in the latest source because I can't get it to compile correctly, but I'm trying to test the (working) source on as many distro's as I can to see if it works. If you want to tell me your distro and architecture, I'll see if I can figure out what's going on.

I'm trying to build on Ubuntu 10.04 (cann't upgrade that easy due to issues with newer kernals). The machine is a toshiba A40 satelite laptop 32bit (pre 64bit). Unfortuantely I'm not sure where condefs.h is (currently on my fedora machine.

Thanks
(10-18-2011, 06:01 AM)nighthawk Wrote: [ -> ]
(10-17-2011, 12:57 AM)Timmythepirate Wrote: [ -> ]
Quote:Thanks, here are the last few lines.


## ----------- ##
## confdefs.h. ##
## ----------- ##

/* confdefs.h */
#define PACKAGE_NAME ""
#define PACKAGE_TARNAME ""
#define PACKAGE_VERSION ""
#define PACKAGE_STRING ""
#define PACKAGE_BUGREPORT ""
#define PACKAGE_URL ""
#define NDEBUG 1
#define XP_UNIX 1
#define _REENTRANT 1

configure: exit 1

What folder is confdefs.h in? Also I think there might be a bug in the latest source because I can't get it to compile correctly, but I'm trying to test the (working) source on as many distro's as I can to see if it works. If you want to tell me your distro and architecture, I'll see if I can figure out what's going on.

I'm trying to build on Ubuntu 10.04 (cann't upgrade that easy due to issues with newer kernals). The machine is a toshiba A40 satelite laptop 32bit (pre 64bit). Unfortuantely I'm not sure where condefs.h is (currently on my fedora machine.

Thanks
It should work on Ubuntu, I posted a tutorial that should help.


It should work on Ubuntu, I posted a tutorial that should help.


Unfortunately I had issues with git (no package found) although I have it installed. So I'm going to wait till a package is released before I continue. Got further with Fedora so will concentrate on that instead.

Thanks for trying to help.

EDIT. I can now conform that Nightingale works in Fedora 15. I based my install on the Ubuntu instructions but had to change step 5 to-

yum install gstreamer-plugins-base-devel gstreamer-devel gtk2-devel dbus-glib-devel hal-devel

There was another which I had to install because it was found to be missing but forgot to write it down (sorry), but this will be brought to your attention after the final instruction is run. :-)
So, on Ubuntu all the build script problems that I've encountered seem to stem from the syntax of the lines that mention dependencies. I've found that if you comment out all the lines that mention dependencies and manually download the dependencies there doesn't seem to be any problems. But, I wonder is there anyway to "rephrase" the dependency lines because on line 18 I get the error:
Code:
build.sh: 18: Syntax error: "(" unexpected (expecting ";;")

I don't know why Ubuntu can't understand this line, but is there a way to change this line and subsequent lines to make it understandable to Ubuntu.
Try adding a semicolon after the array dependencies=();

if that doesn't work, try putting each dependency in apostrophies and try that

dependencies=('asdf' 'asdfadfasdf')

This is why I don't use ubuntu.
So, I've gotten a 32-bit binary built in Ubuntu to work in both Ubuntu and Debian. I assume it should run well in all 32-bit Debian-based distros. However, Fedora, tells me that there are corrupted library files (gstreamer library files, I guess?). So, I wonder would we have to make separate builds for different Linux distros or is there some sort of patch that could be applied to a binary build that would prevent any issue with the location of where gstreamer files are kept.
No, no no.

It's the distros' responsibility to package it themselves. We'll just be releasing tarballs like songbird does.

You can volunteer to make them for a distro, and we'll host them, but generally unless you become the package maintainer, it's not our responsibility to build it for distros.

Anyway, for debian distros it'd be better if you'd setup a PPA repo on launchpad...but I personally am not maintaining packages for any distro, unless Archlinux decides to include nightingale...you can for deb/ubuntu if you'd like, but our releases will just be tarballs.
(10-31-2011, 09:59 AM)ilikenwf Wrote: [ -> ]No, no no.

It's the distros' responsibility to package it themselves. We'll just be releasing tarballs like songbird does.

You can volunteer to make them for a distro, and we'll host them, but generally unless you become the package maintainer, it's not our responsibility to build it for distros.

Anyway, for debian distros it'd be better if you'd setup a PPA repo on launchpad...but I personally am not maintaining packages for any distro, unless Archlinux decides to include nightingale...you can for deb/ubuntu if you'd like, but our releases will just be tarballs.

I understand that we will just do tarballs, but I'm having trouble getting a binary tarball to work in all 32-bit Linux distros.
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15