Conscript_chdir doesn't stick

Hi,

  I'm trying to get cons 2.3.0 to do my hierarchical builds. However, 
Conscript_chdir 1 appears only to apply when the Conscript files are 
processed--when it comes time to actually execute the build actions, they're 
being done back up in the Construct file directory, not the Conscript 
directory.

  Seems undesirable and confusing to process your build script w/ respect to 
one cwd, but then execute it w/ respect to another. What's the point of 
processing it in the Conscript dir in the first place then?

  -Alan

_________________________________________________________________
Persistent heartburn? Check out Digestive Health & Wellness for information 
and advice. http://gerd.msn.com/default.asp



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