Perforce Line Endings

Perforce Line Endings

Postby Bluebeary7 » Wed 17 Feb 2016 17:56

We have our Perforce workspaces set up to use Unix line endings (LF). Our machines are running Windows 10 with VS 2015.

Whenever we do a compare using any tool (Code Compare, VS Internal, or Araxis), we sometimes get double spaced lines and files converted to Windows (CRLF). When we do a Get from Perforce, the files come in as LF as they're supposed to. RA seems like it's converting to Windows (or OS specific). Not all files get converted to double spaced.

Any idea what's going on and how to fix it?

Thanks,
Rob
Bluebeary7
 
Posts: 2
Joined: Wed 17 Feb 2016 17:51

Re: Perforce Line Endings

Postby Artem » Thu 18 Feb 2016 12:00

Review Assistant keeps line endings as is. It just calls Perforce to get file from depot:
Code: Select all
p4.exe -p TCP:YOUR_SERVER:1666 print -o C:\PATH_TO_OUTPUT_FILE //DEPOT/YOURP_ROJECT/YOUR_FILE@REVISION_NO

Maybe, you should use the share option in your workspaces:
https://www.perforce.com/perforce/doc.current/manuals/cmdref/p4_client.html

Also, take a look at the following article: http://answers.perforce.com/articles/KB/3096
Artem
Devart Team
 
Posts: 137
Joined: Mon 21 Jun 2010 14:02

Re: Perforce Line Endings

Postby Bluebeary7 » Fri 19 Feb 2016 02:11

Thank you. I will try that Share option.
Bluebeary7
 
Posts: 2
Joined: Wed 17 Feb 2016 17:51


Return to Review Assistant