Re: :conf should run in $BDIR

Peter Simons wrote:

> I find myself running :conf like this
> 
>     :chdir $BDIR
>     :conf header {required} boost/spirit.hpp {language = C++}
>     :chdir -
> 
> because the compilation process will sometimes leave files
> behind, such as conftest.rpo in case of C++, and I don't
> want them to clutter up the main source. IMHO, :conf should
> do this automatically, since these tests really are platform
> dependent anyway.

Well, a configure check should not leave temp files behind in any case.
A drastic solution would be to delete all "conftest.*" files.  But that
might delete a bit too much.

Currently the directory doesn't matter, but for later checks it might
matter.  Since source files may be used in tests, changing to the $BDIR
directory doesn't seem appropriate.  The general rule is: The configure
checks should be handled just like the actual source is going to be
handled.  Thus if you always change to $BDIR when compiling a file the
configure check should do that same.

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

 /// Bram Moolenaar -- [email protected] -- 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