I moved my own llvm tree out of the way and tried to get a fresh copy from cvs and build everything from scratch... and it worked! apart from one little problem, a file was moved and should be removed from the project files -- here is a patch. There is a small problem with submitting patches for the .vcproj files - VS saves them with CRLF line endings but the CVS versions appear to have only LF (Unix style). This causes every line to differ! I used 'tr -d \r' this time, but it will be a bit painful to have to do this every time a project file is modified... Any suggestions? There are some changes which should be applied to all project files, namely getting rid of the __STDC_LIMIT_MACROS preprocessor define and disabling the negating unsigned number warning... Because of the line ending problem it will have to wait until something more important forces a check in of the project files. m. -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: diff.txt URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20041108/c533856d/attachment.txt>
Are you sure your CVS is configured correctly? On Windows, CVS automatically converts between LF and CR/LF line endings. I sent a patch to remove all CRs from the repository because when I checked out the files on Windows, every line had two CRs and a single LF. When VS saved a modified project file, the extra CR went away, causing every line to diff. On Mon, 08 Nov 2004 12:10:21 +0100 Morten Ofstad <morten at hue.no> wrote:> I moved my own llvm tree out of the way and tried to get a fresh copy > from cvs and build everything from scratch... and it worked! apart from > one little problem, a file was moved and should be removed from the > project files -- here is a patch. > > There is a small problem with submitting patches for the .vcproj files - > VS saves them with CRLF line endings but the CVS versions appear to have > only LF (Unix style). This causes every line to differ! I used 'tr -d > \r' this time, but it will be a bit painful to have to do this every > time a project file is modified... Any suggestions? > > There are some changes which should be applied to all project files, > namely getting rid of the __STDC_LIMIT_MACROS preprocessor define and > disabling the negating unsigned number warning... Because of the line > ending problem it will have to wait until something more important > forces a check in of the project files. > > m. > >
Jeff Cohen wrote:> Are you sure your CVS is configured correctly? On Windows, CVS > automatically converts between LF and CR/LF line endings. I sent a > patch to remove all CRs from the repository because when I checked out > the files on Windows, every line had two CRs and a single LF. When VS > saved a modified project file, the extra CR went away, causing every > line to diff.I'm using the cygwin cvs which doesn't add any CR when checking out.. so I'm getting the version with only LF and when VS saves a modified project file every line diffs... I don't see any option to cvs to tell it how to handle line endings, so I don't know how to fix this. m.
On Mon, 8 Nov 2004, Morten Ofstad wrote:> I moved my own llvm tree out of the way and tried to get a fresh copy > from cvs and build everything from scratch... and it worked! apart from > one little problem, a file was moved and should be removed from the > project files -- here is a patch.Applied. -Chris -- http://llvm.org/ http://nondot.org/sabre/