Re: :conf should run in $BDIR

Peter Simons wrote:

> Bram Moolenaar writes:
> 
>  >> :chdir $BDIR
>  >> :conf header {required} boost/spirit.hpp {language = C++}
>  >> :chdir -
> 
>  > Well, a configure check should not leave temp files
>  > behind in any case.
> 
> I agree! 
> 
> But that will be _very_ hard to accomplish. The *.rpo files
> generated by the C++ compiler are a good example. GCC will
> generate them, when the '-frepo' flag is given in CXXFLAGS.
> Other compilers have similar mechanisms, all of which are
> triggered by different flags (and leave different file names
> behind). Personally, I wouldn't even try to catch all those
> cases; it's a lost cause to begin with.

Doesn't this mean that compiling the actual source files also produces
these .rpo files?  Thus it's not a configure-specific problem.

> Besides, leaving result files behind allows for checking
> whether a test has to be (re-)run or not, so it's not
> necessarily a bad idea, IMHO. It's just that those files
> should be in $BDIR, not in the source directory.

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?  Although this would require
extra work to find header files that are used with #include
"myheader.h".

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