but do threading library even need to worry about the allocation of threads to cores. isn’t this a job of operating system? So what is the real Benifit of using TBB over Boost? You are right, a threading library usually should not care about mapping threads to cores. And TBB does not. TBB operates with … Read more
The COMPONENTS part of FIND_PACKAGE only searches for compiled libraries. It is not able to check for the header-only libraries that comprise a major part of Boost. There are only a few libraries that require linking (mostly those that perform platform-specific things). From your examples, only thread, signals (in contrast to signals2 which is header-only), … Read more
The tut3 example is what you’re looking for: See it Live on Coliru Here’s a simplified version based on c++11: Live On Coliru #include <boost/filesystem.hpp> #include <boost/range/iterator_range.hpp> #include <iostream> using namespace boost::filesystem; int main(int argc, char *argv[]) { path p(argc>1? argv[1] : “.”); if(is_directory(p)) { std::cout << p << ” is a directory containing:\n”; for(auto& … Read more
default_value() is the value that will be put in the variables_map if the user didn’t specify another value: ./a.out # implies width=75 if that’s the default_value for width ./a.out –width=80 # default_value not used implicit_value() is the value that will be used if the user specifies the option but without an adjacent value. ./a.out –width … Read more
Amit is right: boost::mutex::scoped_lock is a typedef for boost::unique_lock<boost::mutex>, not lock_guard. scoped_lock is not available in C++0x. Unless you need the flexibility of unique_lock, I would use lock_guard. It is simpler, and more clearly expresses the intent to limit the lock to a defined scope.
Read Boost Getting Started on Windows mt : multi threaded d : Add ABI tags, could be used with: g : using debug versions of the standard and runtime support libraries. s : linking statically to the standard and runtime support libraries. and more
Take a look at add_definitions, which will add your definitions to your compiler command line, e.g. -D with gcc, or /D with MSVC. Try something like: add_definitions( -DBOOST_FILESYSTEM_VERSION=2 ) In your case, I would definitely go with the add_definition method, but an alternative may to take a look at configure_file. Then you can create a … Read more
Your CMake version is too old. Update CMake and it will work. CMake cannot detect the dependencies between the different Boost libraries. They have explicitly implemented in FindBoost. For every Boost release this information is added by the CMake maintainers and it gets part of the next CMake release. So you have to make sure, … Read more
Are you sure you are doing it the correct way? The idea is that CMake sets BOOST_INCLUDE_DIR, BOOST_LIBRARYDIR and BOOST_ROOT automatically. Do something like this in CMakeLists.txt: FIND_PACKAGE(Boost) IF (Boost_FOUND) INCLUDE_DIRECTORIES(${Boost_INCLUDE_DIR}) ADD_DEFINITIONS( “-DHAS_BOOST” ) ENDIF() If boost is not installed in a default location and can, thus, not be found by CMake, you can tell … Read more
Put this in your CMakeLists.txt file (change any options from OFF to ON if you want): set(Boost_USE_STATIC_LIBS OFF) set(Boost_USE_MULTITHREADED ON) set(Boost_USE_STATIC_RUNTIME OFF) find_package(Boost 1.45.0 COMPONENTS *boost libraries here*) if(Boost_FOUND) include_directories(${Boost_INCLUDE_DIRS}) add_executable(progname file1.cxx file2.cxx) target_link_libraries(progname ${Boost_LIBRARIES}) endif() Obviously you need to put the libraries you want where I put *boost libraries here*. For example, if you’re … Read more