- Boost-users - lists.preview.boost.org

Build Boost 1 66
by Matt Vinson 22 Jan '18

22 Jan '18

Hello - I've been building boost with a script* (via https://studiofreya.com/2017/04/23/building-boost-1-64-with-visual-studio-2…) My Visual C++ project is a static lib so link and runtime-link are static.It's worked for several past build releases. Now with build 1_66, not all x64 libraries are built. There is 74 libraries in the win32 directory and only 27 in the x64. I locate the script using "x64 Native Tools Command Propt for VS2017" I am using Windows7. Any advice is appreciated.Matt *@echo offrem Directory to boost rootset boost_dir=boost_1_66_0 rem Number of cores to use when building boostset cores=%NUMBER_OF_PROCESSORS% rem What toolset to use when building boost. rem Visual Studio 2012 -> set msvcver=msvc-11.0rem Visual Studio 2013 -> set msvcver=msvc-12.0rem Visual Studio 2015 -> set msvcver=msvc-14.0rem Visual Studio 2017 -> set msvcver=msvc-14.1 set msvcver=msvc-14.1 rem Start building boostecho Building %boost_dir% with %cores% cores using toolset %msvcver%. cd %boost_dir%call bootstrap.bat rem Static librariesb2 -j%cores% toolset=%msvcver% address-model=64 architecture=x86 link=static threading=multi runtime-link=static --build-type=complete stage --stagedir=stage/x64 b2 -j%cores% toolset=%msvcver% address-model=32 architecture=x86 link=static threading=multi runtime-link=static --build-type=complete stage --stagedir=stage/win32 pause

2 1

Compiling Boost Libraries
by Good Guy 22 Jan '18

22 Jan '18

How do you guys compile Boost libraries in your project when all the header files are linked using angle brackets? For example in Visual Studio and C++ builder (Embarcadero) a link such as: #include <boost/config.hpp> won't compile but a link such as: #include "boost/config.hpp" Has no problems. How are we suppose to change the files so that there is no such problems. I would like to use only a few libraries in certain projects but changing the files is going to take a heck of a ling time bearing in my mind some files contains nested headers!! Am I missing something here. Surely there must a be a solution because these libraries have been going on since 1999!!

3 3

Boost sync_queue clear
by kjw 21 Jan '18

21 Jan '18

2 2

Question regarding boost binary serializer which is eating 90GB of memory, while re-reading the same content.
by dinesh kumar 21 Jan '18

21 Jan '18

Hi All, Greetings for the day. I am trying to understand the behavior of Boost's binary serializer(Boost version 1.65). Please consider the below example, where I am inserting one record into the file, and trying to read the same record 5 times. #include <boost/archive/binary_iarchive.hpp> #include <boost/archive/binary_oarchive.hpp> #include <boost/serialization/string.hpp> #include <fstream> #include <iostream> using namespace std; using namespace boost::archive; class logEntry { private: size_t m_txID; string m_jsonStr; friend class boost::serialization::access; template <typename Archive> friend void serialize( Archive &ar, logEntry &l, const unsigned int version ); public: logEntry() { m_txID = 0; m_jsonStr = ""; } logEntry( size_t id, const string &val ) { m_txID = id; m_jsonStr = val; } string getJsonValue() { return m_jsonStr; } size_t getTxId() { return m_txID; } }; template <typename Archive> void serialize( Archive &ar, logEntry &l, const unsigned int version ) { ar &l.m_txID; ar &l.m_jsonStr; } size_t prevReadPos = 0; void save( size_t n ) { ofstream file{"/tmp/test.bin", ios::binary | ios::trunc}; binary_oarchive oa{file}; // Save n records for ( int i = 0; i < n; i++ ) oa << logEntry( i, "{Some Json String}" ); file.flush(); file.close(); } // Load data batch wise void load( size_t bsize ) { ifstream file{"/tmp/test.bin", ios::binary}; binary_iarchive ia{file}; // Record file length size_t fileEnd; size_t beg = file.tellg(); file.seekg( 0, ios::end ); fileEnd = file.tellg(); file.seekg( beg, ios::beg ); logEntry l; for ( size_t i = 0; i < bsize; i++ ) { * ia >> l;* * // Reset the file read position to the beginning of the file to read the same line one more time* * file.seekg( beg, ios::beg );* } prevReadPos = file.tellg(); file.close(); } int main() { // Saving only one record save( 1 ); while ( 1 ) { // Trying to read the same record 5 times load( 5 ); sleep( 5 ); } } >From the above code, I am able to read the record one time and whenever I re-set the file pointer back to the beginning of the file, the program "Crashes with SIGKILL". And also, I observed that this process it consumed around *90GB *of memory(I got this reading from xCode while debugging the code). My dev environment is as below. clang --version Apple LLVM version 8.0.0 (clang-800.0.42.1) Target: x86_64-apple-darwin15.6.0 Thread model: posix InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin Kindly let me know if you need any more information from my side. -- Regards, Dinesh manojadinesh.blogspot.com

2 2

Google Summer of Code with Boost
by David Bellot 20 Jan '18

20 Jan '18

Hi everyone, still a few days before we submit our proposal to Google. Don't loose the chance to become a mentor for Boost. It shines on your CV, it is a great opportunity to work with brilliant students around the world, it makes you an official C++ world-wide expert. So far, we have a nice but little list of proposals here: https://github.com/boostorg/boost/wiki/Boost-Google-Summer-of-Code-2018 It would be good to have a bit more before I go and submit to Google. This will increase our chances to be selected again this year. For Boost it's a great funding worth several thousand of dollars every year. We just don't want to miss it. Best regards, David

1 0

Boost ASIO 1.66 serial port open seem to never fail opening (at least the way i'm using it)
by Mathieu Peyréga 12 Jan '18

12 Jan '18

Hello, i'm using boost asio 1.66 serial port on a Ubuntu Mate 64 machine, and I facing the fact that open("port name", error_code) command on an already openned port do not return an error. My test sequence : On the same machine I pre-open /dev/ttsS0 on minicom : minicom -D /dev/ttyS0 and check that is indeed open by sending some chars. Now while minicom still openned, I try openning a second minicom on same /dev/ttyS0 and this return an error : "device /dev/ttyS0 locked" as expected. So the device and system is able to knows that ttyS0 is already open (minicom + OS is capable of doing that) Now, with first minicom still running, if I run my program which is doing open("/dev/ttySO",ec), ec is 0 and further is-open() returns true while obviously the port is not openned. When device not already openned with minicom, my software is behaving properly. Am I doing something wrong detecting if the "open" operation suceeded ? I have a separated boost::thread io_thread(boost::bind(&C_IO_Controller::run,&theIOController)); that is running the boost::asio::io_service object the open command is called from the main thread (not the io_thread ) Regards Mathieu

3 3

Debugging into .ipp files
by Abhishek Deshpande 12 Jan '18

12 Jan '18

Hello boost users and gurus, I built boost 1.56 and client code both with -g option. When I try to debug the code, the TUI mode in GDB just wont let me navigate inside the .ipp files of boost libraries. This is a real hassle and as a work around, I generated a preprocessed output file from gcc option -E and renamed it as New.cpp file. This renamed New.cpp will have all of the template instantiations (the ones I was trying to navigate in .ipp file) of a particular boost library (e.g. serialization) embedded in it. I then compiled this New.cpp using -g and debugged it to see some miracle. But it still just doesn't navigate to places (template instantiations that are embedded inside New.cpp) . As such I am in dire need to find a way to debug these .ipp files. I hope I have made my intent clear over here. How do I debug into .ipp files using gdb ? Thanks, AD

1 0

Boost ASIO write: Socket operation on non-socket
by Sharma, Nishant 11 Jan '18

11 Jan '18

Hi, I cannot post the complete program, but when I do asio::write , I get the error: write: Socket operation on non-socket Now, just before that I check if the socket is opened or not and it indeed is opened. io_service is also running.. I just need some pointers and possible cause for this so that I can debug and take his further... My use model is I call asio::write which is synchronous and for reading I use async_read which first reads the header data and then calls asio::read to read the actual data. Best Regards, Nishant Sharma

2 1

Google Summer of Code 2018
by David Bellot 10 Jan '18

10 Jan '18

Dear Boost community, once again this year, we will apply to be a mentoring organization for the Google Summer of Code 2018. Our organization has been quite succesful for the last decade and this year we hope to be selected again. As part of filling in our application for 2018, we must supply to Google a list of potential GSoC mentors and potential GSoC projects for summer 2018 in order to be approved as an organisation this year. Therefore a lengthy page of awesome project ideas at https://svn.boost.org/trac/boost/wiki/SoC2018 before *January 23rd* would be an enormous help to getting us approved again this year and bringing to Boost another Google funding (worth dozens of thousands of dollars on average). If you think yourself able to mentor a student doing some work on Boost this summer, *please* consider adding a description of the proposed work item and your name to the list. If you want to have a better chance receiving funding for your project ideas, it is better to find good students early and that is best done by getting project ideas floated *early*. If you want to know more about mentoring a Google Summer of Code funded student work before you nominate yourself, please feel free to ask on the main Boost developers mailing list boost(a)lists.boost.org or via gsoc-admin(a)boost.org. Thank you in advance for your time. Finally, I would like to thank Niall Douglas, our previous Boost admnistrator for GSoC, who did an awesome work during many years and helped the Boost community grow thanks to all the funding we received years after years from Google. Best regards, David

1 0

1.66 changes in layout suffix seems to break cmake finder
by Stephan Menzel 09 Jan '18

09 Jan '18

Hello, I am currently trying to upgrade my projects to 1.66 and I am puzzled by a change in bjam's 'laout' parameter. I am building boost for MSVC14 (x64). Normally I use the following command line: > bjam.exe --layout=versioned variant=release address-model=64 link=static,shared runtime-link=shared threading=multi stage to achieve the build flags and setup that I need. Up until 1.65 this yielded libs named like: libboost_atomic-vc140-mt-1_65.lib This is what appears to be the most flexible for my use case and I always discover them using the 'normal' CMake finders like this: set(BOOST_ROOT ${WHERE_MY_THIRD_PARTY_STUFF_IS}/boost-1.66.0 CACHE PATH "set root of boost install") set(BOOST_INCLUDEDIR ${BOOST_ROOT}/include CACHE PATH "set boost includes") set(BOOST_LIBRARYDIR ${BOOST_ROOT}/lib CACHE PATH "set boost library dir") set(Boost_ADDITIONAL_VERSIONS "1.66.0") find_package(Boost REQUIRED COMPONENTS ...) Now over the years the meaning of the --layout parameter and its defaults have occasionally changed by I always managed to get something like this. But now, with 1.66 the filenames are changed to that: libboost_atomic-vc140-mt-x64-1_66.lib With this, CMake won't find the libs anymore. I have tried all different variantions of --layout I know (system, tagged, versioned) but I cannot get the old naming scheme back. I could rename the files manually but I am a bit afraid that this might break some linker (autolink) magick and also it doesn't seem right. Trying with several CMake finder options also got me nowhere. Using layout system is not desired as I like to quickly distinguish between versions on sight. So my question is: Is there a way to get >=1.66 to build with the filename scheme it had until now? Or is there a change to the CMake finders that will fix this? Thanks for any suggestions... Stephan

3 7