Hi! I've downloaded boost 1.38 from the official site and successfully build it. I was able to compile the program that uses regexes. OS is FreeBSD 7.2. gcc is 4.2.1. The question is: how can I do something like this: pkg-config --libs boost-regex I'm new to FreeBSD, so I guess I really miss something basic. Googling for subject gave me a lot but not instructions how to do what I want. Thank you
Roman Shmelev wrote:
Hi! I've downloaded boost 1.38 from the official site and successfully build it. I was able to compile the program that uses regexes. OS is FreeBSD 7.2. gcc is 4.2.1.
The question is: how can I do something like this: pkg-config --libs boost-regex
I'm new to FreeBSD, so I guess I really miss something basic. Googling for subject gave me a lot but not instructions how to do what I want.
This is not possible presently. I suggest you with with --layout=system and then just use -lboost_regex - Volodya
Roman Shmelev wrote:
Thank you, Volodya!
This is not possible presently. I suggest you with with --layout=system and then just use -lboost_regex
Just to be clear - is it planned to make it possible in future releases?
We have such a ticket (hint: svn.boost.org) which was technically scheduled for 1.40 but slipped. I am not sure when it will jump to the top of queue. - Volodya
Dear community, please suggest. I try to compile Boost under EC2 (Fedora 8) the problem is: it seems to ignore --layout=system. I mean, for example created path is /usr/local/include/boost_1.39.0/ but must be /usr/local/include/boost/ ! More, it seems to not place compiled libraries to /usr/local/lib, which must be done by default. Please advice how to simply compile Boost under Fedora 8 without including version number in all folder's and file's names.
Roman Shmelev wrote:
Dear community, please suggest.
I try to compile Boost under EC2 (Fedora 8) the problem is: it seems to ignore --layout=system. I mean, for example created path is /usr/local/include/boost_1.39.0/ but must be /usr/local/include/boost/ !
This is pretty strange. Looking at the code in SVN, there's no way it can *ever* produce such a name. It can produce /usr/local/include/boost-1_39_0/ and only if using versioned layout. Are you sure you are using unmodified 1.39 source release and not version patched by the distribution?
More, it seems to not place compiled libraries to /usr/local/lib, which must be done by default.
What is the exact command line you are using? - Volodya
/usr/local/include/boost-1_39_0/
Sorry, Vladimir! Everything is just what you said. And --layout=system seems to work. The problem was in mix of versioned and unversioned libraries (I guess they were both created during the experiments) and my inattention. Once again sorry.. (I'll check in future on the fresh clean instance to ensure everything is fine)
One more :) FreeBSD: (standard install using ports, of course with thread support) libboost_filesystem Fedora 8 (EC2) : (1.38, Makefile tweaked with --layout=system) libboost_filesystem-mt questions are: Why "-mt" does not appear on FreeBSD? Probably there is a way to make gcc find itself the proper filename using prefix...?
Vladimir, answer please, you are my only hope :)
2009/7/29 Roman Shmelev
FreeBSD: (standard install using ports, of course with thread support) libboost_filesystem Fedora 8 (EC2) : (1.38, Makefile tweaked with --layout=system) libboost_filesystem-mt
questions are: Why "-mt" does not appear on FreeBSD? Probably there is a way to make gcc find itself the proper filename using prefix...?
Hi, You probably need to raise this question with Alexander Churanov, who recently updated the FreeBSD port of Boost to 1.39.0. Roman Shmelev wrote:
Vladimir, answer please, you are my only hope :)
2009/7/29 Roman Shmelev
: FreeBSD: (standard install using ports, of course with thread support) libboost_filesystem Fedora 8 (EC2) : (1.38, Makefile tweaked with --layout=system) libboost_filesystem-mt
questions are: Why "-mt" does not appear on FreeBSD? Probably there is a way to make gcc find itself the proper filename using prefix...?
Normally the libraries are built with multithreading support by default, as FreeBSD ships with POSIX threads enabled; however, this is a configurable option in the port itself; the use of threading in the headers is controllable by preprocessor defines. thanks, BMS
participants (3)
-
Bruce Simpson
-
Roman Shmelev
-
Vladimir Prus