cons-discuss
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: How do I inhibit the copying of the source files to the build tree


From: Anthony Kolarik
Subject: RE: How do I inhibit the copying of the source files to the build tree
Date: Fri, 15 Mar 2002 08:28:46 -0500

I've never found an easy way to get parallel trees that contain _only_ intermediate and final product files.  And I think it would be great if you could.
 
Making the build dir a controlled element seems reasonable, although I don't know anything about MVFS so there may be gotchas. Naively it seems you'd end up with what looks like lots of replication of your code mixed in with your objs in the linked dirs but the "real" controlled src files would live in the MVFS directory tree. Clicking on error messages to linked files in the IDE should get you where you want to be. 
 
It seems like that's probably how its meant to work in a unix (hard link capable) environment.  i.e. do compiler line number errors in emacs or other unix IDEs resolve to the actual file with linked build trees? 
 -- Tony K.
 
-----Original Message-----
From: address@hidden [mailto:address@hidden
Sent: Thursday, March 14, 2002 7:49 PM
To: address@hidden
Subject: Re: How do I inhibit the copying of the source files to the build tree


Hi all, I would like to chime in and supplement my colleague Keith's comments. If you don't "link" then you cannot do variant builds, am I right? The way I see it, we want Cons to build our source tree and use compiler options to redirect the output based on the variant build directory ( build\debug\...\xxx.obj ). This seems to imply that Cons would have to maintain two sets of .consign files ( one set in the source tree, and one in the build tree ). My suspicion is that Cons wasn't designed for this and cannot do this without a redesign. If your filesystem supports links, then it isn't a problem. We use clearcase (MVFS) which supports links, but for controlled elements. The "build" dir is not a clearcase controlled element, which begs the question, could it be?

NTFS ( Win2k ) does support hardlinks for files only, but again we are using the clearcase filesystem (MVFS).

We are trying our best to use Cons, but we cannot disrupt the workflow of our developers. We are building drivers and applications for XP, clearcase is our configuration managment system, and we use the DevStudio environment for debugging. These facts are not going to change. I appreciate the flexibility of other platforms and environments, but this is our world.

Can anyone advise us as to whether we have any hope of getting Cons to do what we want? Have we made the problem clear?

Thanks for your comments

David Weidenkopf
Software Engineer
Philips Ultrasound

reply via email to

[Prev in Thread] Current Thread [Next in Thread]