🚀 go-pugleaf

Remy Lebeau (TeamB) wrote:
> "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.

I predict the text above will be seen in future as some of the best 
information and news for all people who need help!

So I did these steps:

1. Deleted all that I'd done earlier and unzipped indy10.zip.

2. Opened and compiled these projects:

- lib\system\IndySystem100.bdsproj
- lib\core\dclIndyCore100.bdsproj (no complaints about idipaddress)
- lib\protocols\dclIndyProtocols100.bdsproj

3. That left these files in my bpl output directory:

02/07/2007  09:15 PM           390,656 dclIndyCore100.bpl
02/07/2007  09:15 PM            56,953 dclIndyCore100.dcp
02/07/2007  09:16 PM           292,864 dclIndyProtocols100.bpl
02/07/2007  09:16 PM            40,653 dclIndyProtocols100.dcp
02/07/2007  09:14 PM           303,104 IndyCore100.bpl
02/07/2007  09:14 PM           707,814 IndyCore100.dcp
02/07/2007  09:16 PM         1,795,584 IndyProtocols100.bpl
02/07/2007  09:16 PM         3,084,529 IndyProtocols100.dcp
02/07/2007  09:13 PM           145,408 IndySystem100.bpl
02/07/2007  09:13 PM           372,357 IndySystem100.dcp

4. I told BDS to remove Indy Core and Indy Protocols but I have not yet 
deleted the original dcu and dcp files from ($BDS)\lib\indy10, nor have 
I removed from ($BDS)\bin all the Indy related files there.  These newly 
compiled BPLs do not exactly parallel what I see in BDS's bin directory. 
  Maybe Indy's a little restructured, maybe some bin\* files relate to 
.net, etc.

5. ($BDS)\lib\indy10 contains one OBJ file: idantifreeze.obj.

6. I imagine the next step would be to replace the old DCUs with the 
newly-compiled ones, remove the Indy BPLs from ($BDS\bin, place the new 
BPLs somewhere sensible, then add dclIndyProtocols100 and dclIndyCore100 
to the packages.

But I think I'll stop in hopes Remy will comment on this direction.

Also, what does the file prefix "dcl" mean--it's used a lot besides in Indy.

>> 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.

No offense intended. ;-)

>> 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.

So there's still the question how to make LIBs for C++ development where 
Indy objects might be created with new()...

> Gambit

Thanks Remy.