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

[Timothee Besset]

Well, if you don't use the Link statement, the files are not copied over
and the right files are used. You can keep the Link commands for your
baseline machines for instance.

The other solution is to live in an open source world and be able to patch
your IDE code to understand some basic things about cons. Probably not
relevant to you, but I am working on patches for Anjuta
(http://anjuta.sourceforge.net, a unix/Linux IDE) to teach it how to deal
with linked dirs and open the 'real' files instead.

TTimo

On Thu, 14 Mar 2002 13:20:54 -0800
address@hidden wrote:

> We have a couple of issues that arrise out of Cons behavior where all
> the source files are copied to a separate build tree:
> 
> By way of background, we are setting up a Cons build to replace an MS
> DevStudio based build. 1. Double clicking on error messages in the
> output window, to edit the source files, does not work well when doing a
> Cons build from within DevStudio. 2. Debugging from a Cons build does
> not make DevStudio very happy.   When debugging you are not seeing the
> file from source tree, rather you are seeing the "link"ed copy of it.
> Devstudio does not care about htis, but it confuses the developer.   I
> am curious why we would be the first group to encounter this and think
> it was not good.    Is the real question "How can we support variant
> builds without using the "link" command?"
> 
> One possible solution for these problems would be to completely inhibit
> Cons from copying the source to the build tree.   Is this possible?
> 
> Thanks in advance...
> 
> 
> ------------------------------------------------------------------------
> Keith Reed
> Software Engineer
> Philips Ultrasound
> 22100 Bothell Everett Hwy
> Bothell, WA 98021
> (425) 482-8338
> address@hidden
> 
> 
> 
> _______________________________________________
> address@hidden
> http://mail.gnu.org/mailman/listinfo/cons-discuss
> Cons URL: http://www.dsmit.com/cons/
>