Linux build.sh script

[althekiller]

ANNOUNCEMENT build.sh is no longer supported and will soon be removed from SVN. Please see README.linux for build instructions.



As of SVN revision 9884 of linuxbranch the new build script I've authored is in the repository. Pike has modified the README.linux to briefly explain its usage, SO READ IT.

Here is a full list of available options...

$ ./build.sh --help
build.sh by default checks that your source is up-to-date, updates it
if not, compile, and create a working build of XBMC in ./BUILD.
UserData and scripts dirs will be backed up if existing.
Usage: build.sh [OPTIONS]
OPTIONS:
--help [-h] : Display this text.
DEST=<build-dest> : Path to install XBMC to
NOUPDATE : Don't update source.
NOCOMPILE : Don't compile.
NOCLEAN : Don't run "make clean" first.
NOCOPY : Don't create XBMC file structure.
CONFIRM : Don't ask about anything
CONFIGOPT=<config-option> : Option to pass to configure.
One option per CONFIGOPT=,
can pass more than one
WEB=<path/to/web_int.rar> : Web interface to use.
Default = PM3
These options can be defaulted in ~/.xbmc-build-settings.
Just make a white space separated list on the first line.


The script's intent is to go from a checked out SVN to a full build with out the need of an xbox T3CH release or knowing all the little case sensitivity issues that are still lurking in the linux port. It will even do nice things like back up your UserData, scripts and thirdparty skin folders for you so you don't have to toy with them on each new build. The intent of this script is NOT to enable the linux illiterate to compile the linux port (though unfortunately it does). Keep in mind that as of now there is no end-user support for linux and we really don't care to here about problems you may find unless you are willing and able to help us track them down.

Please post bug reports and feature requests here or in #xbmc-linux on FreeNode.

Enjoy :)

EDIT:
Forgot to give a shout out to Pike, dragon788, staz and the rest of #xbmc-linux for testing. Thanks guys.

[pike]

tis a nice script ™

[dragon_788]

Agreed pike, its great for assisting with a quick compile rather than making crazy symlinks all over the place (which is still somewhat necessary in Gentoo anyways).

[erlis]

I totally agree, it's a nice script. However it together with README.linux does not mention that the XBMC_HOME variable must be set to the correct path (mostly ~/XBMC/BUILD)

[spiff]

simply because it aint so. if the var isnt set it uses the dir the executable is in

[pike]

readme says to CD into your "BUILD" folder and run it from there, and if you follow directions everything works as advertised lulz

[gateway69]

I'm wondering if someone could fix the script for nvidia/7.10 systems.

When you use envy to install your nvidia drivers it installs the llzo2-dev, which then when compiling crashes out unless you make a change to your Make file and swap -llzo to -llzo2 in the make file, run make, and then build.sh NOCOMPILE to install the latest build into your BUILD folder.

[Redhound]

This is not a problem in de build.sh script. It needs to be fixed in the configure.in script.

[Gamester17]

http://xboxmediacenter.com/wiki/index.php?title=HOW-TO_submit_a_patch

Patch welcomed :;):

[gateway69]

Wish I was skilled enough to do a patch, you guys deff dont want me going in and coding stuff :) im more of the person that hammers on the software and fines bugs and stuff.

[rodalpho]

Pike, any chance of adding the -jx argument to build.sh to automatically use multiple cores to compile?

[pike]

rodalpho, this should be taken care of automagically by build script, works fine here, not for you ?

[rodalpho]

Oh it does? I actually hadn't checked, I assumed it didn't since there was no option to configure it. Thanks!

[malmis]

[malmis@cruella XBMC]$ ./build.sh DEST=/home/malmis/xbmc-test/
Local source revision : 11180
Repository revision : 11181
Your source is outdated.
Update? (y/n) : y
Updating source code.
U xbmc/cores/dvdplayer/ALSADirectSound.cpp
Uppdaterade till revision 11181.

FAILED! Exiting.
[malmis@cruella XBMC]$

would be nice if it doesn't exit after updateing source code, and just run as it should.

[althekiller]

It's exiting for a reason...svn doesn't seem to be returning 0 for you. Run "svn up" on it's own and try to figure out the problem. You should be able to build with the NOUPDATE option in the meantime.

[malmis]

i can build with the noupdate, but that wasn't the point now.

It's exiting for a reason...svn doesn't seem to be returning 0 for you. Run "svn up" on it's own and try to figure out the problem. You should be able to build with the NOUPDATE option in the meantime.

[althekiller]

I don't know what you expect me to do if you aren't going listen to my suggestions or provide more information. You are the only one to have this problem so it is something with your setup.

[malmis]

I don't know what you expect me to do if you aren't going listen to my suggestions or provide more information. You are the only one to have this problem so it is something with your setup.

huh?
what i was saying was that when i run the script to update and install, it updates and then exit, if i run it again it install, i can do a svn up before i run, but whats the point of the script then when it should do svn up for me and install?!

i did show u an exactly output of what was happening, so i don't really understand what u are talking about.

and how do u know i'm the only one with this problem?
i got this same problem in archlinux, gentoo, slackware and cygwin on 4 different computers, with a lot different setup and configuration.

[rodalpho]

There is no real support for XBMC/linux, it's still in alpha and the developers are not actively assisting endusers yet. If you're looking to run XBMC/linux fulltime and you're not very comfortable with coding yourself, I strongly suggest running the official development platform-- ubuntu 7.10 32bit.

[malmis]

There is no real support for XBMC/linux, it's still in alpha and the developers are not actively assisting endusers yet. If you're looking to run XBMC/linux fulltime and you're not very comfortable with coding yourself, I strongly suggest running the official development platform-- ubuntu 7.10 32bit.

i was just asking and maybe it was a simple problem to solve or something, now it works for me again, but don't really know how.

[s7mx1]

The code in question is

CORES=$(grep "processor" /proc/cpuinfo | wc -l)

which would give incorrect info regarding the cpus, for example if the "model name" contains the key word "processor", like the case of appletv.

Sample output of appletv's /proc/cpuinfo

processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 13
model name : Genuine Intel(R) processor 1.00GHz
stepping : 8
cpu MHz : 600.000
cache size : 2048 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss tm pbe nx up bts est tm2
bogomips : 1201.30
clflush size : 64

Solutions:

CORES=$(grep ^processor /proc/cpuinfo | wc -l)

One more thing about the script is that sometimes it needs too much end-user attention. It will be a good idea to add a "-y" switch to auto answer all the questions.

[s7mx1]

submitted two patches to sourceforge


http://sourceforge.net/tracker/index.php?func=detail&aid=1863202&group_id=87054&atid=581840

http://sourceforge.net/tracker/index.php?func=detail&aid=1863214&group_id=87054&atid=581840

[gzusrawx]

Has anyone successfully run this in Ubuntu64 7.10 gutsy?

[althekiller]

i got this same problem in archlinux, gentoo, slackware and cygwin on 4 different computers, with a lot different setup and configuration.

Funny as it was developed on gentoo...anyway this is getting us nowhere. I'm going to add the patches that have been posted recently and make a flag that doesn't suppress any output. I'll need you to run with this flag and www.pastebin.ca the output.


One more thing about the script is that sometimes it needs too much end-user attention. It will be a good idea to add a "-y" switch to auto answer all the questions.

I think you're looking for the "CONFIRM" option. --help was added to be read...
I'll add your other patches though, thanks.


Has anyone successfully run this in Ubuntu64 7.10 gutsy?

The linuxport as a whole doesn't support 64bit so no attempt has been made to get build.sh to work with it yet.

UPDATE: Ok, updates sent to pike. Should be in svn when he wakes up.

[s7mx1]

I think you're looking for the "CONFIRM" option. --help was added to be read...
I'll add your other patches though, thanks.


Thanks.

One thing I noticed about Changelog.py is that if you run it at a location other than the XBMC source folder it will complain about

svn: '.' is not a working copy

since the svn wasn't provided the svn root folder.

Here is my patch for Changelog.py


--- Changelog.py.back 2008-01-04 09:24:00.000000000 +0000
+++ Changelog.py 2008-01-04 10:04:19.000000000 +0000
@@ -74,7 +74,7 @@
output.write(s)
sys.exit()

-svncmd = "svn log --xml -r %s:HEAD" % (lastrev)
+svncmd = "svn log --xml -r %s:HEAD %s" % (lastrev,dir)
newlog = os.popen(svncmd)

newlogdoc = newlog.read()

althekiller, do you mind submitting that patch as well? Thank you all for your great efforts.

The build script from now on will be executed at 6 pm every day on my machine. Good luck to me! :)

[althekiller]

Changelog.py was tossed together in a few minutes just to get changelog in linux, I've been meaning to rework it for awhile now.

[LittleBear1981]

I was using an older version of XBMC Linux.. i figured it would be best to start fresh versus trying to upgrade. I deleted my original folder and made a new one. Downloaded the latest svn did the apt-get line and tried build.sh got errors. tried sudo got the same errors.

tony@tony-laptop:~/XBMC$ sudo ./build.sh
There is really no reason to run this as root or with sudo.
Run anyway? (y/n) : y
Local source revision : 11345
Repository revision : 11345
Your source is up to date.
Configuring build.
./build.sh: line 176: ./configure: Permission denied
Configuring build.
./build.sh: line 176: ./configure: Permission denied
Cleaning source directory.
Compiling source.
Detected 2 procs/cores, using -j2
make: Entering directory `/home/tony/XBMC'
make: *** No targets specified and no makefile found. Stop.
make: Leaving directory `/home/tony/XBMC'
Generating Changelog.txt
./build.sh: line 500: ./tools/Changelog/Changelog.py: Permission denied
Backing up old ./BUILD to ./BUILD.bak.
Removing old ./BUILD.bak first.
Creating ./BUILD.
Copying xbmc-xrandr
FAILED! Exiting.
tony@tony-laptop:~/XBMC$

please anyone, i am somewhat failure with the command line.

[LittleBear1981]

i meant familiar with the linux command line interface.

[althekiller]

Run "ls -l configure" from your source tree". Output should look similar to

nelson11@farnsworth ~/code/XBMC $ ls -l configure
-rwxr-xr-x 1 nelson11 users 343968 Jan 6 15:51 configure

if the permissions are not -rwxr-xr-x, run "chmod 755 configure" and all should be well.

[LittleBear1981]

Thank you... its compiling..... much love.. Thanks!

[althekiller]

np, dunno how your permissions got messed up. They should be preserved through subversion.

[Livin]

Linux noob here...

I have followed the Wiki (http://xbmc.org/wiki/?title=HOW-TO_compile_XBMC_for_Linux_from_source_code) but got error since build.sh checks for packages needed, which are not installed. Yes, I missed the 1 line that tells you to check the Readme.linux :P

Maybe this is something that can be added to build.sh... check and download packages if missing?

Just a thought.

Al, thx for helping the community!

[althekiller]

The only reason I don't add the package requirements is because I want to keep the script distribution independent. It's a PITA to detect distro and would be even more of a pain to maintain package lists for them all. Everyone should know, or learn quickly, to ALWAYs read the README before they do anything with open source software.

[xgrep]

The only thing that's a little off for me is that build.sh doesn't give you the chance to perform the apt-get after it updates README.linux. So you have to wait till a compiler error to see if you're missing packages. I typically svn up first, check the readme, then run build.sh. This works for me, but it's not as elegant as it could be.

Could maybe just support the 3 supported ubuntu versions, and allow the user to set them as oppose to trying to detect them.

But then again, all these problems will be gone with the .deb package that's released. :)

xgrep

[althekiller]

Good point. build.sh now checks for changes to README.linux, forces the user to read it if so, then prompts whether or not to continue.

[rodalpho]

Now that "make install" is available, should it be used for SVN releases or should we stick with build.sh?

[althekiller]

I'd leave it up to the user. The whole autotools thing could be too complex for some users. Not to mention you may not want to kill a working build with an untested broken one.

[rodalpho]

I'm perfectly happy with build.sh but make install is significantly easier to package for debian/ubuntu... would prefer further development focus on that, IMO.

[wattazoum]

Well, in my opinion, the Build.sh is like an equivalent of "make install". For the packaging, "make" is used to compile and "make install DESTDIR=xxx" to install in a temporary dir in which we will use to split the package into subpackage by specifying the files/dirs to include in each of them.

With the build.sh we can do the same :
use make then build.sh DEST=xxx NOCOMPILE NOCLEAN NOUPDATE

But for sure, the standard way of doing is make , make install

[althekiller]

Once the install target is full featured, I'll likely move build.sh to use it. Until then both will be developed.

[wattazoum]

hello,

Can you check this patch ? http://sourceforge.net/tracker/index.php?func=detail&aid=1940859&group_id=87054&atid=581840
It completes the install target (to be able to use the --prefix option) .

Thank you

[althekiller]

Erm...I dunno what you diffed that to but nothing in the patch even touches build.sh. I'm planning a complete rewrite soon anyway which will add support for this so no biggie.

[wattazoum]

It doesn't touch the build.sh script because it's not meant to. It is for the Makefile install target.
Currently, using the SVN code level, you can install xbmc doing a make install but it will always install under /usr/share/xbmc . But usually the make install command uses a PREFIX=<dir> param to specify the install location. So this patch allows this.
Morover, the install path /usr/share/xbmc is hardcoded currently . Thus installing on another location will fail ( at runtime ). So the patch also changes this.

This is documented in the README.linux file ( after applying the patch )

Best regards

[topfs2]

It doesn't touch the build.sh script because it's not meant to. It is for the Makefile install target.
Currently, using the SVN code level, you can install xbmc doing a make install but it will always install under /usr/share/xbmc . But usually the make install command uses a PREFIX=<dir> param to specify the install location. So this patch allows this.
Morover, the install path /usr/share/xbmc is hardcoded currently . Thus installing on another location will fail ( at runtime ). So the patch also changes this.

This is documented in the README.linux file ( after applying the patch )

Best regards

Hi, from what I remember when I talked to d4rk about this patch he said that it wasn't viable to be put in svn because you use the PlatformDefs.h which didn't fit the crossplattform thing (I'm sorry if I'm vague, hope d4rk will spot this and clear it up :) )
From what I remember he said it would be better to use config.h
He have quite much now but I'll poke and yell on him and hopefully he can conjure up a better explanation

[althekiller]

I think I have a "proper" prefix patch. Testing ATM. I'll run it past d4rk and commit later tonight.

[topfs2]

That's wonderfull! I think that's the only thing holding for a new alpha candidate.

Thx alot!, both of you!

[althekiller]

Ok got a hold of d4rk finally to get this OKed. It's in.

[wattazoum]

Thank you althekiller . That's wonderfull. :-)

There is some modification that are however needed in the Makefile.in .

line 94: @cp tools/Linux/xbmc.sh /usr/bin/xbmc
should be replaced by :
@mkdir -p $(prefix)/bin
@cp tools/Linux/xbmc.sh $(prefix)/bin/xbmc

cause we can't assume that the script will be always in /usr/bin .

[wattazoum]

I also got a fancy scenario and I don't know if it'll work currently.
Basically, when doing a deb package, I need to create the system structure under a temp directory, then create the different subpackages by selecting the concerned file.
But when one will install them, it'll go under /usr/share/xbmc.

So basically I don't know how to do. and I don't think it's possible using only one parameter. I think the "install" target should take a DESTDIR variable to set the install directory (which can be different from the -prefix value).

This can be done by adding in the Makefile.in (to default to $(prefix) ):
DESTDIR=$(prefix)

and replace everywhere $(prefix) by $(DESTDIR)

[althekiller]

One problem I can see with putting the script in $(prefix)/bin/ is that the default $(prefix) is /usr/share and AFAIK no distro has /usr/share/bin in the default PATH. It's fine how it is because WE copy the files so WE know where they SHOULD be. If the end user wants to go mucking around they need to know what they're doing.

As for the second post, I think you're looking at more of a "dist" make target. I'll look into what it is supposed to entail as far as GNU is concerned and see what the devs have to say.

[wattazoum]

well ,

As far as GNU is concerned : http://www.gnu.org/software/make/manual/make.html#Directory-Variables

$(prefix) should default to "/usr/local" and Installers are expected to override these values when calling make (e.g., make prefix=/usr install or configure (e.g., configure --prefix=/usr) .
That's why in my first post I had put "$(prefix)/bin" (I didn't noticed that the prefix was set to /usr/share which doesn't follow GNU specification)
As for my second post, maybe i can achieve what I want by

./configure --prefix=/usr
make
make prefix=debian/tmp/usr install
But this still means that we need to have the change $(prefix)/bin/ but this time $(prefix) as in GNU specification

[althekiller]

update and be happy :)

[wattazoum]

Thank you :grin:

I don't want you to think that I am difficult but ... :laugh: it still need an update.
Currently the install script installs to /usr/xbmc and not /usr/share/xbmc . The file that is well installed is the xbmc script under /usr/bin/xbmc

Here is the files that need to be modified (so that you see what I mean )
http://www.mediafire.com/?uxf29um09rm

Thank a lot for your help and support
Regards

[wattazoum]

oops ! I forgot this file : Makefile.include.in

DEFINES+=-D_LINUX -D_FILE_DEFINED -D_REENTRANT -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 @SDL_DEFINES@ -DINSTALL_PATH="\"$(prefix)/share/xbmc\""

[althekiller]

Is there really a need to install to /usr/share? The app isn't really in a state where it can properly be split as per GNU and likely won't be until much closer to a supported public beta. I'd say just work with what we have now (it works) and we can worry about making it "proper" later.

[wattazoum]

well, as Topfs2 said, it seems to be what is holding the new RC back.

BTW the only think to change right now to support the GNU standard is the 3 files I mentioned early. The application will be installed in $(prefix)/share/xbmc and the launcher under $(prefix)/bin .
Those modification are the last step.

Anyway, as of now, you're right, XBMC will work but it will install under /usr/local/xbmc ( which is fine but a little bit messy :-p ) .

[typhoe]

Hi althekiller,

I would like to submit a little patch to your script for the svn revision detection in other languages than english.

I'm french and my locale is set in french. So when I try to check the svn revision of xbmc, here is what I get:
$ svn info "XBMC" -r HEAD

Chemin : XBMC
URL : https://xbmc.svn.sourceforge.net/svnroot/xbmc/branches/linuxport/XBMC
Racine du dépôt : https://xbmc.svn.sourceforge.net/svnroot/xbmc
UUID du dépôt : 568bbfeb-2a22-0410-94d2-cc84cf5bfa90
Révision : 13531
Type de noeud : répertoire
Auteur de la dernière modification : malloc64
Révision de la dernière modification : 13528
Date de la dernière modification: 2008-06-11 11:40:55 +0200 (mer, 11 jun 2008)

As you can see, in french Revision is spelled "Révision" (with an accent).

So your script can detect the revision because you do a grep on "Revision".

The change I suggest is simply to add in your script the use of the environmental setting "LANG" like this:
$ echo "Init lang is $LANG" ; LANG_old=${LANG} ; LANG="" ; echo "New lang is $LANG" ; svn info "XBMC" -r HEAD ; LANG=${LANG_old} ; echo "Lang is again $LANG"

Init lang is fr_FR.UTF-8
New lang is
Path: XBMC
URL: https://xbmc.svn.sourceforge.net/svnroot/xbmc/branches/linuxport/XBMC
Repository Root: https://xbmc.svn.sourceforge.net/svnroot/xbmc
Repository UUID: 568bbfeb-2a22-0410-94d2-cc84cf5bfa90
Revision: 13532
Node Kind: directory
Last Changed Author: malloc64
Last Changed Rev: 13528
Last Changed Date: 2008-06-11 11:40:55 +0200 (Wed, 11 Jun 2008)

Lang is again fr_FR.UTF-8

Using this method, the ouput of the svn command is defaulted to english and we have no problem to grep.

So the result:

$ diff build_new.sh build.sh
497,500d496
< # Read the actual value of the environmental setting LANG
< LANG_SYSTEM=$LANG
< # Default its value
< LANG=""
679,681d674
< # Restore LANG value (done there because I often do ctrl+c to bypass the log view :p )
< LANG=$LANG_SYSTEM
<

Thank you for your work,
hope this will help others,
regards,

Typhoe

[althekiller]

@typhoe, thanks, committed.

I've updated build.sh to use XBMCTex since the texture bundle is no longer in SVN. If you get a black screen with labels make sure you update and rebuild.

[Haohmaru]

@typhoe, thanks, committed.

I've updated build.sh to use XBMCTex since the texture bundle is no longer in SVN. If you get a black screen with labels make sure you update and rebuild.

I've 2 minutes ago compiled the latest SVN and after starting XBMC I can't see anything but a black background with the menu letters. Can someone please tell me why I doesn't see the skin properly and how can I fix it ?

[althekiller]

Are you using any options or just ./build.sh?
You can't honestly expect help with the amount of info you gave.

EDIT: I just ran it again and it worked fine...

[CapnBry]

For some reason I was losing my Lircmap.xml every time I used build.sh and it looks like the script doesn't copy it back from the backup properly because it is looking for UserData.bak not userdata.bak. I can just modify userdata and it will copy them over but I think this is the desired behaviorIndex: build.sh
================================================== =================
--- build.sh (revision 13746)
+++ build.sh (working copy)
@@ -318,13 +318,13 @@
done
elif [[ "$I" == "userdata" ]]
then
- if [[ -e "$BACKUPDIR/UserData" ]]
+ if [[ -e "$BACKUPDIR/userdata" ]]
then
if (( VERBOSE ))
then
- cp -vrf "$BACKUPDIR/UserData" "$BUILDDIR"
+ cp -vrf "$BACKUPDIR/userdata" "$BUILDDIR"
else
- cp -rf "$BACKUPDIR/UserData" "$BUILDDIR" &> /dev/null
+ cp -rf "$BACKUPDIR/userdata" "$BUILDDIR" &> /dev/null
fi
else
if (( VERBOSE ))
It is pretty changing 6 letters so I didn't see a need to create a patch entry for it on sourceforge, I hope you don't mind. If it is doing the desired behavior then just call me stupid and ignore me. Thanks for the awesome build script in any case!

[snappz]

First off thanks very much for build.sh. It is my preferred way of building and have used it since it was first included.

The last day or two I have not been able to successfully build SVN with it.
It keeps bombing out with


checking for main in -ljasper... (cached) no
configure: error: == Could not find a required library. Please see README.linux


I have read the readme and cut/paste the apt-get line.

I can build manually using make and I am using Ubuntu 8.04

Thanks again

[althekiller]

This has nothing to do with build.sh. The fact that the result is cached is curious, try deleting config.cache if it exists. Otherwise it is pretty obvious you're missing libjasper-dev and need to pay a little closer attention to what you're doing than simply C&P the apt line.

[sparky3387]

I had the same problem and was caused by config.cache

[snappz]

Thanks, deleting config.cache fixed it.

[succo]

would someone please fix build.sh?
it's still pointing to the rarred web files, but they are zips now, so it ends with error when copying skin

[spiff]

screw build.sh

[phunqe]

http://www.thegreenmachine.eu/forum/images/smilies/gently_pat.gif

[rodalpho]

Is that the official answer, then? Build.sh is being removed/deprecated and we should all use make install?

[xgrep]

As a temporary fix, you can do this while you're waiting for build.sh to be patched.


sudo apt-get install rar
cd /path/to/xbmcsvn/web
unzip -d Project_Mayhem_III_webserver_v1.0 Project_Mayhem_III_webserver_v1.0.zip
rar a Project_Mayem_III_webserver_v1.0.rar Project_Mayhem_III_webserver_v1.0

*Typo in Mayem is on purpose.

Then run build.sh again.

Cheers,
xgrep

[rodalpho]

Oh it's easy enough to fix or to to use make install. But if build.sh is being desupported it would be nice to get a heads-up.

[althekiller]

It's fixed. build.sh may see a complete change in style soon. Completely depends on my ambition.

[BLKMGK]

Just updated, got the new Build.sh, and it seems to have worked. When I use Make Install I notice that many of my movie covers are lost. <shrug> The Build script has been working for me well for awhile now honestly.

[althekiller]

If you switch to using "make install" you'll need to manually copy your userdata folder from BUILD to ~/.xbmc/ to preserve settings/thumbs/db/etc.

[BLKMGK]

Ah okay, thanks! However the Build script just ran through fine and I'm a happy camper :) web thing was driving me NUTZ. (lol)

[BLKMGK]

If you switch to using "make install" you'll need to manually copy your userdata folder from BUILD to ~/.xbmc/ to preserve settings/thumbs/db/etc.

Okay, I'd like to get this setup as well - where exactly should I find .xbmc or do I need to create it? I DO have show hidden turned on but I'm not familiar enough with Linux to know where settings liek this are "supposed" to be stored. <sigh>

TIA!

[rodalpho]

I don't remember if you need to create it or not. Try running the PPA release or make install and see. If you do, "mkdir ~/.xbmc".

[althekiller]

~ = your home dir. So /home/blkmgk/.xbmc/ or similar.
A structure will be created here the first time you run xbmc in platform mode "make install" installs a launcher script (xbmc) in your $PATH so you can launch it simply typing "xbmc" in a shell or create a launcher. You should NOT be directly running xbmc.bin when installing with this method or the PPAs. After the structure is created you can close XBMC then copy your userdata dir over from BUILD. Next time you run XBMC you should have all of your settings/thumbs/dbs/etc.

[BLKMGK]

Much much clearer - thank you!

[phunqe]

althekiller, thanks for your work with the build script. A continued working version even in the future would be much aprpeciated :)

[phunqe]

Of course, the make install is approach is easy enough, but the build script really makes for a neat installation procedure (aside from the PPAs).