# Boost :

From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2007-05-10 22:12:38

> "Rene Rivera" <grafikrobot_at_[hidden]> wrote in message
> news:46438BD5.8040901_at_gmail.com...
>> Ovanes Markarian wrote:
>>> Rene,
>>>
>>> Thanks for the answer. I copied the include from c:\boost\Include to my
>>> source control and did the same with lib directory. I solved the problem.
>>> In
>>> attachment is the list of files which were not installed via the
>>> "bjam.exe
>>> ... install" command, but after copying them manually (to my sc dir)
>>> compilation succeeded.
>>>
>>> Sure some of them are not required (I simply diff-ed the directories),
>>> but
>>> some of them were definitely missing.
>> I must this is rather depressing :-( Of course most of those missing
>> files are because authors are using "non-standard" file extensions for
>> file. This *has* to be fixed, so I'm fixing it. And since this post is
>> going to the dev list also, I'm asking lib authors to pay attention to
>> this request for info...
>
> I am sorry i am missing the context. What is not installed, where and why?

Some "header" files, in root/boost, are not copied when users run "bjam
install".

>> ** test **
>> parsetree.dtd
>
> I don't recognize this name

Oops, that's Spirit. I got confused since it's in "spirit/tree"

>> argv_traverser.cpp
>> char_parameter.cpp
>> dual_name_parameter.cpp
>> id_policy.cpp
>> named_parameter.cpp
>> parser.cpp
>> validation.cpp
>> environment.cpp
>> config_file.cpp
>> config_file_iterator.cpp
>
> This is not required at the moment by the mainstream Boost.Test. But I would
> prefer them to stay where they are - along with .hpp files

The question is, are they needed by users of Boost.Test? Hence, should
they be installed?

```--
-- Grafik - Don't Assume Anything
-- Redshift Software, Inc. - http://redshift-software.com
-- rrivera/acm.org - grafik/redshift-software.com
-- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
```