XP build environment

I have found that build errors are output with a 1> preceding each line.
This make Visual Studio unable to find the source line when scanning through
errors. Any idea why or how to illuminate.

Ken


You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com

Processor number? I was building (from command line) on a dual processor
system and saw the number before the ‘>’ switch between 0 and 1, so I
assumed that it was processor number.

Brad
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Ken Galipeau
Sent: Thursday, August 02, 2001 3:22 PM
To: File Systems Developers
Subject: [ntfsd] XP build environment

I have found that build errors are output with a 1> preceding each line.
This make Visual Studio unable to find the source line when scanning through
errors. Any idea why or how to illuminate.

Ken

You are currently subscribed to ntfsd as: xxxxx@macromedia.com
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com