From: Patrick H. <pa...@in...> - 2004-07-30 12:50:37
|
Raymond de Vries wrote: > Hi > > >>> In Linux: >>> >>> checking for boost::filesystem::exists() in >>> boost_filesystem-gcc-mt... no >>> configure: error: *** Boost.Filesystem required by VPR *** >>> Configuration of VRJuggler in >>> /tile/apps/VRJUGGLER/juggler/build/modules/vapor failed >>> > > fyi: we had the same problem on our debian machines. Boost is in the > debian repository so we reported this problem to the boost package > maintainer and it was recognized as a bug, see below. So I don't think a > user should compile and install boost for him/herself. I don't think that people making redistributable packages of Boost should be changing the names of the installed libraries. While the explosion of library variants complicates things, we have addressed all the issues raised in the posting to the boost-users mailing list. We can determine at configuration time which build variant we need because the configure script knows which compiler is being used and what threading subsystem we have. If Red Hat or Debian or whoever decides that the Boost library naming convention should be ignored, then they are introducing headaches for people writing cross-platform software. It would be even worse if two Linux distrubutions chose to use different conventions for renaming Boost libraries. Then again, it wouldn't be the first time that any given pairing of Linux distrubtions had incompatibilities. :) > I don't know about other distributions. IRIX really doesn't fall into this category since I doubt that SGI will ever be distributing pre-packaged versions of Boost. Even if they did, my experience tells me that they would always be at least one or two major releases behind. Thus, someone (user or sys admin) has to compile and install Boost for their local use. Once again, however, I direct your attention to the pre-compiled VR Juggler dependency distribution. By using it, you're guaranteed to get everything you need with very little work. Of course, for operating systems with Boost or omniORB or whatever already installed via package management, it's not an out-of-the-box solution. Nonetheless, the dependency distribution tree could be pruned quite easily to clear out duplication. Of course, the pre-compiled dependency distribution is something new that is being tried with 2.0 Alpha 4, and there are probably ways to improve it. -Patrick > Here's a copy of the response: > > Date: Sun, 25 Jul 2004 17:52:33 -0400 > From: "Steve M. Robbins" <ste...@vi...> > To: Jeroen Akershoek <je...@sa...> > Subject: Re: Debian libboost-filesystem-dev > > On Tue, Jul 06, 2004 at 04:33:46PM +0200, Jeroen Akershoek wrote: > >>> Hello, >>> >> >> > >>> I was building VR-Juggler and noticed that it wasn't able to find >>> libboost-filesystem-gcc-mt.so When I looked in the package I found >>> that the file was called libboost-filesystem-gcc-mt-1.31.so. Is it >>> an idea to provide a symlink to the current/latest .so without the >>> version number in the\ dev-package? I think this will make some >>> software (like VRjuggler :)) easier to build, since it would save >>> editing some configure.in files >> >> >> > > My Debian co-packager and I decided to create a symlink from > libboost_filesystem.so to the current installed library. > > That only helps the author of VRjuggler if our convention becomes > > > widespread. See the thread at > http://lists.boost.org/MailArchives/boost-users/msg06964.php > > -Steve > > > > >>> In Irix: checking for boost::filesystem::exists() in >>> boost_filesystem-mp... no >>> configure: error: *** Boost.Filesystem required by VPR *** >>> >>> I guess that I need some boost.filesystem package does not comes with >>> boost or something? >> >> >> No, Boost.Filesystem is one of the Boost libraries. I strongly >> recommend that you go to the Boost website and learn about what Boost >> is. This has come up before, and I am not sure that you understand that >> Boost is a third-party collection of C++ libraries. We don't maintain >> it; we don't control it; we just take advantage of the huge amounts of >> benefits it offers. >> >> >> >>> Could you send me some pointers to download those package? >> >> >> Have you looked that the build/install instructions for VR Juggler that >> come with the source? There are URLs pointing directly to the >> information you need and plenty of detailed instructions related to all >> of this. In a nutshell, what you need to do for Boost is the following: >> >> 1. Go to http://www.boost.org/ >> 2. Get the Boost 1.31.0 source >> 3. Compile and install Boost 1.31.0 using the instructions that >> they provide >> 4. Tell the VR Juggler configure.pl script where you installed >> Boost. >> >> The process has some caveats, and you really should be reading the >> instructions. >> >> -Patrick >> >> >> >> > > -- Patrick L. Hartling | VP Engineering, Infiscape Corp. PGP: http://tinyurl.com/2msw3 | http://www.infiscape.com/ |