The line-ending business is a mess. The normal approach with SVN and Tortoise SVN is to set the system to bring platform-dependent line breaks to the working folder on check-out and updates and to use the standard on-repository (LF = NL, no CR) on check-ins. This is by file type (wildcard) because it must be used only on text files, using the [auto-prop] option svn:eol-style=native. (Text file names with no file extensions are not helpful in that respect, as they have to be individually named in the svn config.)
The pain is that this appears to be a global setting for SVN and Tortoise SVN. You set the svn:eol-style on individual file types in the [auto-props] section of the SVN config file, and have the enable-auto-props option set in [miscellany]. You can choose to use the on-repository form in the working folder. The problem is that if you use Windows tools (Visual Studio, Visual Code, jEdit, whatever), you have to ensure that they use the same convention when they *save* files into the working folder. The better Windows development tools are ecumenical about what they accept, not being confused with either CRLF or LF (NL) alone. And some can be controlled in what they produce. The problem is using multiple repositories with different approaches. - Dennis > -----Original Message----- > From: Patricia Shanahan [mailto:p...@acm.org] > Sent: Tuesday, February 2, 2016 16:37 > To: dev@openoffice.apache.org > Subject: Re: Building on Windows > > On 2/2/2016 4:34 PM, Greg Bullock wrote: > > > > On 2/1/2016 3:33 PM, Patricia Shanahan wrote: > ... > >> Thanks for looking into it. It appears to probably be, ultimately, an > >> issue with TortoiseSVN mangling line endings. I am redoing the > >> checkout using Cygwin's command line svn. Once that is done, I'll > copy > >> over a few things from the old tree, and try again from autoconf on. > >> > >> Patricia > > > > I know you've already moved on to cygwin's command line svn, but for > > completeness: I believe TortoiseSVN lets you set options for whether > and > > how line endings should be handled on checkout. > > I found some information about that, but it was not clear how to set > "don't mess with the endings at all" for an entire source tree. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
