All kinds of trouble with Indy 9 and BDS 4

Thread View: borland.public.cppbuilder.internet.socket

3 messages

[T] Back to Threads [V] Tree View [G] Group Articles

3 total messages Started by Frank Burleigh Sun, 30 Jul 2006 05:03

#2137

Author: Frank Burleigh
Date: Sun, 30 Jul 2006 05:03

34 lines
2249 bytes

I've spent much of the day struggling to get Indy 9 working with BDS 4 
with very little luck, I'm afraid.  Here's what I've tried:

- I see Indy 10 "doesn't work" in C++Builder 2006 so I've removed the 
Indy packages from the project.

- I make Indy components in code with new(), so I've removed the design 
time packages from the project.

- 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) then created the 
necessary environment variables by hand.  The PAS files compile to OBJs 
fine it seems.

- Since 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) I 
made a list of all the OBJs compiled into a file to tlib can place those 
into indy6.lib.

- I added indy6.lib to my project but ilink32 also access violates when 
I do that.  And when I simply add the directory with the OBJs to the OBJ 
search path, the build process always ends with unresolved external 
referances like:

[Linker Error] Error: Unresolved external 'Idmessage::TIdText::' 
referenced from 
C:\DEVELOP\PROJECTS\SI_MASSMAILER\DEBUG_BUILD\FM_MASSEMAIL.OBJ

- I'm stuck.  Since the compilation has no errors I figure this isn't a 
namespace issue, but I'm no expert on linked object names.

Any help appreciated.

Re: All kinds of trouble with Indy 9 and BDS 4

#2139

Author: Remy Lebeau (TeamB)
Date: Mon, 31 Jul 2006 00:26

44 lines
2937 bytes

"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 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.
Unfortunately, computil.exe does not support BDS at all (it did support
future BCB 7-9 releases, but that was before Borland decided to merge Delphi
and C++ into a new product).  Fortunately, Indy does include the
computil.dpr source code, so you can update it with BDS support if you wish.

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

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


Gambit

Re: All kinds of trouble with Indy 9 and BDS 4

#2141

Author: Frank Burleigh
Date: Mon, 31 Jul 2006 14:52

59 lines
3743 bytes

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

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads