🚀 go-pugleaf

Remy Lebeau (TeamB) wrote:
> "Frank Burleigh" <burleigh@indiana.edu> wrote in message
> news:44cc3d83@newsgroups.borland.com...
> 
>> I make Indy components in code with new(), so I've removed
>> the design time packages from the project.
> 
> The project should not have had any references to the design-time packages
> in the first place, only to the run-time packages, which you still need in
> the project regardless of whether or not you use 'new' to instantiate the
> components.

I made progress on this work after my post--I'd intended to post my 
experiences sooner.  Sorry.

>> - I got the "snapshot" zip from the indy mirror.  I removed the line:
>> computil SetupC6
>> from the fullc6.bat file (since it seems to want bcb6)

> As its filename implies, FULLC6.BAT is specifically designed for C6, aka
> C++Builder v6.  BDS 2006 did not exist yet when Indy 9 became
> feature-frozen, so Indy 9 will never officially support any BDS version.
> 
> You can't just comment out the 'computil' line because computil.exe sets up
> environment variables that the rest of the FULLxx.BAT file uses to know
> where the command-line compiler and the OS system directory are located.

I understood this and set the vars manually.

>> I can't find indywin32.rsp (no earlier indy 9 versions to download,
>> and the one Remy posted to an atozed newsgroup is now dead)
> 
> The old Indy 9 versions are available for download on Indy's website.  The
> links works fine.  What you describe was just a temporary problem on Indy's
> web server at the time.

I found them yesterday, no problems.

>> when I simply add the directory with the OBJs to the OBJ search path,
>> the build process always ends with unresolved external referances
> 
> That is because you did not actually add the .obj files (or the .lib that
> contains the .obj data) to the project.  Simply setting the folder location
> is not enough.

I should have recognized that before posting.  I had success linking 
when I added the objs manually (somewhat tedious), but the link always 
failed when I added the lib to the project.

Then I got the real indywin32.rsp and rebuilt the library with debug 
support, only to have any effort to make a TIdSMTP except with AVs about 
three inherited constructors down the stack.  If it matters, I never did 
install the runtime package (it always fails with the complaint that the 
"file can't be found."

Then I made a brand new project file for my app (which has been carried 
through many versions of BCB), adding the source files plus the library. 
  That let me link without problems and run through the point where I 
instantiate a TIdSMTP.  I take that to be progress. ;-)