problems compiling boost against visual studio 2008
first of all, hi to everyone, i´m new to boost and this is my first post i´m running windows vista x64 and visual studio 2008 i´ve followed the instructions from the "getting started" section but no good results here this is what i´ve done 1- download boost build and compile bjam 3.1.16 2- download boost 1.35 source 3- place the bjam executable in the boost1.35 main folder 4- execute bjam with these parameters first try with bjam --prefix=c:\boost --toolset=msvc install all done in the visual studio shell the compilation starts and it builds a lot of libraries and files. When i try to make my first Boost program the visual studio tells me that there is a lib missing (libboost_thread-vc90-mt-s-1_35.lib) why didn´t the VS compile this??? PS: any idea where to find links to precompiled 1.35 MSVS2005 and MSVS2008 packages???? _________________________________________________________________ MSN Video. http://video.msn.com/?mkt=es-es
the compilation starts and it builds a lot of libraries and files.
When i try to make my first Boost program the visual studio tells me that there is a lib missing
(libboost_thread-vc90-mt-s-1_35.lib)
there is a boost_thread-vc90-mt-s-1_35.lib -- just create a symbolic link to libboost_thread-vc90-mt-s-1_35.lib -- yes Vista can finally create symbolic links Peter
i was already testing this little tutorial when you answered http://www.quantnet.org/forum/showthread.php?t=2221&page=2 i wasn´t interested in Quantlib, just the 1.35 boost compilation and it works now. This explanation is really simple and helped me a lot to get everything compiled and running without having to read a lot of documentation. I guess something like this should be in the boost web... thank you anyway cheers ;) Date: Thu, 15 May 2008 16:46:55 -0600 From: peter_foelsche@agilent.com To: boost-users@lists.boost.org Subject: Re: [Boost-users] problems compiling boost against visual studio 2008
the compilation starts and it builds a lot of libraries and files.
When i try to make my first Boost program the visual studio tells me that there is a lib missing
(libboost_thread-vc90-mt-s-1_35.lib)
there is a boost_thread-vc90-mt-s-1_35.lib -- just create a symbolic link to libboost_thread-vc90-mt-s-1_35.lib -- yes Vista can finally create symbolic links Peter _________________________________________________________________ Tecnología, moda, motor, viajes,…suscríbete a nuestros boletines para estar siempre a la última http://newsletters.msn.com/hm/maintenanceeses.asp?L=ES&C=ES&P=WCMaintenance&Brand=WL&RU=http%3a%2f%2fmail.live.com
1. I download the 1.35 .tar.bz2 file. 2. untar it within cygwin 3. copy the folder onto c;\ 4. inside cygwin, navigate to c:\boost\tools\jam\src 5. ./build.sh gcc to build the bjam.exe 6. copy the bjam.exe from c:\boost\tools\jam\src\bin.cygwinx86 to c:\boost 7. navigate back to c;\boost\ 8. type "./bjam --build-dir=boost-binary --boolset=gcc stage" to build boost 9. after a while, the result are as following: ...failed updateing 13 targets ... ...skipped 13 targets ... ...updated 288 targets ... I successfully built it on linux without any failure. any comments? thanks, James
failed targets are probably the ones with unicode which is not supported on windows. I never get all targets built but it still works very fine. To get more info, add "-d2" on the command line of bjam and redirect ouput to a file ">& mylog.txt" Fred boost-users-bounces@lists.boost.org a écrit sur 20/05/2008 23:02:24 :
1. I download the 1.35 .tar.bz2 file. 2. untar it within cygwin 3. copy the folder onto c;\ 4. inside cygwin, navigate to c:\boost\tools\jam\src 5. ./build.sh gcc to build the bjam.exe 6. copy the bjam.exe from c:\boost\tools\jam\src\bin.cygwinx86 to c:\boost 7. navigate back to c;\boost\ 8. type "./bjam --build-dir=boost-binary --boolset=gcc stage" to build boost 9. after a while, the result are as following: ...failed updateing 13 targets ... ...skipped 13 targets ... ...updated 288 targets ...
I successfully built it on linux without any failure.
any comments?
thanks,
James
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
Avis : Ce message et toute pièce jointe sont la propriété d'Alcan et sont destinés seulement aux personnes ou à l'entité à qui le message est adressé. Si vous avez reçu ce message par erreur, veuillez le détruire et en aviser l'expéditeur par courriel. Si vous n'êtes pas le destinataire du message, vous n'êtes pas autorisé à utiliser, à copier ou à divulguer le contenu du message ou ses pièces jointes en tout ou en partie. Notice: This message and any attachments are the property of Alcan and are intended solely for the named recipients or entity to whom this message is addressed. If you have received this message in error please inform the sender via e-mail and destroy the message. If you are not the intended recipient you are not allowed to use, copy or disclose the contents or attachments in whole or in part.
Ok, I found why the build was failed. there are two errors: 1. libs\serialization\src\basic_text_wiprimitive.cpp:14:2: #error "wide char i/o not supported on this platform" 2. libs\iostreams\src\bzip2.cpp:19:56: bzlib.h: No such file or directory Anybody can help me about this? I am using latest Cygwin with default packages install on a Windows XP machine. thanks, --- frederic.bron@alcan.com wrote:
failed targets are probably the ones with unicode which is not supported on windows. I never get all targets built but it still works very fine. To get more info, add "-d2" on the command line of bjam and redirect ouput to a file ">& mylog.txt"
Fred
boost-users-bounces@lists.boost.org a écrit sur 20/05/2008 23:02:24 :
1. I download the 1.35 .tar.bz2 file. 2. untar it within cygwin 3. copy the folder onto c;\ 4. inside cygwin, navigate to c:\boost\tools\jam\src 5. ./build.sh gcc to build the bjam.exe 6. copy the bjam.exe from c:\boost\tools\jam\src\bin.cygwinx86 to c:\boost 7. navigate back to c;\boost\ 8. type "./bjam --build-dir=boost-binary --boolset=gcc stage" to build boost 9. after a while, the result are as following: ...failed updateing 13 targets ... ...skipped 13 targets ... ...updated 288 targets ...
I successfully built it on linux without any failure.
any comments?
thanks,
James
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org
http://lists.boost.org/mailman/listinfo.cgi/boost-users
Avis : Ce message et toute pièce jointe sont la propriét?>
?l'entit??qui le message est adress? Si vous avez reçu ce message par erreur, veuillez le détruire et en aviser l'expéditeur par courriel. Si vous n'êtes pas le destinataire du message, vous n'êtes pas autoris??utiliser, ?copier ou ?>
d'Alcan et sont destinés seulement aux personnes ou divulguer le contenu du message ou ses pièces
jointes en tout ou en partie.
Notice: This message and any attachments are the property of Alcan and are intended solely for the named recipients or entity to whom this message is addressed. If you have received this message in error please inform the sender via e-mail and destroy the message. If you are not the intended recipient you are not allowed to use, copy or disclose the contents or attachments in whole or in part.
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org
1. libs\serialization\src\basic_text_wiprimitive.cpp:14:2: #error "wide char i/o not supported on this platform"
This is the unicode stuff which is not supported on windows gcc/g++
2. libs\iostreams\src\bzip2.cpp:19:56: bzlib.h: No such file or directory
You need to add -sNO_BZIP2=1 on the bjam command line (skip it if you do not need it) or -sBZIP2_INCLUDE=path/to/bzip2/include -sBZIP2_LIBPATH=/path/to/bzip2/lib Personnaly, I compile bzip2 from source but it should be possible to include the one provided by cygwin. (Same for zlib: -sNO_ZLIB=1) Fred Avis : Ce message et toute pièce jointe sont la propriété d'Alcan et sont destinés seulement aux personnes ou à l'entité à qui le message est adressé. Si vous avez reçu ce message par erreur, veuillez le détruire et en aviser l'expéditeur par courriel. Si vous n'êtes pas le destinataire du message, vous n'êtes pas autorisé à utiliser, à copier ou à divulguer le contenu du message ou ses pièces jointes en tout ou en partie. Notice: This message and any attachments are the property of Alcan and are intended solely for the named recipients or entity to whom this message is addressed. If you have received this message in error please inform the sender via e-mail and destroy the message. If you are not the intended recipient you are not allowed to use, copy or disclose the contents or attachments in whole or in part.
We tried to build boost binary library to be used in our projects on Windows and Linux. We have successfully built v1.35 on linux. But we cannot built it without any error on Cygwin and MinGW. We got the same result on Cygwin and MinGW: libs\serialization\src\basic_text_wiprimitive.cpp:14:2: #error "wide char i/o not supported on this platform" . . . ...failed updating 12 targets... ...skipped 8 targets... ...updated 255 targets... My questions here are followed: 1. Does serialization must be built before we use it? the doc says it must be built separately. does that serialization is this one we failed? 2. With those failed targets, can we still use the built binary result? thanks, James
Am Freitag 23 Mai 2008 16:36:56 schrieb Longyu Mei:
We tried to build boost binary library to be used in our projects on Windows and Linux.
We have successfully built v1.35 on linux. But we cannot built it without any error on Cygwin and MinGW.
We got the same result on Cygwin and MinGW: libs\serialization\src\basic_text_wiprimitive.cpp:14:2: #error "wide char i/o not supported on this platform" . . . ...failed updating 12 targets... ...skipped 8 targets... ...updated 255 targets...
What is the gcc version of your mingw installation? Mingw-gcc--3.x doesn't support wide characters. -- Maik
My MinGW is the latest 5.1.4. Do you mean I need to download the GCC Version 4 to replace the gcc come with MinGW 5.1.4? I believe that gcc is version 3.4.5. --- Maik Beckmann <beckmann.maik@googlemail.com> wrote:
Am Freitag 23 Mai 2008 16:36:56 schrieb Longyu Mei:
We tried to build boost binary library to be used in our projects on Windows and Linux.
We have successfully built v1.35 on linux. But we cannot built it without any error on Cygwin and MinGW.
We got the same result on Cygwin and MinGW:
libs\serialization\src\basic_text_wiprimitive.cpp:14:2:
#error "wide char i/o not supported on this platform" . . . ...failed updating 12 targets... ...skipped 8 targets... ...updated 255 targets...
What is the gcc version of your mingw installation? Mingw-gcc--3.x doesn't support wide characters.
-- Maik _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org
After using GCC4.3 instead of the default gcc 3.* with MinGW, I have the following four failures. Anybody can give me some advices? 1. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -mthreads -DBOOST_ALL_NO_LIB=1 -DBOOST_TEST_DYN_LINK=1 -DNDEBUG -I"." -c -o "my_binary\boost\bin.v2\libs\test\build\gcc-mingw-4.3.0\release\threading-multi\debug.o" "libs\test\src\debug.cpp" ...failed gcc.compile.c++ my_binary\boost\bin.v2\libs\test\build\gcc-mingw-4.3.0\release\threading-multi\debug.o... 2. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -mthreads -DBOOST_ALL_NO_LIB=1 -DNDEBUG -I"." -c -o "my_binary\boost\bin.v2\libs\test\build\gcc-mingw-4.3.0\release\link-static\threading-multi\debug.o" "libs\test\src\debug.cpp" ...failed gcc.compile.c++ my_binary\boost\bin.v2\libs\test\build\gcc-mingw-4.3.0\release\link-static\threading-multi\debug.o... 3. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -mthreads -DBOOST_ALL_DYN_LINK=1 -DBOOST_ALL_NO_LIB=1 -DNDEBUG -I"." -c -o "my_binary\boost\bin.v2\libs\wave\build\gcc-mingw-4.3.0\release\threading-multi\instantiate_cpp_grammar.o" "libs\wave\src\instantiate_cpp_grammar.cpp" ...failed gcc.compile.c++ my_binary\boost\bin.v2\libs\wave\build\gcc-mingw-4.3.0\release\threading-multi\instantiate_cpp_grammar.o... 4. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -mthreads -DBOOST_ALL_DYN_LINK=1 -DBOOST_ALL_NO_LIB=1 -DNDEBUG -I"." -c -o "my_binary\boost\bin.v2\libs\wave\build\gcc-mingw-4.3.0\release\threading-multi\instantiate_predef_macros.o" "libs\wave\src\instantiate_predef_macros.cpp" ...failed gcc.compile.c++ my_binary\boost\bin.v2\libs\wave\build\gcc-mingw-4.3.0\release\threading-multi\instantiate_predef_macros.o... ...failed updating 4 targets... ...skipped 19 targets... ...updated 252 targets... Thanks, James --- Maik Beckmann <beckmann.maik@googlemail.com> wrote:
Am Freitag 23 Mai 2008 16:36:56 schrieb Longyu Mei:
We tried to build boost binary library to be used in our projects on Windows and Linux.
We have successfully built v1.35 on linux. But we cannot built it without any error on Cygwin and MinGW.
We got the same result on Cygwin and MinGW:
libs\serialization\src\basic_text_wiprimitive.cpp:14:2:
#error "wide char i/o not supported on this platform" . . . ...failed updating 12 targets... ...skipped 8 targets... ...updated 255 targets...
What is the gcc version of your mingw installation? Mingw-gcc--3.x doesn't support wide characters.
-- Maik _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org
Am Freitag 23 Mai 2008 19:39:56 schrieb Longyu Mei:
After using GCC4.3 instead of the default gcc 3.* with MinGW, I have the following four failures.
Anybody can give me some advices?
1. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -mthreads -DBOOST_ALL_NO_LIB=1 -DBOOST_TEST_DYN_LINK=1 -DNDEBUG -I"." -c -o "my_binary\boost\bin.v2\libs\test\build\gcc-mingw-4.3.0\release\threading-m ulti\debug.o" "libs\test\src\debug.cpp"
...failed gcc.compile.c++ my_binary\boost\bin.v2\libs\test\build\gcc-mingw-4.3.0\release\threading-mu lti\debug.o...
2. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -mthreads -DBOOST_ALL_NO_LIB=1 -DNDEBUG -I"." -c -o "my_binary\boost\bin.v2\libs\test\build\gcc-mingw-4.3.0\release\link-static \threading-multi\debug.o" "libs\test\src\debug.cpp"
...failed gcc.compile.c++ my_binary\boost\bin.v2\libs\test\build\gcc-mingw-4.3.0\release\link-static\ threading-multi\debug.o...
3. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -mthreads -DBOOST_ALL_DYN_LINK=1 -DBOOST_ALL_NO_LIB=1 -DNDEBUG -I"." -c -o "my_binary\boost\bin.v2\libs\wave\build\gcc-mingw-4.3.0\release\threading-m ulti\instantiate_cpp_grammar.o" "libs\wave\src\instantiate_cpp_grammar.cpp"
...failed gcc.compile.c++ my_binary\boost\bin.v2\libs\wave\build\gcc-mingw-4.3.0\release\threading-mu lti\instantiate_cpp_grammar.o...
4. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -mthreads -DBOOST_ALL_DYN_LINK=1 -DBOOST_ALL_NO_LIB=1 -DNDEBUG -I"." -c -o "my_binary\boost\bin.v2\libs\wave\build\gcc-mingw-4.3.0\release\threading-m ulti\instantiate_predef_macros.o" "libs\wave\src\instantiate_predef_macros.cpp"
...failed gcc.compile.c++ my_binary\boost\bin.v2\libs\wave\build\gcc-mingw-4.3.0\release\threading-mu lti\instantiate_predef_macros.o...
...failed updating 4 targets... ...skipped 19 targets... ...updated 252 targets...
Thanks,
These infos are not enough, because you left out the error messages. However, neither boost-1.35.0 nor boost trunk is read for gcc-4.3. Most problems are minor, like a missing cstring, climits.. includes. When I get my head around the other stuff I'm doing at the moment, I'll do a big attach and spam the bug tracker. -- Maik PS: Robert, do you remember the fix for boost.serialization I sent you a month ago?
I searched my log file. There was no error message. --- Maik Beckmann <beckmann.maik@googlemail.com> wrote:
Am Freitag 23 Mai 2008 19:39:56 schrieb Longyu Mei:
After using GCC4.3 instead of the default gcc 3.* with MinGW, I have the following four failures.
Anybody can give me some advices?
1. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -mthreads -DBOOST_ALL_NO_LIB=1 -DBOOST_TEST_DYN_LINK=1 -DNDEBUG -I"." -c -o
"my_binary\boost\bin.v2\libs\test\build\gcc-mingw-4.3.0\release\threading-m
ulti\debug.o" "libs\test\src\debug.cpp"
...failed gcc.compile.c++
my_binary\boost\bin.v2\libs\test\build\gcc-mingw-4.3.0\release\threading-mu
lti\debug.o...
2. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -mthreads -DBOOST_ALL_NO_LIB=1 -DNDEBUG -I"." -c -o
"my_binary\boost\bin.v2\libs\test\build\gcc-mingw-4.3.0\release\link-static
\threading-multi\debug.o" "libs\test\src\debug.cpp"
...failed gcc.compile.c++
my_binary\boost\bin.v2\libs\test\build\gcc-mingw-4.3.0\release\link-static\
threading-multi\debug.o...
3. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -mthreads -DBOOST_ALL_DYN_LINK=1 -DBOOST_ALL_NO_LIB=1 -DNDEBUG -I"." -c -o
"my_binary\boost\bin.v2\libs\wave\build\gcc-mingw-4.3.0\release\threading-m
ulti\instantiate_cpp_grammar.o" "libs\wave\src\instantiate_cpp_grammar.cpp"
...failed gcc.compile.c++
my_binary\boost\bin.v2\libs\wave\build\gcc-mingw-4.3.0\release\threading-mu
lti\instantiate_cpp_grammar.o...
4. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -mthreads -DBOOST_ALL_DYN_LINK=1 -DBOOST_ALL_NO_LIB=1 -DNDEBUG -I"." -c -o
"my_binary\boost\bin.v2\libs\wave\build\gcc-mingw-4.3.0\release\threading-m
ulti\instantiate_predef_macros.o" "libs\wave\src\instantiate_predef_macros.cpp"
...failed gcc.compile.c++
my_binary\boost\bin.v2\libs\wave\build\gcc-mingw-4.3.0\release\threading-mu
lti\instantiate_predef_macros.o...
...failed updating 4 targets... ...skipped 19 targets... ...updated 252 targets...
Thanks,
These infos are not enough, because you left out the error messages.
However, neither boost-1.35.0 nor boost trunk is read for gcc-4.3. Most problems are minor, like a missing cstring, climits.. includes.
When I get my head around the other stuff I'm doing at the moment, I'll do a big attach and spam the bug tracker.
-- Maik
PS: Robert, do you remember the fix for boost.serialization I sent you a month ago?
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org
do you need the entire log file? If yes, how can I give to you? --- Steven Watanabe <watanabesj@gmail.com> wrote:
AMDG
Longyu Mei wrote:
I searched my log file. There was no error message.
They should have been sent to the standard error. Did you only look at the standard output?
In Christ, Steven Watanabe
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org
Started with asio tutorial from boost 1.35. Copied the second timer code but cannot compile it. In the same setting, I compiled and run an example from boost. Following is the first 3 errors: g++ -g -Wall -I. -I./include -I/home/lmei/work/boostlib/boost_1_35_0 ./timer.cpp -o timer /tmp/ccKOni8q.o: In function `__static_initialization_and_destruction_0':/home/lmei/work/boostlib/boost_1_35_0/boost/system/error_code.hpp:204: undefined reference to `boost::system::get_system_category()' :/home/lmei/work/boostlib/boost_1_35_0/boost/system/error_code.hpp:205: undefined reference to `boost::system::get_posix_category()' :/home/lmei/work/boostlib/boost_1_35_0/boost/system/error_code.hpp:209: undefined reference to `boost::system::get_posix_category()' :/home/lmei/work/boostlib/boost_1_35_0/boost/system/error_code.hpp:210: undefined reference to `boost::system::get_system_category()' please help. thanks
On linux you need to link to -lboost_system-gcc32-mt. Also, you will need to supply the path to library using -L /home/foo/boost/lib man g++ (it's a good ref.) -----Original Message----- From: boost-users-bounces@lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Longyu Mei Sent: Friday, May 23, 2008 3:10 PM To: boost-users@lists.boost.org Subject: [Boost-users] boost 1.35 asio sample compile error Started with asio tutorial from boost 1.35. Copied the second timer code but cannot compile it. In the same setting, I compiled and run an example from boost. Following is the first 3 errors: g++ -g -Wall -I. -I./include -I/home/lmei/work/boostlib/boost_1_35_0 ./timer.cpp -o timer /tmp/ccKOni8q.o: In function `__static_initialization_and_destruction_0':/home/lmei/work/boostlib/boo st_1_35_0/boost/system/error_code.hpp:204: undefined reference to `boost::system::get_system_category()' :/home/lmei/work/boostlib/boost_1_35_0/boost/system/error_code.hpp:205: undefined reference to `boost::system::get_posix_category()' :/home/lmei/work/boostlib/boost_1_35_0/boost/system/error_code.hpp:209: undefined reference to `boost::system::get_posix_category()' :/home/lmei/work/boostlib/boost_1_35_0/boost/system/error_code.hpp:210: undefined reference to `boost::system::get_system_category()' please help. thanks _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - This message is intended only for the personal and confidential use of the designated recipient(s) named above. If you are not the intended recipient of this message you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited. This communication is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any financial product, an official confirmation of any transaction, or as an official statement of Lehman Brothers. Email transmission cannot be guaranteed to be secure or error-free. Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such. All information is subject to change without notice. -------- IRS Circular 230 Disclosure: Please be advised that any discussion of U.S. tax matters contained within this communication (including any attachments) is not intended or written to be used and cannot be used for the purpose of (i) avoiding U.S. tax related penalties or (ii) promoting, marketing or recommending to another party any transaction or matter addressed herein.
After I built boost in Linux, I found in the lib directory there are three files for each package. For example, for system, files are libboost_system-gcc41-mt-1_35.so libboost_system-gcc41-mt-1_35.so.1.35.0 libboost_system-gcc41-mt.so Why is that? Only one file is needed in my link flag? which one? thanks, James
Longyu Mei wrote:
After I built boost in Linux, I found in the lib directory there are three files for each package. For example, for system, files are
libboost_system-gcc41-mt-1_35.so libboost_system-gcc41-mt-1_35.so.1.35.0 libboost_system-gcc41-mt.so
Why is that? Only one file is needed in my link flag? which one?
They are typically linked to each other (there is only one 'real' file - the others are pointers with different names. listing with 'ls -l' shows more detail: lrwxrwxrwx 1 root root 25 2008-02-24 17:06 libboost_thread.so -> libboost_thread.so.1.33.1 -rwxr-xr-x 1 root root 45508 2008-01-17 11:02 libboost_thread.so.1.33.1 lrwxrwxrwx 1 root root 25 2008-02-24 17:03 libboost_thread.so.2 -> libboost_thread.so.1.33.1 This allows you to include the libboost_thread.so file in your build and when you upgrade to a new version, the specific version of the file does not need to be changed in your build file (ie. you can keep referring to libboost_thread.so even though it may now link to libboost_thread.so.1.34.1) Another point you might not be aware of is that when you link to a library file, depending on the platform, there may be some prefix or suffix added by the compiler - specifically, on linux, the "lib" is prefixed and ".so" suffixed so you would include the following in your build file: -l boost_system-gcc41-mt (I confess that since I don't have the "-gcc41-mt" part in my build, I've assumed that is necessary) In my Makefile, I have "-l boost_thread" which the linker translates into libboost_thread.so which in turn is linked by the OS to libboost_thread.so.1.33.1
thanks, James
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
So, I have to generate a few template class specialisation that look like that : template<size_t I,size_t O, size_t M> class foo; template<> class foo<4,0,0> {}; template<> class foo<3,1,0> {}; template<> class foo<3,0,1> {}; template<> class foo<0,3,1> {}; template<> class foo<0,1,3> {}; ... template<> class foo<1,1,2> {}; and so on for all combination of I,O,M so that M+I+O = N (N = 4 in this example). So I decided to use BOOST_PP to generate those specialisation for arbirary values of N and to test the way I can enumerate the sets of value, I wrote the following code : #define MAX_VAL 11 #define L1 (0, (1, (2, (3, (4, (5, (6, (7, (8, (9, (10, (11, BOOST_PP_NIL)))))))))))) #define NOP(p) #define ADD(p) BOOST_PP_ADD( BOOST_PP_TUPLE_ELEM(3,0,p), BOOST_PP_ADD(BOOST_PP_TUPLE_ELEM(3,1,p),BOOST_PP_TUPLE_ELEM(3,2,p))) #define PRT(p) cout << BOOST_PP_TUPLE_ELEM(3,0,p) << " " << BOOST_PP_TUPLE_ELEM(3,1,p) << " " << BOOST_PP_TUPLE_ELEM(3,2,p) << endl; #define DO(r, p) BOOST_PP_IF(BOOST_PP_EQUAL(ADD(p),MAX_VAL),PRT,NOP)(p) int main() { BOOST_PP_LIST_FOR_EACH_PRODUCT(DO, 3, (L1, L1, L1)) return 0; } that use cout to display the values triplet. This works nice but it is somehow slow for larger value of MAX_VAL and cumbersome to extand cause of the list. Is there anyway I can produce the same code using a better PP code ? Thanks in advance -- Joel FALCOU Research Engineer @ Institut d'Electronique Fondamentale Université PARIS SUD XI France
AMDG Joel FALCOU wrote:
This works nice but it is somehow slow for larger value of MAX_VAL and cumbersome to extand cause of the list.
How large a MAX_VAL? at 11 you are already generating 1296 specializations.
Is there anyway I can produce the same code using a better PP code ?
I personally prefer SEQ to LIST... (0)(1)(2)(3)(4)(5)(6)(7)(8)(9) In Christ, Steven Watanabe
Steven Watanabe a écrit :
How large a MAX_VAL? at 11 you are already generating 1296 specializations. MAX_VAL should be able to go up to 15 for a total of 136 specialisation as number of combination of A,B,C so that A+B+C=K seems to be (K+1)(K+2)/2
But indeed I generate 16*16*16 instanciation of some PP macros, which si friggin large.
I personally prefer SEQ to LIST... (0)(1)(2)(3)(4)(5)(6)(7)(8)(9) Indeed, I missed BOOST_PP_SEQ_FOR_EACH_PRODUCT
-- Joel FALCOU Research Engineer @ Institut d'Electronique Fondamentale Université PARIS SUD XI France
AMDG Joel FALCOU wrote:
MAX_VAL should be able to go up to 15 for a total of 136 specialisation as number of combination of A,B,C so that A+B+C=K seems to be (K+1)(K+2)/2
But indeed I generate 16*16*16 instanciation of some PP macros, which si friggin large.
I see. You might be able to get away with using nested BOOST_PP_REPEATs You're limited to three levels so be careful. In Christ, Steven Watanabe
Steven Watanabe a écrit :
I see. You might be able to get away with using nested BOOST_PP_REPEATs You're limited to three levels so be careful.
How exactly can I pass the iteration count of one PP_REPEAT to another ? -- Joel FALCOU Research Engineer @ Institut d'Electronique Fondamentale Université PARIS SUD XI France
AMDG Joel FALCOU wrote:
Steven Watanabe a écrit :
I see. You might be able to get away with using nested BOOST_PP_REPEATs You're limited to three levels so be careful.
How exactly can I pass the iteration count of one PP_REPEAT to another ?
#include <boost/preprocessor/repetition/repeat.hpp> #include <boost/preprocessor/arithmetic/sub.hpp> #include <boost/preprocessor/arithmetic/add.hpp> #include <boost/preprocessor/arithmetic/inc.hpp> #define SUM 16 #define INNER_LOOP(z, n, data) template<> test<data, n, BOOST_PP_SUB(SUM, BOOST_PP_ADD(n, data))>; #define OUTER_LOOP(z, n, data) BOOST_PP_REPEAT_ ## z(BOOST_PP_INC(BOOST_PP_SUB(SUM, n)), INNER_LOOP, n) BOOST_PP_REPEAT(BOOST_PP_INC(SUM), OUTER_LOOP, ~) In Christ, Steven Watanabe
Do you have a schedule about this? --- Maik Beckmann <beckmann.maik@googlemail.com> wrote:
These infos are not enough, because you left out the error messages.
However, neither boost-1.35.0 nor boost trunk is read for gcc-4.3. Most problems are minor, like a missing cstring, climits.. includes.
When I get my head around the other stuff I'm doing at the moment, I'll do a big attach and spam the bug tracker.
-- Maik
PS: Robert, do you remember the fix for boost.serialization I sent you a month ago?
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org
Hello, try ./bjam --build-dir=boost-binary --toolset=gcc <threading>multi <target-os>cygwin <threadapi>pthread There is a thread in boost dev and on boost build related to this issue. The problem seams to be related to the fact that cygwin is seen as a cross-compiler and so you need target-os. Good luck ____________________ Vicente Juan Botet Escriba ----- Original Message ----- From: "Longyu Mei" <lmei007@yahoo.com> To: <boost-users@lists.boost.org> Sent: Tuesday, May 20, 2008 11:02 PM Subject: [Boost-users] cannot build v1.35 on cygwin
1. I download the 1.35 .tar.bz2 file. 2. untar it within cygwin 3. copy the folder onto c;\ 4. inside cygwin, navigate to c:\boost\tools\jam\src 5. ./build.sh gcc to build the bjam.exe 6. copy the bjam.exe from c:\boost\tools\jam\src\bin.cygwinx86 to c:\boost 7. navigate back to c;\boost\ 8. type "./bjam --build-dir=boost-binary --boolset=gcc stage" to build boost 9. after a while, the result are as following: ...failed updateing 13 targets ... ...skipped 13 targets ... ...updated 288 targets ...
I successfully built it on linux without any failure.
any comments?
thanks,
James
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
tried ./bjam --build-dir=boost-binary --toolset=gcc <threading>multi <target-os>cygwin <threadapi>pthread but the result is bash: threading: No such file or directory I look at the options on bjam, there is no option named threading, target-os and threadapi. So bjam just cannot recongnize them. thanks, --- "vicente.botet" <vicente.botet@wanadoo.fr> wrote:
Hello,
try ./bjam --build-dir=boost-binary --toolset=gcc <threading>multi <target-os>cygwin <threadapi>pthread
There is a thread in boost dev and on boost build related to this issue. The problem seams to be related to the fact that cygwin is seen as a cross-compiler and so you need target-os.
Good luck
____________________ Vicente Juan Botet Escriba
----- Original Message ----- From: "Longyu Mei" <lmei007@yahoo.com> To: <boost-users@lists.boost.org> Sent: Tuesday, May 20, 2008 11:02 PM Subject: [Boost-users] cannot build v1.35 on cygwin
1. I download the 1.35 .tar.bz2 file. 2. untar it within cygwin 3. copy the folder onto c;\ 4. inside cygwin, navigate to c:\boost\tools\jam\src 5. ./build.sh gcc to build the bjam.exe 6. copy the bjam.exe from c:\boost\tools\jam\src\bin.cygwinx86 to c:\boost 7. navigate back to c;\boost\ 8. type "./bjam --build-dir=boost-binary --boolset=gcc stage" to build boost 9. after a while, the result are as following: ...failed updateing 13 targets ... ...skipped 13 targets ... ...updated 288 targets ...
I successfully built it on linux without any failure.
any comments?
thanks,
James
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org
http://lists.boost.org/mailman/listinfo.cgi/boost-users
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org
Longyu Mei wrote:
tried
./bjam --build-dir=boost-binary --toolset=gcc <threading>multi <target-os>cygwin <threadapi>pthread
but the result is bash: threading: No such file or directory
I look at the options on bjam, there is no option named threading, target-os and threadapi. So bjam just cannot recongnize them.
The command should have been: ./bjam --build-dir=boost-binary --toolset=gcc threading=multi target-os=cygwin threadapi=pthread -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org (msn) - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim,yahoo,skype,efnet,gmail
You are right. But the result is almost the same. 1. #error "wide char i/o not supported on this platform" 2. libs\iostreams\src\bzip2.cpp:19:56: bzlib.h: No such file or directory thanks, --- Rene Rivera <grafikrobot@gmail.com> wrote:
Longyu Mei wrote:
tried
./bjam --build-dir=boost-binary --toolset=gcc <threading>multi <target-os>cygwin <threadapi>pthread
but the result is bash: threading: No such file or directory
I look at the options on bjam, there is no option named threading, target-os and threadapi. So bjam just cannot recongnize them.
The command should have been:
./bjam --build-dir=boost-binary --toolset=gcc threading=multi target-os=cygwin threadapi=pthread
-- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org (msn) - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim,yahoo,skype,efnet,gmail
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org
participants (12)
-
David _ -
frederic.bron＠alcan.com -
Joel FALCOU -
Khandelwal, Amit -
Longyu Mei -
Maik Beckmann -
Mathieu Champlon -
peter_foelsche＠agilent.com -
Rene Rivera -
Rupert Bruce -
Steven Watanabe -
vicente.botet