On 21 Jul 2013, at 13:45, Alan Teeder wrote:
> What is the status of this on Windows 64 bit?
>
> Up until now I have kept with 32 bit builds on Windows due to the lack of a
> 64 bit version of libSvn.
The replacement code is disabled by default on next, and 2.12 will certainly
not use it. My
: [Flightgear-devel] TerraSync libSVN replacement testing
Hi,
I've pushed some code to Git, which will ultimately replace our use of
libSvn, and hence simplify build and deployment, especially on Mac and
Windows. This has an immediate benefit for end-users too: TerraSync will use
pretty much half the
On 11 Jun 2013, at 16:17, James Turner wrote:
> I've pushed some code to Git, which will ultimately replace our use of
> libSvn, and hence simplify build and deployment, especially on Mac and
> Windows. This has an immediate benefit for end-users too: TerraSync will use
> pretty much half the
James
Success !!
The built in system populates an empty Terrasync directory, and my “new” hangar
appears at an otherwise empty airfield (EGNO).
Thanks
Alan--
This SF.net email is sponsored by Windows:
Build for Windows St
AVE_SVN_CLIENT_H)”, showing that the
code after and including “or” is ignored.
This is confirmed at runtime as "Using external SVN utility '" appears in the
log.
Alan
From: Alan Teeder
Sent: Tuesday, June 18, 2013 10:17 AM
To: FlightGear developers discussions
Subject: Re: [Fligh
And it works too!
Once the problem that Vivian reported is sorted I will also try with a 64 bit
Windows build.
Thanks
Alan
From: Alan Teeder
Sent: Tuesday, June 18, 2013 9:55 AM
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] TerraSync libSVN replacement testing
James
Subject: Re: [Flightgear-devel] TerraSync libSVN replacement testing
James
I found this, in terrasync.cxx, line 91, but the compilation is still failing
#if (defined(HAVE_SVN_CLIENT_H) or defined(SG_SVN_CLIENT))
should be ?
#if (defined(HAVE_SVN_CLIENT_H) || defined(SG_SVN_CLIENT))
Alan
From
developers discussions
Subject: Re: [Flightgear-devel] TerraSync libSVN replacement testing
Sorry James, I just reported ,and then left it.
I can give it a go, but my C++ debugging is somewhat hit and miss.
Alan
From: James Turner
Sent: Monday, June 17, 2013 9:38 PM
To: FlightGear developers
Sorry James, I just reported ,and then left it.
I can give it a go, but my C++ debugging is somewhat hit and miss.
Alan
From: James Turner
Sent: Monday, June 17, 2013 9:38 PM
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] TerraSync libSVN replacement testing
On 17
On 17 Jun 2013, at 21:25, Vivian Meazza wrote:
> Haven't managed to get it to work for Win 7 64 bit either - still seems to
> want LIBSVN to build. Seems to be a cmake issue, but I'm not confident that
> I know how to fix this one.
That's because I didn't yet remove the libsvn checks - that wou
Alan
> Sent: 17 June 2013 20:06
> To: FlightGear developers discussions
> Subject: Re: [Flightgear-devel] TerraSync libSVN replacement testing
>
> Does this affect the code freeze?
>
> -Original Message-
> From: Alan Teeder
> Sent: Tuesday, June 11, 20
Does this affect the code freeze?
-Original Message-
From: Alan Teeder
Sent: Tuesday, June 11, 2013 8:12 PM
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] TerraSync libSVN replacement testing
James
As requested (windows 7, MSVC10 (32bit build):
(Sorry)
Alan
3
On 11 Jun 2013, at 18:52, Anders Gidenstam wrote:
> I always use the separate terrasync binary since with it I only have to
> suffer the initial startup synchronization once per day - and not for each
> FG session.
>
> Will the separate terrasync binary use the new SVN replacement if I set
>
mgear\scene\tsync\terrasync.cxx(124): error C2088:
'[' : illegal for class
3>C:\FlightGear\simgear\simgear\scene\tsync\terrasync.cxx(124): fatal error
C1903: unable to recover from previous error(s); stopping compilation
3> Generating Code...
-Original Message-
From: Jam
On Tue, 11 Jun 2013, James Turner wrote:
> (BTW, the option to use rsync or external, command-line svnclient still
> exists, and will be retained - though I am curious if anyone still uses
> those options!)
I always use the separate terrasync binary since with it I only have to
suffer the init
Hi,
I've pushed some code to Git, which will ultimately replace our use of libSvn,
and hence simplify build and deployment, especially on Mac and Windows. This
has an immediate benefit for end-users too: TerraSync will use pretty much half
the disk space it currently does, since unlike a real S
16 matches
Mail list logo
