I see that I should not have used those particular file names in my request.
We are *not* dealing with C++ (or C) source files. Think instead of files
"foofoo.x" and "foofoo.y" where we want the two names to refer to the same
file.
This is a legacy situation here and so our options are more limited than one
would like.
-----Original Message-----
From: Donald Sharp [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 13, 2000 9:30 AM
To: Eric Chamberlain
Cc: '[EMAIL PROTECTED]'
Subject: Re: Linked Files in the Repository
I seem to recall that it's very easy to tell MS's C++ compiler the
'correct' extensions for your file. Why don't you just do that.
Another thing that might be extremely usefull would be for you to
explain your cvs setup some more to us. What are you using?
pserver/ssh? What type of machine does your cvs sit on? How
you connect to the server?
thanks!
donald
On Thu, Jul 13, 2000 at 08:50:13AM -0700, Eric Chamberlain wrote:
> We all would *very* much like to change the build system as you suggest
but,
> for reasons I cannot go into here, that is not a feasible option.
>
> I just need to know what problems we should anticipate by using dual links
> within CVS.
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, July 12, 2000 10:20 PM
> To: Eric Chamberlain
> Cc: '[EMAIL PROTECTED]'
> Subject: Re: Linked Files in the Repository
>
>
> [ On Wednesday, July 12, 2000 at 15:42:45 (-0700), Eric Chamberlain wrote:
]
> > Subject: Linked Files in the Repository
> >
> > We have a cross-platform (Mac/Win) situation here. We have common
files
> > between the two systems but they need to have different file suffixes on
> the
> > two machines (!). Is it safe to simply create links in the repository
for
> > the common files?
> >
> > In other words, we might want one platform to call a given file
foofoo.cxx
> > and the other platform to call the *same* file foofoo.cpp. Can we just
> have
> > two unix-style links to the same file in the repository? Can you see
how
> > this would weird out the CVS code in some way?
>
> This is not a problem CVS should even attempt to contemplate. Fix your
> build system (or "wrap" it with some script that'll arrange such links
> at build time in each workspace as necessary).
>
> --
> Greg A. Woods
>
> +1 416 218-0098 VE3TCP <[EMAIL PROTECTED]> <robohack!woods>
> Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]>
>
