[cfe-dev] clang and boost
Richard Smith
richard at metafoo.co.uk
Tue Nov 13 23:12:10 PST 2012
On Tue, Nov 13, 2012 at 5:42 PM, lis <li_shao1 at hotmail.com> wrote:
> I am new to Clang. I try to use clang-2.9-mingw to build Boost_1_52_0. One
> problem I have is that $(Includes) is not set when build with bjam. I tried
> to workaround that by modifying clang-linux.jam to hard-code the include
> path.
>
> actions compile.c++.without-pth {
> "$(CONFIG_COMMAND)" -c -x c++ $(OPTIONS) $(USER_OPTIONS) -D$(DEFINES)
> -I"C:\boost_1_52_0\boost_1_52_0\boost\compatibility\cpp_c_headers"
> -I"C:\boost_1_52_0\boost_1_52_0" -I"C:\boost_1_52_0\boost_1_52_0\boost"
> -I"C:\boost_1_52_0\boost_1_52_0\boost\tr1\tr1" -o "$(<)" "$(>)"
> }
>
> This helped to get around some of the include path issues but I stuck with
> the following message:
>
> In file included from C:\boost_1_52_0\boost_1_52_0\boost\tr1\tr1/utility:19:
> C:\boost_1_52_0\boost_1_52_0/boost/tr1/detail/config_all.hpp:161:12: fatal
> error
> : '../include/utility' file not found
> # include BOOST_TR1_STD_HEADER(utility)
> ^
> C:\boost_1_52_0\boost_1_52_0/boost/tr1/detail/config_all.hpp:83:41: note:
> instantiated from:
> # define BOOST_TR1_STD_HEADER(name) <../include/name>
>
> My question is: What do I need to do to get Clang to set up the include path
> correctly?
I'm not sure what the problem is, but you should use a newer version
of Clang. Clang development moves fast, and version 2.9 is now very
far behind in terms of language support.
More information about the cfe-dev
mailing list