$include_dir="/home/hyper-archives/boost/include"; include("$include_dir/msg-header.inc") ?>
From: Andrey Melnikov (melnikov_at_[hidden])
Date: 2005-05-30 15:10:34
Rene Rivera wrote:
> Jeff Flinn wrote:
> 
> I'm not sure "libs", or "Libraries", or "Library Files", fits in this 
> case because we are talking about both programs(bjam, wave, etc.) and 
> libraries. And the other examples, Python, MinGW, etc. also install 
> programs. A more appropriate location would be:
> 
>     "\Development Files\Boost"
>     "\Development Files\Python"
>     "\Development Files\MinGW"
>     ...
> 
> Although the shorter "\Development\*" would probably works as well. But 
> if we are talking about such a location you need to consider language 
> localization, in the same way as "Program Files" treated.
> 
Just two more agruments  for %ProgramFiles%: On Windows %ProgramFiles% 
is more like %Packages%. Anything what is installed usually goes there. 
Even non-programs like MSDN or Platform SDK.
And root has the same access permissions like %ProgramFiles%, hasn't it? 
  On security-restricted machine the only place which is always 
write-enabled is %USERPROFILE%/%HOME%.
I agree with rest arguments against ProgramFiles, but I think that 
ProgramFiles and \libs are equally better than c:\
I wonder, if it's hardcoded c:, or %SystemDrive%?
Andrey