On 08/26/2014 11:52 AM, Michael Shepanski wrote:
> On 26/08/2014 12:51 PM, Michael Shepanski wrote:
>>>> I'm probably doing something wrong, but to chase it I will need docs that I can trust.
>>> Is this reproducible with a simple project?
>> I'll have a go.
>
> I figured it out. I was trying to use project-config.jam in the top-level directory of my boost installation -- and that file wasn't being
> read. When I used project-config.jam in my /project/ directory (as the name suggests), it started working.
>
> Here's my problem. Boost.Build is my build tool of choice; I use it to build multiple projects that are not a part of boost. I need
> somewhere to put information about my computer's specific setup (which toolset, the location of third-party libraries), that will be
> available to all the builds. In the 1.55 days, I used a single user-config.jam for that purpose. How can I achieve the same result now?

Michael,

the recommended approach is to put user-config.jam in your home directory. Please refer to the table at

	http://www.boost.org/boost-build2/doc/html/bbv2/overview/configuration.html

to see what is considered a home directory on Windows.

Does this help?

- Volodya

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build