Re: [Flightgear-devel] TerraSync libSVN replacement testing
On 21 Jul 2013, at 13:45, Alan Teeder ajtee...@v-twin.org.uk 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 plan is to enable it (and require it) for 3.0, but I won't make that change until after 2.12 is released, since I'm aware of some intermitted issues with the code, where it gets stuck 'not doing anything'. This is happening for some people erratically, but is annoying, and obviously precludes enabling the code by default! Gijs also reported a crash on Windows - help tracking that down would be most welcome. Regards, James -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] TerraSync libSVN replacement testing
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. Alan -Original Message- From: James Turner Sent: Tuesday, June 11, 2013 4:17 PM To: FlightGear developers discussions Subject: [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 disk space it currently does, since unlike a real SVN client, we don't need to keep two copies of each file locally. In the longer term, there are many other improvements I will make - to reduce the number of network round-trips to check directories are in sync, to improve the interaction with the main thread so the splash screen waits for terrasync to update a location before finalising position, and others. These things will happen *after* 2.12, and once the code is tested everywhere. First, I need some help; for people to rebuild simgear with -DSG_SVN_CLIENT=1, and mv / erase their TerraSync dir. Then simply run FGFS as normal, as if you were starting on a new machine / account with no previous use of TerraSync. (Remember that TerraSync initially syncs the large Models and Airports dirs, which takes some time - be patient. Also expect some nav-cache rebuilds since the nav-cache will see the paths / stat-times change. This is nothing to do with the revised code, simply what happens if you change your TerraSync dir) If the testing is mostly positive, I will consider making the option default to ON for 2.12, but if people report problems (which cannot be easily fixed!), I will be cautious and leave it OFF by default for 2.12. Soon after 2.12 branches, 'next' will be switched to using the new code exclusively. (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!) James -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] TerraSync libSVN replacement testing
On 11 Jun 2013, at 16:17, James Turner zakal...@mac.com 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 disk space it currently does, since unlike a real SVN client, we don't need to keep two copies of each file locally. In the longer term, there are many other improvements I will make - to reduce the number of network round-trips to check directories are in sync, to improve the interaction with the main thread so the splash screen waits for terrasync to update a location before finalising position, and others. These things will happen *after* 2.12, and once the code is tested everywhere. First, I need some help; for people to rebuild simgear with -DSG_SVN_CLIENT=1, and mv / erase their TerraSync dir. Then simply run FGFS as normal, as if you were starting on a new machine / account with no previous use of TerraSync. (Remember that TerraSync initially syncs the large Models and Airports dirs, which takes some time - be patient. Also expect some nav-cache rebuilds since the nav-cache will see the paths / stat-times change. This is nothing to do with the revised code, simply what happens if you change your TerraSync dir) If the testing is mostly positive, I will consider making the option default to ON for 2.12, but if people report problems (which cannot be easily fixed!), I will be cautious and leave it OFF by default for 2.12. Soon after 2.12 branches, 'next' will be switched to using the new code exclusively. (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!) If you run from Git, haven't already tried this option, and have a spare moment, I would welcome more feedback on this. So far I have positive feedback from various people, and one problem I can't identity, which is slow downloads for Chris (papillion) on Linux. I encountered this on Mac during testing, erratically - it resulted in the Models directory taking 10 minutes to download instead of the more normal 2-3 minutes (of course scale those times by your Internet download bandwidth), but at some point during development it went away entirely. (The issue is not bandwidth, but the socket apparently sitting idle, as if there's a flow-control issue) Regards, James -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] TerraSync libSVN replacement testing
James
With your patch it now compiles and runs, but changing “or” to “||” is still
required.
The MSVC API kindly greys out code that is ignored by #ifdef statements, e.g.
in (terrasync.cxx at about line 340:-
#if defined(HAVE_SVN_CLIENT_H) or defined(SG_SVN_CLIENT)
if (_use_svn _use_built_in)
status = Using built-in SVN support. ;
else
#endif
if (_use_svn)
{
status = Using external SVN utility ';
status += _svn_command;
status += '. ;
}
the greyout starts after “#if defined(HAVE_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: [Flightgear-devel] TerraSync libSVN replacement testing
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
I have a fix to make it compile.
In SVNRepository.hxx, change names off 1st two elements in enum ResultCode
e.g.
enum ResultCode {
ERROR_NONE = 0,
ERROR_UNFOUND,
ERROR_SOCKET,
ERROR_XML,
ERROR_TXDELTA,
ERROR_IO,
ERROR_CHECKSUM
};
Also change these names in SVNRepository.cxx, SVNReportParser.cxx,
SVNDirectory.cxx and terrasync.cxx.
Also #if defined(HAVE_SVN_CLIENT_H) or defined(SG_SVN_CLIENT) should be
corrected on each occurence in terrasync.cxx
Alan
From: Alan Teeder
Sent: Monday, June 17, 2013 11:34 PM
To: FlightGear developers discussions
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: Alan Teeder
Sent: Monday, June 17, 2013 10:00 PM
To: FlightGear 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 discussions
Subject: Re: [Flightgear-devel] TerraSync libSVN replacement testing
On 17 Jun 2013, at 21:25, Vivian Meazza vivian.mea...@lineone.net 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 would be risky,
this close to the freeze. It's strictly a new, optional feature until after
2.12 is branched.
Alan, did you have any luck with the compiler errors? it builds on the Windows
build slaves on Jenkins I believe.
Regards,
James
--
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
--
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
--
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
--
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
Re: [Flightgear-devel] TerraSync libSVN replacement testing
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 Store. http://p.sf.net/sfu/windows-dev2dev___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] TerraSync libSVN replacement testing
James
I have a fix to make it compile.
In SVNRepository.hxx, change names off 1st two elements in enum ResultCode
e.g.
enum ResultCode {
ERROR_NONE = 0,
ERROR_UNFOUND,
ERROR_SOCKET,
ERROR_XML,
ERROR_TXDELTA,
ERROR_IO,
ERROR_CHECKSUM
};
Also change these names in SVNRepository.cxx, SVNReportParser.cxx,
SVNDirectory.cxx and terrasync.cxx.
Also #if defined(HAVE_SVN_CLIENT_H) or defined(SG_SVN_CLIENT) should be
corrected on each occurence in terrasync.cxx
Alan
From: Alan Teeder
Sent: Monday, June 17, 2013 11:34 PM
To: FlightGear developers discussions
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: Alan Teeder
Sent: Monday, June 17, 2013 10:00 PM
To: FlightGear 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 discussions
Subject: Re: [Flightgear-devel] TerraSync libSVN replacement testing
On 17 Jun 2013, at 21:25, Vivian Meazza vivian.mea...@lineone.net 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 would be risky,
this close to the freeze. It's strictly a new, optional feature until after
2.12 is branched.
Alan, did you have any luck with the compiler errors? it builds on the Windows
build slaves on Jenkins I believe.
Regards,
James
--
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
--
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
--
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
--
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] TerraSync libSVN replacement testing
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 terrasync.cxx 3C:/FlightGear/simgear\simgear/io/SVNRepository.hxx(58): error C2059: syntax error : 'constant' 3C:/FlightGear/simgear\simgear/io/SVNRepository.hxx(65): error C2143: syntax error : missing ';' before '}' 3C:/FlightGear/simgear\simgear/io/SVNRepository.hxx(65): error C2238: unexpected token(s) preceding ';' 3C:/FlightGear/simgear\simgear/io/SVNRepository.hxx(67): error C2146: syntax error : missing ';' before identifier 'failure' 3C:/FlightGear/simgear\simgear/io/SVNRepository.hxx(67): error C4430: missing type specifier - int assumed. Note: C++ does not support default-int 3C:/FlightGear/simgear\simgear/io/SVNRepository.hxx(67): error C2270: 'failure' : modifiers not allowed on nonmember functions 3C:/FlightGear/simgear\simgear/io/SVNRepository.hxx(67): error C4430: missing type specifier - int assumed. Note: C++ does not support default-int 3C:/FlightGear/simgear\simgear/io/SVNRepository.hxx(68): error C2059: syntax error : 'private' 3C:/FlightGear/simgear\simgear/io/SVNRepository.hxx(69): error C2270: 'isBare' : modifiers not allowed on nonmember functions 3C:/FlightGear/simgear\simgear/io/SVNRepository.hxx(74): error C2059: syntax error : '}' 3C:/FlightGear/simgear\simgear/io/SVNRepository.hxx(74): error C2143: syntax error : missing ';' before '}' 3C:/FlightGear/simgear\simgear/io/SVNRepository.hxx(74): error C2059: syntax error : '}' 3C:\FlightGear\simgear\simgear\scene\tsync\terrasync.cxx(90): warning C4067: unexpected tokens following preprocessor directive - expected a newline 3C:\FlightGear\simgear\simgear\scene\tsync\terrasync.cxx(90): warning C4067: unexpected tokens following preprocessor directive - expected a newline 3C:\FlightGear\simgear\simgear\scene\tsync\terrasync.cxx(124): error C2088: '[' : illegal for class 3C:\FlightGear\simgear\simgear\scene\tsync\terrasync.cxx(124): error C2088: '[' : illegal for class 3C:\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: James Turner Sent: Tuesday, June 11, 2013 4:17 PM To: FlightGear developers discussions Subject: [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 disk space it currently does, since unlike a real SVN client, we don't need to keep two copies of each file locally. In the longer term, there are many other improvements I will make - to reduce the number of network round-trips to check directories are in sync, to improve the interaction with the main thread so the splash screen waits for terrasync to update a location before finalising position, and others. These things will happen *after* 2.12, and once the code is tested everywhere. First, I need some help; for people to rebuild simgear with -DSG_SVN_CLIENT=1, and mv / erase their TerraSync dir. Then simply run FGFS as normal, as if you were starting on a new machine / account with no previous use of TerraSync. (Remember that TerraSync initially syncs the large Models and Airports dirs, which takes some time - be patient. Also expect some nav-cache rebuilds since the nav-cache will see the paths / stat-times change. This is nothing to do with the revised code, simply what happens if you change your TerraSync dir) If the testing is mostly positive, I will consider making the option default to ON for 2.12, but if people report problems (which cannot be easily fixed!), I will be cautious and leave it OFF by default for 2.12. Soon after 2.12 branches, 'next' will be switched to using the new code exclusively. (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!) James -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear
Re: [Flightgear-devel] TerraSync libSVN replacement testing
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, 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 terrasync.cxx 3C:/FlightGear/simgear\simgear/io/SVNRepository.hxx(58): error C2059: syntax error : 'constant' 3C:/FlightGear/simgear\simgear/io/SVNRepository.hxx(65): error C2143: syntax error : missing ';' before '}' 3C:/FlightGear/simgear\simgear/io/SVNRepository.hxx(65): error C2238: unexpected token(s) preceding ';' 3C:/FlightGear/simgear\simgear/io/SVNRepository.hxx(67): error C2146: syntax error : missing ';' before identifier 'failure' 3C:/FlightGear/simgear\simgear/io/SVNRepository.hxx(67): error C4430: missing type specifier - int assumed. Note: C++ does not support default-int 3C:/FlightGear/simgear\simgear/io/SVNRepository.hxx(67): error C2270: 'failure' : modifiers not allowed on nonmember functions 3C:/FlightGear/simgear\simgear/io/SVNRepository.hxx(67): error C4430: missing type specifier - int assumed. Note: C++ does not support default-int 3C:/FlightGear/simgear\simgear/io/SVNRepository.hxx(68): error C2059: syntax error : 'private' 3C:/FlightGear/simgear\simgear/io/SVNRepository.hxx(69): error C2270: 'isBare' : modifiers not allowed on nonmember functions 3C:/FlightGear/simgear\simgear/io/SVNRepository.hxx(74): error C2059: syntax error : '}' 3C:/FlightGear/simgear\simgear/io/SVNRepository.hxx(74): error C2143: syntax error : missing ';' before '}' 3C:/FlightGear/simgear\simgear/io/SVNRepository.hxx(74): error C2059: syntax error : '}' 3C:\FlightGear\simgear\simgear\scene\tsync\terrasync.cxx(90): warning C4067: unexpected tokens following preprocessor directive - expected a newline 3C:\FlightGear\simgear\simgear\scene\tsync\terrasync.cxx(90): warning C4067: unexpected tokens following preprocessor directive - expected a newline 3C:\FlightGear\simgear\simgear\scene\tsync\terrasync.cxx(124): error C2088: '[' : illegal for class 3C:\FlightGear\simgear\simgear\scene\tsync\terrasync.cxx(124): error C2088: '[' : illegal for class 3C:\FlightGear\simgear\simgear\scene\tsync\terrasync.cxx(124): fatal 3error C1903: unable to recover from previous error(s); stopping compilation 3 Generating Code... -Original Message- From: James Turner Sent: Tuesday, June 11, 2013 4:17 PM To: FlightGear developers discussions Subject: [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 disk space it currently does, since unlike a real SVN client, we don't need to keep two copies of each file locally. In the longer term, there are many other improvements I will make - to reduce the number of network round-trips to check directories are in sync, to improve the interaction with the main thread so the splash screen waits for terrasync to update a location before finalising position, and others. These things will happen *after* 2.12, and once the code is tested everywhere. First, I need some help; for people to rebuild simgear with - DSG_SVN_CLIENT=1, and mv / erase their TerraSync dir. Then simply run FGFS as normal, as if you were starting on a new machine / account with no previous use of TerraSync. (Remember that TerraSync initially syncs the large Models and Airports dirs, which takes some time - be patient. Also expect some nav-cache rebuilds since the nav-cache will see the paths / stat-times change. This is nothing to do with the revised code, simply what happens if you change your TerraSync dir) If the testing is mostly positive, I will consider making the option default to ON for 2.12, but if people report problems (which cannot be easily fixed!), I will be cautious and leave it OFF by default for 2.12. Soon after 2.12 branches, 'next' will be switched to using the new code exclusively. (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!) 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. Vivian -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ Flightgear-devel mailing list Flightgear-devel
Re: [Flightgear-devel] TerraSync libSVN replacement testing
On 17 Jun 2013, at 21:25, Vivian Meazza vivian.mea...@lineone.net 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 would be risky, this close to the freeze. It's strictly a new, optional feature until after 2.12 is branched. Alan, did you have any luck with the compiler errors? it builds on the Windows build slaves on Jenkins I believe. Regards, James -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
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 discussions Subject: Re: [Flightgear-devel] TerraSync libSVN replacement testing On 17 Jun 2013, at 21:25, Vivian Meazza vivian.mea...@lineone.net 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 would be risky, this close to the freeze. It's strictly a new, optional feature until after 2.12 is branched. Alan, did you have any luck with the compiler errors? it builds on the Windows build slaves on Jenkins I believe. Regards, James -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
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: Alan Teeder Sent: Monday, June 17, 2013 10:00 PM To: FlightGear 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 discussions Subject: Re: [Flightgear-devel] TerraSync libSVN replacement testing On 17 Jun 2013, at 21:25, Vivian Meazza vivian.mea...@lineone.net 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 would be risky, this close to the freeze. It's strictly a new, optional feature until after 2.12 is branched. Alan, did you have any luck with the compiler errors? it builds on the Windows build slaves on Jenkins I believe. Regards, James -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] TerraSync libSVN replacement testing
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 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 the new option? Cheers, Anders -- --- Anders Gidenstam WWW: http://gitorious.org/anders-hangar http://www.gidenstam.org/FlightGear/ -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] TerraSync libSVN replacement testing
James As requested (windows 7, MSVC10 (32bit build): (Sorry) Alan 3 terrasync.cxx 3C:/FlightGear/simgear\simgear/io/SVNRepository.hxx(58): error C2059: syntax error : 'constant' 3C:/FlightGear/simgear\simgear/io/SVNRepository.hxx(65): error C2143: syntax error : missing ';' before '}' 3C:/FlightGear/simgear\simgear/io/SVNRepository.hxx(65): error C2238: unexpected token(s) preceding ';' 3C:/FlightGear/simgear\simgear/io/SVNRepository.hxx(67): error C2146: syntax error : missing ';' before identifier 'failure' 3C:/FlightGear/simgear\simgear/io/SVNRepository.hxx(67): error C4430: missing type specifier - int assumed. Note: C++ does not support default-int 3C:/FlightGear/simgear\simgear/io/SVNRepository.hxx(67): error C2270: 'failure' : modifiers not allowed on nonmember functions 3C:/FlightGear/simgear\simgear/io/SVNRepository.hxx(67): error C4430: missing type specifier - int assumed. Note: C++ does not support default-int 3C:/FlightGear/simgear\simgear/io/SVNRepository.hxx(68): error C2059: syntax error : 'private' 3C:/FlightGear/simgear\simgear/io/SVNRepository.hxx(69): error C2270: 'isBare' : modifiers not allowed on nonmember functions 3C:/FlightGear/simgear\simgear/io/SVNRepository.hxx(74): error C2059: syntax error : '}' 3C:/FlightGear/simgear\simgear/io/SVNRepository.hxx(74): error C2143: syntax error : missing ';' before '}' 3C:/FlightGear/simgear\simgear/io/SVNRepository.hxx(74): error C2059: syntax error : '}' 3C:\FlightGear\simgear\simgear\scene\tsync\terrasync.cxx(90): warning C4067: unexpected tokens following preprocessor directive - expected a newline 3C:\FlightGear\simgear\simgear\scene\tsync\terrasync.cxx(90): warning C4067: unexpected tokens following preprocessor directive - expected a newline 3C:\FlightGear\simgear\simgear\scene\tsync\terrasync.cxx(124): error C2088: '[' : illegal for class 3C:\FlightGear\simgear\simgear\scene\tsync\terrasync.cxx(124): error C2088: '[' : illegal for class 3C:\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: James Turner Sent: Tuesday, June 11, 2013 4:17 PM To: FlightGear developers discussions Subject: [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 disk space it currently does, since unlike a real SVN client, we don't need to keep two copies of each file locally. In the longer term, there are many other improvements I will make - to reduce the number of network round-trips to check directories are in sync, to improve the interaction with the main thread so the splash screen waits for terrasync to update a location before finalising position, and others. These things will happen *after* 2.12, and once the code is tested everywhere. First, I need some help; for people to rebuild simgear with -DSG_SVN_CLIENT=1, and mv / erase their TerraSync dir. Then simply run FGFS as normal, as if you were starting on a new machine / account with no previous use of TerraSync. (Remember that TerraSync initially syncs the large Models and Airports dirs, which takes some time - be patient. Also expect some nav-cache rebuilds since the nav-cache will see the paths / stat-times change. This is nothing to do with the revised code, simply what happens if you change your TerraSync dir) If the testing is mostly positive, I will consider making the option default to ON for 2.12, but if people report problems (which cannot be easily fixed!), I will be cautious and leave it OFF by default for 2.12. Soon after 2.12 branches, 'next' will be switched to using the new code exclusively. (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!) James -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] TerraSync libSVN replacement testing
On 11 Jun 2013, at 18:52, Anders Gidenstam anders-...@gidenstam.org 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 the new option? The terrasync binary *should* use the new SVN, it's certainly technically feasible, I just didn't test yet. Setting a refresh timeout is one of the things i want to do after 2.12 - probably 24 hours validity after a successful sync of a dir or tile, would give exactly the speed you want. (And greatly reduce trivial requests on the backend). But also once Airports/A..Z is synced, I'm going to convert it into a single Airports dir, and hence only one round-trip to update, *and* I'm planning to make syncing Airports, Models (and other data in the future, such as AI traffic), a separate HTTP engine from regular tiles, so tiles will validate quicker, not getting stuck behind 'slow' data. Taken together these things *should* make regular terrasync fast enough for you I hope - if you disagree, or can think of other ways to improve it, please say. James-- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
