Re: :conf should run in $BDIR

Peter Simons wrote:

>  > Doesn't this mean that compiling the actual source files
>  > also produces these .rpo files?
> 
> Yes, that's right..
> 
> 
>  > Since I still think that compiling for config checks
>  > should be done the same way as compiling source files for
>  > production, perhaps a solution would be to do all
>  > compilation in $BDIR?
> 
> I would like that. I treat my source hierarchies as "read
> only" anyway, because I don't want version controlled
> directories to be cluttered up with generated files.

You could redefine the action for compiling to do a ":cd $BDIR" first.
Taking care that the argument(s) get a "../" before them.  And probably
add a "-I .." argument.

I don't think building should always be done in $BDIR, because it is not
what a first-time user would expect.

If this is a generic way to build, we could add a global setting for it
and have all the build actions use it.  You can imagine that this is a
bit of work.

--

-- 
From "know your smileys":
 *<|	Santa Claus (Ho Ho Ho)

 /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net   \\\
///          Creator of Vim - Vi IMproved -- http://www.Vim.org          \\\
\\\              Project leader for A-A-P -- http://www.A-A-P.org        ///
 \\\  Help AIDS victims, buy here: http://ICCF-Holland.org/click1.html  ///

-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click