11 messages in com.perforce.perforce-userX-Platform UNIX and NT code - CR/LF i...| From | Sent On | Attachments |
|---|---|---|
| Rick...@vsl.com | 15 Jun 1999 19:30 | |
| Eric...@Adobe.COM | 15 Jun 1999 20:12 | |
| Scot...@seaslug.org | 15 Jun 1999 20:55 | |
| Rick...@vsl.com | 15 Jun 1999 21:22 | |
| Rick...@vsl.com | 15 Jun 1999 21:29 | |
| Scot...@seaslug.org | 15 Jun 1999 22:04 | |
| Nick...@pobox.com | 16 Jun 1999 02:40 | |
| Nick...@pobox.com | 16 Jun 1999 02:44 | |
| Nick...@pobox.com | 16 Jun 1999 02:48 | |
| Eric...@Adobe.COM | 16 Jun 1999 07:30 | |
| Eric...@Adobe.COM | 16 Jun 1999 07:30 |
| Subject: | X-Platform UNIX and NT code - CR/LF issues (fwd) |
|---|---|
| From: | Scot...@seaslug.org (Scot...@seaslug.org) |
| Date: | 06/15/1999 08:55:22 PM |
| List: | com.perforce.perforce-user |
Rick Macdonald <rickm at vsl.com> wrote:
We've started using Perforce recently. Some of our people are developing code that runs on UNIX and NT. I'm told that Visual C++ can't handle UNIX files (LF) and UNIX compilers can't handle DOS files (CR/LF).
I've done builds in a single directory tree from both platforms (a couple years ago). I think that was with VC 4.x. I had a complicated GNU makefile scheme setup to drop the generated files (e.g. *.o, *.obj) into subdirectories named by platform type. I'm pretty sure the VC compiler handled the UNIX style LF-termination. I found that being able to do multi-platform builds off the same source directory was REAL handy...
Now, it's quite possible that some NT editors don't like that style, but I would think any reasonable one (i.e. not notepad) would work.
This means that the policy of the codeline from which you do this work must allow for incomplete, untested code to be checked in. If anybody makes an edit and submits changes in the middle of your work, you both have quite a mess to deal with. Likely neither one of you is in a state to incorporate the other persons unfinished code. All this would probably lead to each person making a personal branch for everything that they work on.
Yeah...a personal dev branch scheme is what I was just thinking of. I've never actually done that before, so I don't know how workable it really is in practice.
Scott.Blachowicz at seaslug.org