🚀 go-pugleaf

Gene Buckle <geneb@grumble.deltasoft.com> wrote:
> I've scrubbed the system of any "default" Indy installs and the Delphi
> tests I run show the version I expect after building it according to
> the instructions on the website.
> 
> However, there are none of the .hpp files for the Indy components in the system
> anywhere.  How do I go about getting the system to create them?
> 
> Is there documentation anywhere on the use of the full*.bat files and the
> other tools in the Builder directory?
> 
> tnx all.
> 

Ok, I thrashed around the net and found a the famed "fullc10.bat" file and
I've got the header files generated for *120.

Note to those in my shoes - you'll need to update the computil.dpr program
by adding SetupC10 in a couple of places as well as making sure you add
the registry key (towards the end of the program) so that the environment
can be set up correctly to find the tool chain.

You'll also need to change any reference to "100" to "120" if you're 
actually using RAD Studio 2007 to grab the "right" version for that compiler.

What I want to know is why the hell isn't AtoZed not supporting the software
that's included with a commercial product?  I had to fall across by accident
a post about a guy that figured it out.  The supposed "daily snapshot" 
should have at a _minimum_ a pointer where to go to learn what the hell is 
going on.  Instead, we get terse and unhelpful documentation and a FAQ that
is about as useful for actually building the product as is a kaleidescope
to a blind person.  Way to go CodeGear and AtoZed!  

Maybe Embarcadero can clean this mess up, but I'm not going to hold my breath.

(and there's no way I'm renewing my SA until I see evidence(sp) that crap
like this has been taken care of)

g.

-- 
Proud owner of F-15C 80-0007
http://www.f15sim.com - The only one of its kind.