Alexander Neundorf wrote:
On Friday 24 August 2007 04:48, Andreas Pakulat wrote:
On 24.08.07 11:02:02, Dizzy wrote:
My project in the install phase copies some configuration files. These
files are originally using UNIX line endings (we are doing main
development on UNIX plus SVN likes to keep t
On Friday 24 August 2007 04:48, Andreas Pakulat wrote:
> On 24.08.07 11:02:02, Dizzy wrote:
> > My project in the install phase copies some configuration files. These
> > files are originally using UNIX line endings (we are doing main
> > development on UNIX plus SVN likes to keep them that way).
>
2007/8/24, Dizzy <[EMAIL PROTECTED]>:
> On Friday 24 August 2007 13:04:15 Jack Kelly wrote:
> > Dizzy wrote:
> >
> > You shouldn't have to do any escaping. Use
> >
> > CONFIGURE_FILE(${SOURCEFILE} ${DESTFILE} COPYONLY)
>
> Thanks for the hint. This should solve my existent problem but it's not a go
On Friday 24 August 2007 13:04:15 Jack Kelly wrote:
> Dizzy wrote:
> > Thanks for the idea. I could use as a workarround configure_file() in
> > some way or another but then I still need one more issue solved. How to
> > escape "${variable}" strings in a input to configure_file() so that it
> > doe
Dizzy wrote:
Thanks for the idea. I could use as a workarround configure_file() in some way
or another but then I still need one more issue solved. How to
escape "${variable}" strings in a input to configure_file() so that it
doesn't try to do variable replacement on the placeholder? (this shou
On Friday 24 August 2007 12:30:58 Andreas Pakulat wrote:
> On 24.08.07 12:08:34, Dizzy wrote:
> > On Friday 24 August 2007 11:48:27 Andreas Pakulat wrote:
> > > Alternatively you could let your program be intelligent enough to guess
> > > the lineending by checking wether its \r\n or just \n and ad
On 24.08.07 12:08:34, Dizzy wrote:
> On Friday 24 August 2007 11:48:27 Andreas Pakulat wrote:
> > Alternatively you could let your program be intelligent enough to guess
> > the lineending by checking wether its \r\n or just \n and adjust the
> > reading of the conf files apropriately.
>
> The pro
On Friday 24 August 2007 11:48:27 Andreas Pakulat wrote:
> You can have a different lineending on the working copy really easily by
> using svn:eol-style property (on each file where you want it). That way
> you could checkout on win32 and automatically get win32-lineendings for
> those files that
On 24.08.07 11:02:02, Dizzy wrote:
> My project in the install phase copies some configuration files. These files
> are originally using UNIX line endings (we are doing main development on UNIX
> plus SVN likes to keep them that way).
Right, SVN internally always stores text files with only \n a
Hello
My project in the install phase copies some configuration files. These files
are originally using UNIX line endings (we are doing main development on UNIX
plus SVN likes to keep them that way). However, when installing on Win32 (or
other platform with different line endings) it would be n
10 matches
Mail list logo
