Now that I've used all this swell stuph, it's time to pay the piper: turn it over to QC and get it into "The Build". Unfortunately the QC people would like some instructions that describe which version of boost-build I'm using; how to install it; which version of the libs I'm using; etc. <some background> It's been a couple of months since I started with the boost libs, and I don't remember all the gyrations I went through to get it working and I'm POSITIVE I did a LOT more than is required. I remember that, after downloading and extracting boost_1_27_0.tar.gz, I had to get the current version from CVS before I could get a clean compile. (I tried turning over copies of my disk drives to them but it turns out that is not considered acceptable documentation. %>[ ) I've been following the jamboost and Boost-Users mailing lists so I know there've been quite a few changes - especially to boost-build. After building a "clean" testbed machine, I started by downloading boost-build.win.zip and following the instructions in the readme.html. Well, that didn't work. I can do a hand job on the path but I'm not sure what environment variables are actually required. Current plan is to pull the library source directly from CVS. Problem is, I don't know what version to tell QC I'm using and, unless all the folks at boost.org would agree not to add anything to CVS for a while, I SURE can't tell them how to re-create what I did. ;) I can always take what I've got; check it in and call it a day but that's not the path to getting boost integrated into the development environment around here. (Hey, I'm trying to be an evangelist here.) Anyone by any chance working on some updated instructions and/or docs that maybe aren't ready for prime time but would be willing to share? TIA PS: Current target systems are Win2000, SP2 and Visual C++ 6.0, SP5 and vanilla Red Had Linux 7.2.
On Wednesday 08 May 2002 01:51 pm, you wrote:
Current plan is to pull the library source directly from CVS. Problem is, I don't know what version to tell QC I'm using and, unless all the folks at boost.org would agree not to add anything to CVS for a while, I SURE can't tell them how to re-create what I did. ;)
I can always take what I've got; check it in and call it a day but that's not the path to getting boost integrated into the development environment around here. (Hey, I'm trying to be an evangelist here.) Anyone by any chance working on some updated instructions and/or docs that maybe aren't ready for prime time but would be willing to share?
First, the required question. Are you using any of these libraries: threads, regex, or python? If not, you don't need Boost.Build. Just take the Boost headers and put them somewhere. If so, you will need Boost build. At this point, I'd suggest waiting for 1.28.0 before trying to get Boost past QC. 1.28.0 should be available within a week or two, and there have been many improvements to Boost.Build that will be included. Doug
participants (2)
-
dick.bridges@tais.com
-
Douglas Gregor