Re: How to use Command

I think if you use '#' at the beginning of a path, you can avoid the
directory linking situation and go directly to your main source tree. I
remember the docs had a function which could return an actual OS path from
a '#<relative_path>' syntax.

TTimo

On Thu, 23 Jan 2003 12:49:03 +0100
"BUFFERNE,VINCENT (HP-France,ex1)" <[email protected]> wrote:

> The point is that cons work in a build directory where it will copy the
> necessary files for the build (the necessary dependencies). So in my case,
> with no dependencies explicitly listed, I have nothing in this working
> directory and a simple "ls" will return nothing.
> I have tried as well to do my "ls" directly in my source directory (where my
> code is), but I have not found CONS variable that point to this one. I could
> specify the entire (or relative) path but I do not want to see
> "../../../dir1/dir2/" stuff in my Conscript.
> So I am still looking for the magical CONS variable that will point to the
> source directory (and not the working directory).
> 
> Sincerely,
> 
> Vincent 
> 
> -----Original Message-----
> From: Timothee Besset [mailto:[email protected]]
> Sent: Thursday, January 23, 2003 9:25 AM
> To: [email protected]
> Subject: Re: How to use Command
> 
> 
> Well you can write some perl code which generates the complete list of
> dependencies for you? Run the loop, feed it through ->Depends() ? (if I
> remember correctly)
> 
> TTimo
> 
> On Thu, 23 Jan 2003 08:50:04 +0100
> "BUFFERNE,VINCENT (HP-France,ex1)" <[email protected]> wrote:
> 
> > Hi All,
> > 
> > I am using cons to build my software. During my build I produce a shar
> file
> > with:
> > 
> > $local_env->Command("foo", qq (
> >      shar $script_dir > %>
> > )
> > );
> > 
> > This shar hundreds of files. I do not want to maintain such a huge list of
> > dependencies; it is why I have removed dependencies in "Command".
> > But if I modify one of the file that I want to shar, Cons will not detect
> > the change (as their is no dependencies) and will retrieve the shar file
> > from its cache.
> > 
> > I have found a workaround using a dummy file that I "touch" when I want to
> > force the production of a new shar file:
> > 
> > $local_env->Command("foo", "dummy_file" ,qq (
> >      shar $script_dir > %>
> > )
> > );
> > 
> > But I not really happy with it. Do you have any suggestions ???
> > 
> > Vincent
> > 
> > 
> > _______________________________________________
> > [email protected]
> > http://mail.gnu.org/mailman/listinfo/cons-discuss
> > Cons URL: http://www.dsmit.com/cons/
> > 
> 
> 
> _______________________________________________
> [email protected]
> http://mail.gnu.org/mailman/listinfo/cons-discuss
> Cons URL: http://www.dsmit.com/cons/
> 


_______________________________________________
[email protected]
http://mail.gnu.org/mailman/listinfo/cons-discuss
Cons URL: http://www.dsmit.com/cons/