🚀 go-pugleaf

Remy Lebeau (TeamB) wrote:
> "Paul at NCF" <notplmacca@clara.co.uk> wrote in message
> news:45c78d7b$1@newsgroups.borland.com...
> 
>> I thought that in Indy 9 is converted (compiled) the PAS files in to
>> the HPP files, they weren't there to start off with (just looked at
> my archive).
> 
> Yes, the Pascal compiler does produce HPP files during compiling -
> IF - the command-line parameters tell it to.  Which leads me to think
> that people are not installing Indy in the correct manner to begin
> with.  I do compile both Indy 9 and 10 from command-line scripts, and
> HPP files are always generated properly.
> 
> 
> Gambit

Comprehensive documentation would be welcome.  But I can also see how 
time-consuming such a production might be in a moving project that has 
to support 5 versions of two compilers....

I see people asking both about BCB6 and BDS 2006, sometimes for Indy 10. 
  Last year, when I migrated from another library to Indy, I spent some 
quality time getting Indy 9 to work enough with C++ in BDS 2006 in one 
project that I could build working software.  I think I link specific 
OBJ files to get it all to work.  It's not good--hard to understand why 
it works and certainly hard to reproduce.  (Some LIBs are also linked.)

Yesterday I decided to try Indy 10 with C++ in BDS 2006 again--because 
it looks like you've worked to make Indy 10 work with Borland's more 
recent C++ compiler and IDE environments.  I've done these things:

- added a SetupCA (10) to computil.dpr that knows where to find BDS 
2006's bin directory.

- updated fullc6.bat to be aware of BDS 2006, including using dcc32's 
command line switches that make HPP and OBJ files during the compile 
(-NO, -NH, -JPH).  These changes appear to compile without error.  I now 
see HPP and OBJ files but don't really know what other files should be made.

- So I get five BPLs in the C6 directory (as before), but also get HPP 
and OBJ files there.  I'd guess I could add that directory--C6--to my 
include path, install the BPL files, and be pretty close to having a 
working VCL approach for Indy 10 in a C++ VCL project.  Do you agree?

- I'd also like to have working LIBs.  When I worked on this last year, 
the fullc6.bat file made LIB files using a response file I got from the 
zip file for some other version of Indy 9.  Fullc6.bat doesn't seem to 
make LIBs now, so I don't know what LIB files need to be made or which 
OBJ files to put in each.  Without that knowledge it would likely be a 
fool's errand to spend much more time on this--I might have cascading 
unresolved references and never know how to get back on track.

So I look forward to your guidance, Remy.


Thanks!