$include_dir="/home/hyper-archives/boost/include"; include("$include_dir/msg-header.inc") ?>
From: Hendrik Schober (SpamTrap_at_[hidden])
Date: 2005-05-25 10:39:19
Caleb Epstein <caleb.epstein_at_[hidden]> wrote:
> [...]
> No, thats not at all what the guide says. You type:
>
> ..\bjam.exe -sTOOLS=vc-7_1 stage
Wow. No warning. Thanks!
> Where did you get VC71_ROOT from?
I explained this in another mail.
> > After quite a pause ("what's it doing now?") it
> > spit out a lengthy messagethat that I have an
> > incorrect configuration. It couldn't find Python.
>
> This is only pertinent if you are building Boost.Python.
As I said: /I/ knew this. But many who
stumble over boost don't.
> > Mhmm. Do I need this? Will it even work without
> > Python? (I know it will. But not from the guide.)
> > Next thing it emits is
> > don't know how to make bjam
>
> Because you typed bjam twice on the command line
<blush>
Didn't I say I don't like having to type
commands? <sheepish grin>
> > [etc]
>
> Just follow the directions. They could be more clearly written, but
> you haven't even come close to typing equivalent commands to the ones
> listed on the Getting Started page.
Maybe I'm really just being dumb here. But I
believe that there are many like me. (And not
only on Windows. You should see a Mac guy
here looking over my shoulder when I actually
/type/ commands!)
> Admittedly there should be example command lines for vc-7_1 etc and
> not just gcc.
IMO a straight
bjam "-sTOOLS=<tools_name>" install
with exact hinting at where to find "tools_name"
would do.
Schobi
-- SpamTrap_at_[hidden] is never read I'm Schobi at suespammers dot org "Coming back to where you started is not the same as never leaving" Terry Pratchett