First, compile
Run the. Bat Build Bjam.exe
Run: Bjam--build-type=complete TOOLSET=GCC Stage
Second, the configuration
Configure Eclipse-l
Path joins the link library location
http://blog.csdn.NET/caroline_wendy/article/details/17282187
Seed_rng.hpp:242:20:error: ' WINAPI ' in namespace ' boost::d etail ' does not name a type
Boost::d etail::winapi::hcryptprov_ random_;
WORKAROUND: boost_1_59_0\boost\uuid\seed_rng.hpp:41#if defined (_msc_ver) is modified to #if defined (boost_windows) 1. Windows
Window->preferences->c/c++->new CDT Project Wizard->makefile Project
Find Binary Parser Cancel Elf Parser re-election PE Windows Parser.
2. Linux
Window->preferences->c/c++->new CDT Project Wizard->makefile Project
Find Binary Parser Select Elf Parser.
Note that if Makefile project, the specific solution is to create a new project, select Makefile project->next->advanced settings, tick generate makefiles automatically.
3.
After the configuration is completed to establish the project test, found to build the Hello World C + + project types of projects can run tests, directly establish an empty project write a test class can not run, prompted "launch failed." Binary not found ".
Cause: In the CDT after each new project is completed, the system will generally be built by default for the first time, that is, automatically generate the executable file. But the fact is that we don't even have a source file in our new project, so of course we won't be able to generate executable files. When we create a new source file, clicking the Execute button pops up the word "launch failed." Binary not Found "hint description (Cannot find a binary file that can be run).
Workaround: Right-click on the project folder on the left side of the window, select Build configurations--->build-->select in the popup menu, select Debug or Release to build.
At this time will appear binaries under the XXX.exe, and then go to run it.
Eclipse+mingw+boost Environment Construction
