Rob Hudson wrote:
> The problem we have is that we can't pick a global one or the other due to
> various applications not handling them (off the top of my head, our copy of
> install shield doesn't like only having LF on Windows and our build scripts
> don't like CRLF on UNIX, things like Ksh just can't handle it)
Hi Rob,
I manage a build system in exactly the same situation: Building for
windows / hpux / aix / solaris / linux. I was able to achieve a unified
working copy by:
* engineering the build system to have per-platform output files
* keeping all files CR/LF (i.e. svn:eol-style=native and checkout on
windows)
* using tools like gcc and GNU make which grok any eol-style
* explicitly setting svn:eol-style=LF for specific files like your Ksh
example, since these files aren't needed on windows anyway
For further bonus points build all of these platforms (except hpux) via
cross compiler for huge speedup and to avoid I/O problems with intense
compile operations working over SAMBA or (less so) over NFS.
Some in this thread have suggested the proper solution is to have one WC
per platform, and checkout on the desired platform. While this does
have some merit, when you're running a large build system this also has
a few drawbacks:
* svn client required on every machine (sometimes difficult depending
on how old/odd the machine/os is)
* disk space goes way up (yes disk is cheap, but it isn't *faster*,
and backup overheads, etc. add up)
* extra problem of ensuring *exact same* source is used for every platform
* when making changes you have to copy them to every WC to test them,
before committing
-Nathan
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Thu Apr 19 17:30:06 2007