Re: [opensource-dev] autobuild on linux?

2011-08-05 Thread Stone Linden
On Fri, Aug 5, 2011 at 1:19 PM, Boroondas Gupte
wrote:

> **
> On 08/05/2011 08:41 PM, Ace Ace wrote:
>
> does anyone know how to set this up on linux
>
> No real setup needed, you can check it out from hg ...
>
> mkdir ~/sldevstuff
> hg clone ssh://h...@bitbucket.org/lindenlab/autobuild ~/sldevstuff/autobuild
>
>  ... and then run it in a viewer source checkout by specifying the absolute
> path to the command in autobuild's bin directory, e.g. ...
>
> hg clone ssh://h...@bitbucket.org/lindenlab/viewer-development 
> ~/sldevstuff/viewer-development
> cd ~/sldevstuff/viewer-development
> ~/sldevstuff/autobuild/bin/autobuild build -c ReleaseOS
>
>
> Note that invocation with a relative path (i.e., in the example above
> ../autobuild/bin/autobuild) won't always work, the path has to be
> absolute. Shortcuts and aliases like "~" and "$HOME" work fine, though. I
> guess something in the scripts is sometimes eating the ".." upon the
> recursive self-invocation autobuild does.
>
> If you want to be able to use autobuild just by typing autobuild rather
> than a path to it, add the autobuild/bin directory to your PATH or symlink
> the autobuild script to a place which is, e.g. /usr/local/bin.
>
> You might also install autobuild with easy_install or pip as suggested on 
> Autobuild
> Quick Start , but
> that makes updating python, updating autobuild and removing (uninstalling)
> autobuild more complicated. (Or maybe I just don't know it how to do that
> cleanly with easy_install and pip.) With the setup above, autobuild won't
> need any additional steps to keep working when you upgrade python (as long
> as the new version is still compatible with) and updating autobuild can be
> done by simply by updating the repository. If you want to get rid of
> autobuild, just delete ~/sldevstuff/autobuild and remove the symlink if you
> created one.
>
>
> the wiki has no info on how to do it on linux
>
> Yeah, the Linux build instructions really could need some update. :-\
>
> Cheers,
> Boroondas
>
> PS: Just tried now and can't repro invocation with relative command path
> not working. Maybe this has been fixed since I've noticed this. Does anyone
> know?
>

I use it with a relative path call often, and it Works For Me (TM) :)

Cheers - Stone


> ___
> Policies and (un)subscribe information available here:
> http://wiki.secondlife.com/wiki/OpenSource-Dev
> Please read the policies before posting to keep unmoderated posting
> privileges
>
___
Policies and (un)subscribe information available here:
http://wiki.secondlife.com/wiki/OpenSource-Dev
Please read the policies before posting to keep unmoderated posting privileges

Re: [opensource-dev] autobuild on linux?

2011-08-05 Thread Boroondas Gupte
On 08/05/2011 08:41 PM, Ace Ace wrote:
> does anyone know how to set this up on linux
No real setup needed, you can check it out from hg ...

mkdir ~/sldevstuff
hg clone ssh://h...@bitbucket.org/lindenlab/autobuild ~/sldevstuff/autobuild

... and then run it in a viewer source checkout by specifying the
absolute path to the command in autobuild's bin directory, e.g. ...

hg clone ssh://h...@bitbucket.org/lindenlab/viewer-development 
~/sldevstuff/viewer-development
cd ~/sldevstuff/viewer-development
~/sldevstuff/autobuild/bin/autobuild build -c ReleaseOS


Note that invocation with a relative path (i.e., in the example above
../autobuild/bin/autobuild) won't always work, the path has to be
absolute. Shortcuts and aliases like "~" and "$HOME" work fine, though.
I guess something in the scripts is sometimes eating the ".." upon the
recursive self-invocation autobuild does.

If you want to be able to use autobuild just by typing autobuild rather
than a path to it, add the autobuild/bin directory to your PATH or
symlink the autobuild script to a place which is, e.g. /usr/local/bin.

You might also install autobuild with easy_install or pip as suggested
on Autobuild Quick Start
, but that makes
updating python, updating autobuild and removing (uninstalling)
autobuild more complicated. (Or maybe I just don't know it how to do
that cleanly with easy_install and pip.) With the setup above, autobuild
won't need any additional steps to keep working when you upgrade python
(as long as the new version is still compatible with) and updating
autobuild can be done by simply by updating the repository. If you want
to get rid of autobuild, just delete ~/sldevstuff/autobuild and remove
the symlink if you created one.

> the wiki has no info on how to do it on linux
Yeah, the Linux build instructions really could need some update. :-\

Cheers,
Boroondas

PS: Just tried now and can't repro invocation with relative command path
not working. Maybe this has been fixed since I've noticed this. Does
anyone know?
___
Policies and (un)subscribe information available here:
http://wiki.secondlife.com/wiki/OpenSource-Dev
Please read the policies before posting to keep unmoderated posting privileges

Re: [opensource-dev] autobuild on linux?

2011-08-05 Thread Vadim Savchuk
On Fri, Aug 5, 2011 at 9:41 PM, Ace Ace  wrote:

> does anyone know how to set this up on linux the wiki has no info on how to
> do it on linux
>
http://wiki.secondlife.com/wiki/Autobuild/Quick_Start
http://wiki.secondlife.com/wiki/Autobuild
http://wiki.secondlife.com/wiki/Building_the_Viewer_with_Autobuild

-- 
Vadim
___
Policies and (un)subscribe information available here:
http://wiki.secondlife.com/wiki/OpenSource-Dev
Please read the policies before posting to keep unmoderated posting privileges

[opensource-dev] autobuild on linux?

2011-08-05 Thread Ace Ace
does anyone know how to set this up on linux the wiki has no info on how to
do it on linux
___
Policies and (un)subscribe information available here:
http://wiki.secondlife.com/wiki/OpenSource-Dev
Please read the policies before posting to keep unmoderated posting privileges

Re: [opensource-dev] autobuild on linux

2011-02-19 Thread Nicky D.
>
> when i run autobuild configure -c OpenSourceRelWithDebInfo I still get
> 'autobuild.common.AutobuildError: invalid 'pathcheck' setting for 'boto'
>   looking in common.py, the pathcheck for boto is 'lib/python2.5/boto'
>
> Anyone have any hints to help me get further?
>

As normal user try the following
(  cd "/var/tmp/`whoami`/install.cache" && wget
http://s3.amazonaws.com/viewer-source-downloads/install_pkgs/boto-1.9b-common-20100414.tar.bz2
)

Then try again.
Looks like boto is a prereg that needs to be downloaded, but for
downloading you need boto. Or something like this :)
autobuild should really be happy if there is a system wide boto and use this.
For now you need to populate install.cache with the package, than
autobuild will unpack it for you and continue from there.

Cheers,
  Nicky
___
Policies and (un)subscribe information available here:
http://wiki.secondlife.com/wiki/OpenSource-Dev
Please read the policies before posting to keep unmoderated posting privileges


[opensource-dev] autobuild on linux

2011-02-19 Thread Twisted Laws

on Ubuntu ...
 
i've installed python-boto (sudo apt-get install python-boto) [also tried 
getting boto source direct and installing with 'sudo python setup.py install' 
after pulling with 'svn checkout http://boto.googlecode.com/svn/trunk']
 
i've installed llbase (hg clone https://bitbucket.org/lindenlab/llbase) and 
installed with 'sudo python setup.py install'
 
i've re-installed autobuild (hg clone 
https://bitbucket.org/lindenlab/autobuild) and installed with 'sudo python 
setup.py install'
 
when i run autobuild configure -c OpenSourceRelWithDebInfo I still get 
'autobuild.common.AutobuildError: invalid 'pathcheck' setting for 'boto'   
looking in common.py, the pathcheck for boto is 'lib/python2.5/boto'
 
Anyone have any hints to help me get further?
  ___
Policies and (un)subscribe information available here:
http://wiki.secondlife.com/wiki/OpenSource-Dev
Please read the policies before posting to keep unmoderated posting privileges

[opensource-dev] autobuild on Linux 64-bit standalone: setup & configuring issues (was: Using 'autobuild' to build the viewer)

2011-02-07 Thread Boroondas Gupte
Ok, I've finally taken some time to test autobuild, too.

On 01/28/2011 12:41 AM, Oz Linden (Scott Lawrence) wrote:
>
> To begin experimenting with this new way of doing things, you'll need
> to check out autobuild itself (it's written in python, and is open
> source) from:
>
> https://bitbucket.org/lindenlab/autobuild
>
> You can either run it directly from the checkout, or install it as a
> normal python package using the command:
>
> setup.py install
>
With the current (9ee2db08d677
)
autobuild, this command won't work on UNIX-like systems for two reasons
(see OPEN-10 ). Workaround
is to prepend python, i.e. call

python setup.py install

or, because this tries to write into system directories

sudo python setup.py install


> A "standalone" non-Linden developer build:
>
> autobuild configure -c OpenSourceStandaloneRelWithDebInfo
>
This won't work with the current (00453191c1b9
)
viewer-autobuild code: "standalone" has to be CamelCased, too:

autobuild configure -c OpenSourceStand*A*loneRelWithDebInfo


Then, I had to merge in my VWR-24520
 fix or I'd hit that bug,
just as I would in unmodified viewer-development. After that,
configuring yields:

$ autobuild configure -c OpenSourceStandAloneRelWithDebInfo
-- The C compiler identification is GNU
-- The CXX compiler identification is GNU
-- Check for working C compiler: /usr/bin/gcc
-- Check for working C compiler: /usr/bin/gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Using autobuild at: /usr/bin/autobuild
-- checking for module 'ogg'
--   found ogg, version 1.2.0
-- checking for module 'vorbis'
--   found vorbis, version 1.3.1
-- checking for module 'vorbisenc'
--   found vorbisenc, version 1.3.1
-- checking for module 'vorbisfile'
--   found vorbisfile, version 1.3.1
-- checking for module 'openal'
--   found openal, version 1.11.753
-- checking for module 'freealut'
--   found freealut, version 1.1.0
-- Building with OpenAL audio support
-- Found Google BreakPad: /usr/lib64/libbreakpad_client.so
*CMake Error at cmake/Copy3rdPartyLibs.cmake:263 (copy_if_different):
  COPY_IF_DIFFERENT Macro invoked with incorrect arguments for macro named:
  COPY_IF_DIFFERENT
Call Stack (most recent call first):
  llcommon/CMakeLists.txt:14 (include)*


-- Looking for XOpenDisplay in /usr/lib64/libX11.so;/usr/lib64/libXext.so
-- Looking for XOpenDisplay in /usr/lib64/libX11.so;/usr/lib64/libXext.so - 
found
-- Looking for gethostbyname
-- Looking for gethostbyname - found
-- Looking for connect
-- Looking for connect - found
-- Looking for remove
-- Looking for remove - found
-- Looking for shmat
-- Looking for shmat - found
-- Looking for IceConnectionNumber in ICE
-- Looking for IceConnectionNumber in ICE - found
-- Found X11: /usr/lib64/libX11.so
-- checking for module 'freetype2'
--   found freetype2, version 12.1.6
-- Looking for include files CMAKE_HAVE_PTHREAD_H
-- Looking for include files CMAKE_HAVE_PTHREAD_H - found
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
-- checking for module 'atk'
--   found atk, version 1.30.0
-- checking for module 'cairo'
--   found cairo, version 1.8.10
-- checking for module 'gdk-2.0'
--   found gdk-2.0, version 2.20.1
-- checking for module 'gdk-pixbuf-2.0'
--   found gdk-pixbuf-2.0, version 2.20.1
-- checking for module 'glib-2.0'
--   found glib-2.0, version 2.24.2
-- checking for module 'gmodule-2.0'
--   found gmodule-2.0, version 2.24.2
-- checking for module 'gtk+-2.0'
--   found gtk+-2.0, version 2.20.1
-- checking for module 'gthread-2.0'
--   found gthread-2.0, version 2.24.2
-- checking for module 'libpng'
--   found libpng, version 1.4.5
-- checking for module 'pango'
--   found pango, version 1.28.3
-- checking for module 'pangoft2'
--   found pangoft2, version 1.28.3
-- checking for module 'pangox'
--   found pangox, version 1.28.3
-- checking for module 'pangoxft'
--   found pangoxft, version 1.28.3
-- checking for module 'sdl'
--   found sdl, version 1.2.13
-- Looking for Q_WS_X11
-- Looking for Q_WS_X11 - found
-- Looking for Q_WS_WIN
-- Lookin