Date: 2002-07-07 12:40:04
In article <013b01c225d6$77d6a560$6601a8c0_at_[hidden]>,
David Abrahams <jamboost_at_[hidden]> wrote:
>As explained in my message to Gennadiy, Beman has been working on a system
>to generate those pages using bjam and some front-end scripting, but we
>have never released status pages built that way on the website.
Yes, I saw, thanks!
>> It looks like some something reads
>> that .cfg file???? Guess I'll be snooping around that directory.
>See http://www.boost.org/more/regression.html, which describes the system
>that has been used to-date.
I just posted that I thought this, so thanks for the verification.
I think that'll be sufficient for me to start moving on some work.
>> >* I looked at the como toolset a bit more, and it's definately as
>> >in support as the description says. It only works in Win32/VC.
>> What does 'if $(NT)' check for?
>A windows platform.
Ok good. But then the problem is that it was stated (and seems
from my looking at the file) that the file is only Windows specific.
So why would a windows specific file look for a windows specfic
platform? Does it want to do something specific on Windows NT
that it won't do non-NT versions of Windows? I'm clearly confused
on a number of points, so go easy on me if this is too obvious :)
>> As such, let me start with a question: I'm unclear as to
>> the difference between COMO_PATH, COMO_BIN_PATH, COMO_BIN_DIRECTORY,
>> COMO_BASE_SETUP, and COMO_PATH_SETUP and how they [need to] interact
>> and/or how they are [necessary to be] different from just
>> PATH and COMO_PATH?
>That's actually a statement followd by a question-mark ;-)
>Does http://www.boost.org/tools/build/como-tools.html fail to explain it?
>If so, please ask a specific question.
I'm still confused over como-tools.html, so I'll ask my question
statement as a question :} :
the difference between COMO_PATH, COMO_BIN_PATH, COMO_BIN_DIRECTORY,
COMO_BASE_SETUP, and COMO_PATH_SETUP and how do they [need to] interact
and/or how are they [necessary to be] different from just
PATH and COMO_PATH? :) Seriously. I see for instance that
borland-tools.html only discusses BCCROOT. Why doesn't como
need just COMOROOT then? And/or why isn't there just a ROOT
or COMPILER_ROOT for all compilers? Or why isn't it just
assumed to be in PATH?
>> And also what program uses these "new" variables, and why?
>bjam uses them when using the como toolset in order to know what it needs
>to stick in the command-line.
>What's "new" about them?
I probably should have said "extra". Extra in the sense that
Comeau C++ normally doesn't use them, so what does use then,
where does it use them, and why?
-- Greg Comeau 4.3.0 NEWS: New Windows Backends + 'export' IN July! Comeau C/C++ ONLINE ==> http://www.comeaucomputing.com/tryitout World Class Compilers: Breathtaking C++, Amazing C99, Fabulous C90. Comeau C/C++ with Dinkumware's Libraries... Have you tried it?
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk