Linux build.sh script

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

Linux noob here...

I have followed the Wiki 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

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!

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.

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

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.

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

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.

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.

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

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