Taylor Venable wrote:
> Hello fellow Vimmers,
>
> I noticed that you can set TCL_INC in the environment to affect where
> the TCL header files are located, but this does not impact compilation.
> I'm not sure how to go about doing so myself, so I will just suggest
> that the make rule for building if_tcl.o examines TCL_INC and adds "-I
> ${TCL_INC}" [or equivalent] to the compiler options when the value of
> TCL_INC is used by configure to find the TCL header location. This
> would prevent users from having to set both CPPFLAGS and TCL_INC to
> reflect the same place.
I generally avoid using environment variables, because they make
configuration unpredictable. Only generally accepted things like $CC
are used.
So, is $TCL_INC something that the tcl shell always uses? My manual
page for tclsh doesn't mention it.
--
Q: What is the difference betwee open-source and commercial software?
A: If you have a problem with commercial software you can call a phone
number and they will tell you it might be solved in a future version.
For open-source software there isn't a phone number to call, but you
get the solution within a day.
/// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ download, build and distribute -- http://www.A-A-P.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
