From: Vivian M. <viv...@li...> - 2011-06-23 07:44:21
|
Alan wrote > -------------------------------------------------- > From: "Vivian Meazza" <viv...@li...> > Sent: Wednesday, June 22, 2011 11:32 PM > To: "'FlightGear developers discussions'" > <fli...@li...> > Subject: Re: [Flightgear-devel] Heads up: scenery download > /built-interrasync > > > ThorstenB wrote: > > > >> > >> You need to provide a target directory for the scenery. This message > >> means the target directory is completely empty (or contains white- > spaces > >> only). See directory configured in the "scenery download" GUI. > >> Stuart's suggestion to use a default target may be a good idea. > >> > >> > Today, with the new GIT the Flightgear program crashes. Here is a > >> > stack > >> > trace: > >> > >> Thanks, a string boundary problem - should be fixed right now. The new > >> check to avoid svn from crashing on trailing "/" was missing a pair of > >> parenthesis. > >> > > > > With the latest Jenkins or Local builds I get this: > > > > Starting automatic scenery download/synchronization. Using external SVN > > utility > > 'C:/Program Files/Subversion/bin/svn'. Directory: > 'D:/Git_New/terrasync'. > > 'C:/Program' is not recognized as an internal or external command, > > operable program or batch file. > > > > Looks like a white space issue to me. > > > > When svn.exe is in the path I get: > > > > Starting automatic scenery download/synchronization. Using external SVN > > utility > > 'svn'. Directory: 'D:/Git_New/terrasync'. > > The filename, directory name, or volume label syntax is incorrect. > > > > Missing something? I'm probably doing something wrong. Any guidance? > > > > The Built-in download works correctly. > > > > Vivian > > > I have this on my MSVC10 machine and have put it down to cmake not finding > the SVN libraries. ( Note. I have given cmake the path to the SVN > includes.) > > If you look into the simgear\CMakeModules\FindSvnClient.cmake the SVN > search > paths are all unix style ones such /usr/local, but I have not looked any > further into the problem. > > All is OK on MSVC9, which is not encumbered with cmake. > I'm getting this problem on the latest Jenkins build #345, which I understand uses MSVC9, as well as my local MSVC9 build. Interesting to know that you aren't getting it with your local MSVC9 build. I'll look into it some more. Vivian |