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

[david . weidenkopf]

Hi Nadim,

The wrong file is opened. It opens the file it compiled, which is in the "build" tree. This behavior occurs for compile errors and debugging. In the debugging scenario, you are stepping through code that is in the "build" dir. Should you find a problem and want to fix it, you don't the source file you want to change in front of you, you have a copy of it.

We are trying to avoid modifying Cons proper. But we have created our own extensions.

David

Nadim Khemir <address@hidden> Sent by: address@hidden 03/15/2002 12:24 AM

To:        "'address@hidden'" <address@hidden>         cc:        (bcc: David Weidenkopf/ATL-BTL/MS/PHILIPS)         Subject:        RE: How do I inhibit the copying of the source files to the build         tree         Classification:

> 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.

Can you be more precise? Is it that you can't get the files open or get the
wrong file opened?

>NTFS ( Win2k ) does support hardlinks for files only
True, That should do the trick.
I am also interested in getting cons to link files instead of copying them
(under win32) and I will have 
a look at it asap.

>Can anyone advise us as to whether we have any hope of getting Cons to do
what we want?
To spare you wartime with the cons gurus, Read the code and modify it. I
know that answer sucks
But it's the one I got and the one you almost always get.

>Have we made the problem clear? 
NO.

Nadim. 


_______________________________________________
address@hidden
http://mail.gnu.org/mailman/listinfo/cons-discuss
Cons URL: http://www.dsmit.com/cons/