On 01/09/2014 01:28 AM, Tyler Kavanaugh wrote: > I've just finished configuring and bootstrapping the Windows build of > OpenOffice (from the head revision on trunk). I changed to > aoo/main/instsetoo_native, and ran: > > build -P2 -- -P2
Also use the --all option, so that all dependencies of this final module are processed first, i.e. run build --all -P2 -- -P2 > [...] The first time I tried to do the build, about > an hour or so ago, I got errors relating to the use of carriage > return/newline (\r\n) pairs, with Perl complaining that '\r' wasn't a > valid command. (Keep in mind that my initial checkout was done using > TortoiseSVN and not Cygwin). So I clobbered the whole checkout, redid it > with the Cygwin svn client, then reconfigured and bootstrapped again. I > remembered to source the winenv.set.sh file--did that prior to the call > to ./bootstrap. Apparently cygwin's Subversion and Tortoise use different defaults for files without a svn:eol-style property (or with svn:eol-style=native). Keeping files as they are checked in when that property hasn't been set seems to be the default for cygwin's svn. Can Tortoise be configured to behave similarly? Herbert --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org