Re: [orca-list] A couple of questions about orca sources

[Steve Holmes <steve holmes88 gmail com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

I've always been wondering, when Orca is compiled and built to run in
a user's private directory like you suggest below, how do you get
gnome to launch that version instead of the general system-wide
default found in /usr/bin?

On Mon, Oct 12, 2009 at 03:44:53PM -0400, Willie Walker wrote:
> Hi Jen:
>
> On Mon, 2009-10-12 at 19:08 +0100, Jennifer wrote:
> > Hi. I have downloaded the latest orca sources and followed the
> > instructions for installing them (obtained from the gnome website).
> > According to the results of the command orca --version (checking the
> > git status also gives the same result) I am running version 2.27.92
> > pree
> > Is this the latest version as of Friday 9th October, retrieved by
> > using the git clone command (without specifying a branch?
>
> The configure.in file in the repository is what ends up setting this
> value.  I forgot to change the value to 2.29.1pre when I branched Orca
> for 2.28.0.  So, it was still stuck at 2.27.92pre.  I just checked in a
> change to update configure.in to flag the git master branch as
> 2.29.1pre.
>
> > If it is then the orca directory is visible in my /home/jen directory,
> > it was not visible before I installed these sources. Is orca running
> > from these sources by default? The command string in gnome
> > (/home/jen/orca) suggests that it is, and I can't remember if orca was
> > located in the same directory (but just hidden) last time.
> > If the new sources are not being used by default could someone please
> > tell me how to make them default, and if I should hide the orca
> > directory or move it to a more appropriate place?
>
> Where Orca ends up depends upon the --prefix flag you passed to the
> autogen.sh or configure file.  The orca build/install is also set up so
> that it should find the right Python modules.  I regularly run the
> following command from my orca directory:
>
> ./autogen.sh --prefix=`pwd`/bld
>
> With this, I can keep /usr/bin/orca at the version of Orca installed by
> the operating system distribution, while also working with the Orca
> sources from git.
>  
> > I also can't make Liblouis or brltty 4.0. I had some issues making the
> > brltty at work so don't think it is just something related to my
> > distro (9.04) Will liblouis be included in Orca installs by default?
>
> Liblouis and brltty are separate projects, so Orca doesn't include them.
> Instead, the packaging of these is dependent upon your operating system
> distribution.
>
> Hope this helps,
>
> Will
>
>
>
> _______________________________________________
> Orca-list mailing list
> Orca-list gnome org
> http://mail.gnome.org/mailman/listinfo/orca-list
> Visit http://live.gnome.org/Orca for more information on Orca.
> The manual is at http://library.gnome.org/users/gnome-access-guide/nightly/ats-2.html
> The FAQ is at http://live.gnome.org/Orca/FrequentlyAskedQuestions
> Netiquette Guidelines are at http://live.gnome.org/Orca/FrequentlyAskedQuestions/NetiquetteGuidelines
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEAREDAAYFAkrVYVAACgkQWSjv55S0LfHl6wCfW+3QvI+T3nCxri31jvo/FLSZ
LfgAn1HxDt+SP4UT5jgm/Qi1RY9s4SGd
=KpWL
-----END PGP SIGNATURE-----