RE: [cciug] FW: ClearCase Visual C++ problem...

From: Riedel, Martina (Martina.Riedel@icn.siemens.com)
Date: Wed Jan 05 2000 - 16:17:23 EST


You really shouldn't use Tools->Options / Directory. that is for
installation paths and every user will have to duplicate your settings in
their installation. For your project you want to put all those settings in
Project -> settings.
You want to use either relative settings (..\include) or \code\include,
which will work from any view.
Martina
   Don't Postpone Joy - Have Fun
Martina Riedel Siemens Information and Communication
Networks
phone: 561-997-3774 Martina.Riedel@ICN.Siemens.com
<mailto:Martina.Riedel@ICN.Siemens.com>

                -----Original Message-----
                From: O'brien, Mark [mailto:marko@UU.NET
                Sent: Wednesday, January 05, 2000 3:05 PM
                To: 'cciug@rational.com'
                Cc: Swift, John
                Subject: [cciug] FW: ClearCase Visual C++ problem...

                Hello,
                        I am a developer who has recently introduced
ClearCase into my
                development
                environment and I'm having troubling setting my include
directories in
                DevStudio. I created a snapshot view, went into my view,
opened my project
                file which started Visual C++, then I went to the
"Tools->Options" menu and
                selected the "Directories" tab. From there, I am required to
set the search
                paths for the all include directories so Visual C++ can
compile my project.
                The problem is, Visual C++ insists on using the absolute
path which does not
                work in a team environment since the absolute path is
different for each
                team member using Visual C++ and ClearCase because ClearCase
requires every
                team member to have a unique view name, which equates to a
unique absolute
                path. Here's an example...

                In the Tools->Options->Directories tab I place the path to
the include
                directory where all of the public headers are located.

                        E:\snapshot\jswift_view\code\include

                At that point, I can compile everything fine. Then, a team
member of mine
                comes along and checks everything out and tries to build and
it fails
                because the compiler cannot find the header file. After Rob
examines the
                project's include directory settings he sees that the path
above is invalid
                for his and should be...

                        E:\snapshot\rob_view\code\include

                My question is how do we make both of these product work
harmoniously in a
                team environment? Simply adding every developers personal
view path in
                Visual C++ is NOT acceptable. Obviously we cannot all use a
standard view
                name such as...

                        E:\snapshot\project_view\code\include

                ...since only one of these can be created.

                Anyway, I checked the documentation and I can't find
anything on this
                problem. I suspect it's something simple that I'm just
missing.

                Can someone please help?
                js

                John Swift
                jswift@uu.net
                UUNET Technologies, an MCI WorldCom Company.

                 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
                 with
body
                 can also
unsubscribe
                 customers-only
website
                
http://clearcase.rational.com/cciug/mailing_list.html
 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -



This archive was generated by hypermail 2b29 : Sun May 06 2001 - 00:22:18 EDT