🚀 go-pugleaf

"Frank Burleigh" <burleigh@indiana.edu> wrote in message
news:45c9dcbc$1@newsgroups.borland.com...

> If you're still using BCB6 I don't think you need to do this.  My
edits
> to the computil.dpr unit just add the path to BDS 2006's bin
directory
> so that Remy's batch file can compile.

The .bat files are not needed in order to compile Indy for BDS 2006.
With the merging of C++ and Delphi into a single unified IDE, the .dpk
files can be loaded and compiled directly in the IDE for installing
Indy in both personalities.  That is why computil.exe was never
updated to look for BDS's compiler.

The only downside to compiling the .dpk files inside the IDE is that
the "BCB" conditional has to be defined manually inside the Core
package, or else IdIPAddress.pas will not compile correctly (an
"unsupported language feature" error will occur).  The .bat files
define "BCB" at the command-line level for the compiler to pick up
automatically.

> Remy's build process needs computil.exe to manipulate some
> environment variables and to create a setenv.bat file.

It is not my build process.  Indy was using .bat files long before I
started using Indy.

> What *are* BPI files, anyway?

A .bpi file is an import lib for a .bpl library.  When runtime
packages are enabled in the project, .bpi/bpl are used.  When runtime
packages are disabled, a static .lib is used instead.


Gambit