Re: Wrapping gcc

Joel S writes:

> Sure enough, the gcc--3.2.xml I copied from verilabs2 had the status set to
> deployed. Digging, I learned about version wrappers and the need to deploy
> gcc--3.2 and reveal gcc-wrapper. ...

Joel, I'll deal w/ the shtool weirdness later; here, I will
speak up for Matt Holgate's wondrous "version wrapping"
(which I happen to use for GCC at Verilab, but which is
optional.)  Doc: http://ark.sourceforge.net/vwrapper.html

We live in a world of multiple versions of bizarre EDA
tools, each requiring even-more-bizarre delicate
environments to run.  Matt's stuff deals with just the
*versions* thing.

* You can see the many versions available:

    % gcc --show-versions
    Versions of `gcc' available:
      2.95.3
      3.2 *
      3.1

* You can pick a non-default one:

    % gcc --use-version=2.95.3 --version
    2.95.3

I try to do this wrapping thing for *any* tool that might be
used in a build system (Makefiles and such) where we want
*precise* control over what's going into the mix.

Like I say, it's optional.

Will


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf