🚀 go-pugleaf

Sharad wrote:
> i need to use Indy 10 but i dont know how to get it. all i got is its source from the indy site and i dont know how to compile it.
> 
> please help.

Download the indy 10.0.52 source from the site.

you will have to do the following...
Compile first only...
IndySystem
IndyCore
IndyProtocols
IndySuperCore (not needed)

then install the following.

dclIndyCore
dclIndyProtocols
dclIndySuperCore(only if you have already compiled...)

In order to accomplish the things above you will have to do the following...

For indySystem let's say.
Open BCB.
Component->Install Component->Into New Package.
Go inside the system directory and find IndySystem70.dpk
open it with notepad and you will have to provide as the
source file for your new component all the pascal files listed there.
you can multiselect them. then just compile it.

The same thing you must do for the other packages as well.
I named my packages IndySystem61.bpk and so on.
you will also have to check the requires list inside the dpk's.
when it tells you to include a indy sourse you only have to
add the directory you have previously compiled within the
include path and library path of each project. Only the ones needed though.

If you encounter any other problems reply to this message.
Another thing... i wasn't able to compile the development
shnapshot and that's why i do not recommend it.

On Wed, 29 Jun 2005 12:58:51 +0300, qyte <gyte@vivodinet.gr> wrote:

>Download the indy 10.0.52 source from the site.
done

>In order to accomplish the things above you will have to do the following...
>
>For indySystem let's say.
>Open BCB.
>Component->Install Component->Into New Package.
>Go inside the system directory and find IndySystem70.dpk
do you mean IndySystem60.dpk?  They appear to be the
same anyway so maybe it doesn't matter?

>source file for your new component all the pascal files listed there.
>you can multiselect them. then just compile it.
That worked fine too.

>I named my packages IndySystem61.bpk and so on.
did that too

>If you encounter any other problems reply to this message.
The build for all three seemed to work fine.  There were no errors.
The problem is that I don't see anything on the component bar.  Also,
when I click on Component -> Install Packages, I see the 3 packages
IndySystem61, IndyCore61 and IndyProtocols61 but if I select one and
click Components, I get an empty list of Installed Components.  One 
coworker suggested checking the bpk options to see if runtime package
option was checked.  I did and it was.

I have seen posts saying it has been done but I certainly would like
to know how it was done

Damon Register

"Damon Register" <damon.w.register@lmco.com> wrote in message
news:3gqcd15p233skvct1ea0s6pi2j2ev1v6o8@4ax.com...

> when I click on Component -> Install Packages, I see the 3 packages
> IndySystem61, IndyCore61 and IndyProtocols61 but if I select one
> and click Components, I get an empty list of Installed Components.

Then none of the packages registered any components.  The Core and Protocols
packages have IdRegister... units that register the components.  Did you
include those files when you created your new packages?  Otherwise, you
would alternatively have to register the components yourself in the
package's own Register() function.

> One coworker suggested checking the bpk options to see if runtime
> package option was checked.  I did and it was.

That has nothing to do with it.


Gambit

On Thu, 14 Jul 2005 10:15:44 -0700, "Remy Lebeau \(TeamB\)"
<no.spam@no.spam.com> wrote:

>Then none of the packages registered any components.  The Core and Protocols
>packages have IdRegister... units that register the components.  Did you
>include those files when you created your new packages?  Otherwise, you
>would alternatively have to register the components yourself in the
>package's own Register() function.
in stumbling around some more I sort of learned that (or something
related).  I followed qyte's instructions in this thread.  With some
help from a coworker, I found that what I had was a runtime package
without the design time part.  After looking at
http://www.indyproject.org/Sockets/Docs/Indy10Install.iwp
again I found that there are IndyCore*.dpk and dclIndyCore*.dpk.
Using qyte's method, I did the same thing with the dclIndyCore60.dpk
and dclIndyProtocols60.dpk and got a lot farther than before.  
The only thing I didn't understand is why there is a dclIndyCore60.dpk
in both the \core and \protocols folder and each had a different list
of "contains".    For the dclIndyCore60 project I used the 
dclIndyCore60.dpk that was in core.  For the dclIndyProtocols60
I used these files

dclIndyCore61.res" FORMNAME="" UNITNAME="dclIndyCore61.res" 
dclIndyCore61.cpp
dclIndyCore61
IdRegisterCore.pas
IdAbout.pas
IdAntiFreeze.pas
IdCoreDsnRegister.pas
IdDsnBaseCmpEdt.pas
IdDsnCoreResourceStrings.pas
IdDsnPropEdBinding.pas
C:\Program Files\BORLAND\CBuilder6\Source\Toolsapi\designintf.pas

I added the designintf because I got a squawk at compile

The IdRegister.pas that you mentioned was not in the dclIndyCore60.dpk
that was in the \core folder but it was in the file that was in the
file that was in the \protocols folder.  The core one has 
IdRegisterCore.pas

I was able to build and install with all the components showing up on
the palette.  I tried making a simple program with just a TIdTCPClient
but got a compile error so it seems something still isn't right

Damon Register

"Damon Register" <damon.w.register@lmco.com> wrote in message
news:h3add15303bc2ts50r711p8jjqfcttk8ne@4ax.com...

> The only thing I didn't understand is why there is a
> dclIndyCore60.dpk in both the \core and \protocols folder

A mistake.  It should only be in the \core folder.

> The IdRegister.pas that you mentioned was not in the dclIndyCore60.dpk
> that was in the \core folder but it was in the file that was in the
> file that was in the \protocols folder.  The core one has
> IdRegisterCore.pas

Correct.  If you look back at my earlier message, I did not actually say
"IdRegister.pas", I said "IdRegister...", which encompasses both
"IdRegister.pas" and "IdRegisterCore.pas".

> I tried making a simple program with just a TIdTCPClient but
> got a compile error so it seems something still isn't right

Please elaborate.


Gambit

Remy Lebeau (TeamB) wrote:
> "Damon Register" <damon.w.register@lmco.com> wrote in message
> news:h3add15303bc2ts50r711p8jjqfcttk8ne@4ax.com...
> 
> 
>>The only thing I didn't understand is why there is a
>>dclIndyCore60.dpk in both the \core and \protocols folder
> 
> 
> A mistake.  It should only be in the \core folder.
> 
> 
>>The IdRegister.pas that you mentioned was not in the dclIndyCore60.dpk
>>that was in the \core folder but it was in the file that was in the
>>file that was in the \protocols folder.  The core one has
>>IdRegisterCore.pas
> 
> 
> Correct.  If you look back at my earlier message, I did not actually say
> "IdRegister.pas", I said "IdRegister...", which encompasses both
> "IdRegister.pas" and "IdRegisterCore.pas".
> 
> 
>>I tried making a simple program with just a TIdTCPClient but
>>got a compile error so it seems something still isn't right
> 
> 
> Please elaborate.
> 
> 
> Gambit
> 
> 


Soory for interupting your discussion but when i answered the thread
i forgot to mention the dclIndy... packages. Another thing i forgot to 
mention is that although i managed to compile and install the packages i 
had never used them. I also get the compiler errors (which i believe to 
be the same with Damon) when trying to build a project. The errors i 
find are within the idwinsock2.hpp file. It seems that the typedefs' 
there are somehow incorrect. I have not yet managed to solve the matter.
If someone else has it would be of GREAT comfort for a lot of people (i 
believe) to reply to this Thread.

Too bad since Indy 10 seem to be a lot better than Indy 9.
I really hope there is a solution out there.

"qyte" <gyte@vivodinet.gr> wrote in message
news:42d860e5@newsgroups.borland.com...

> I also get the compiler errors (which i believe to be the same with
> Damon) when trying to build a project.

Again, I ask for SPECIFIC details.  What are the ACTUAL errors?

> The errors i find are within the idwinsock2.hpp file.

IdWinsock has not been BCB-ified yet.  It is a known problematic unit for
C++ projects due to conflicts with the Win32 API's own header files.  This
has already been addressed in Indy 9 but has not been implemented in Indy 10
yet.


Gambit

On Thu, 14 Jul 2005 12:55:23 -0700, "Remy Lebeau \(TeamB\)"
<no.spam@no.spam.com> wrote:

>
>"Damon Register" <damon.w.register@lmco.com> wrote in message
>news:h3add15303bc2ts50r711p8jjqfcttk8ne@4ax.com...
>
>> The only thing I didn't understand is why there is a
>> dclIndyCore60.dpk in both the \core and \protocols folder
>
>A mistake.  It should only be in the \core folder.
That was the one I used.  

>Correct.  If you look back at my earlier message, I did not actually say
>"IdRegister.pas", I said "IdRegister...", which encompasses both
>"IdRegister.pas" and "IdRegisterCore.pas".
I need both?

>> I tried making a simple program with just a TIdTCPClient but
>> got a compile error so it seems something still isn't right
>
>Please elaborate.

Build
  [C++ Error] IdWinSock2.hpp(370): E2257 , expected
  [C++ Error] IdWinSock2.hpp(726): E2303 Type name expected
  [C++ Error] IdWinSock2.hpp(728): E2303 Type name expected
  [C++ Error] IdWinSock2.hpp(730): E2303 Type name expected
  [C++ Error] IdWinSock2.hpp(744): E2303 Type name expected
  [C++ Error] IdWinSock2.hpp(746): E2303 Type name expected
  [C++ Error] IdWinSock2.hpp(748): E2303 Type name expected
  [C++ Error] IdWinSock2.hpp(780): E2303 Type name expected
  [C++ Error] IdWinSock2.hpp(782): E2303 Type name expected
  [C++ Error] IdWinSock2.hpp(784): E2303 Type name expected
  [C++ Error] IdWinSock2.hpp(788): E2293 ) expected
  [C++ Error] IdWinSock2.hpp(790): E2293 ) expected
  [C++ Error] IdWinSock2.hpp(792): E2293 ) expected
  [C++ Error] IdWinSock2.hpp(794): E2293 ) expected
  [C++ Error] IdWinSock2.hpp(796): E2293 ) expected
  [C++ Error] IdWinSock2.hpp(798): E2293 ) expected
  [C++ Error] IdWinSock2.hpp(1954): E2303 Type name expected

I posted my Indy60 project files to borland.public.attachments
if you or anyone else cares to look at them.  The post subject 
is:  Indy 10 project files for BCB6

Damon Register

On Mon, 18 Jul 2005 01:01:22 -0700, "Remy Lebeau \(TeamB\)"
<no.spam@no.spam.com> wrote:

>IdWinsock has not been BCB-ified yet.  It is a known problematic unit for
>C++ projects due to conflicts with the Win32 API's own header files.  This
>has already been addressed in Indy 9 but has not been implemented in Indy 10
>yet.
Does this mean that I am just wasting time on this?  I should wait
until this problem is fixed and should use version 9 until then?

Damon Register

"Damon Register" <damon.w.register@lmco.com> wrote in message
news:859nd154r7fh7fqtrfmi24u549gg1o3l1n@4ax.com...

> I need both?

Yes.  There are components in both packages.

>   [C++ Error] IdWinSock2.hpp(370): E2257 , expected

That doesn't help.  You need to show the actual code that the compiler is
complaining about.


Gambit

On Mon, 18 Jul 2005 09:51:58 -0700, "Remy Lebeau \(TeamB\)" <no.spam@no.spam.com> wrote:

>
>>   [C++ Error] IdWinSock2.hpp(370): E2257 , expected
>
>That doesn't help.  You need to show the actual code that the compiler is
>complaining about.

[C++ Error] IdWinSock2.hpp(373): E2257 , expected
typedef TWSAProtocol_InfoW *LPWSAProtocol_InfoW;

[C++ Error] IdWinSock2.hpp(746): E2303 Type name expected
typedef int __stdcall (*TWSAEnumProtocolsAProc)(System::PInteger lpiProtocols, PWSAProtocol_InfoA lpProtocolBuffer, unsigned &lpdwBufferLength);

[C++ Error] IdWinSock2.hpp(748): E2303 Type name expected
typedef int __stdcall (*TWSAEnumProtocolsWProc)(System::PInteger lpiProtocols, PWSAProtocol_InfoW lpProtocolBuffer, unsigned &lpdwBufferLength);

[C++ Error] IdWinSock2.hpp(750): E2303 Type name expected
typedef int __stdcall (*TWSAEnumProtocolsProc)(System::PInteger lpiProtocols, PWSAProtocol_InfoA lpProtocolBuffer, unsigned &lpdwBufferLength);

[C++ Error] IdWinSock2.hpp(764): E2303 Type name expected
typedef int __stdcall (*TWSADuplicateSocketAProc)(const int s, const unsigned dwProcessId, PWSAProtocol_InfoA lpProtocolInfo);

[C++ Error] IdWinSock2.hpp(766): E2303 Type name expected
typedef int __stdcall (*TWSADuplicateSocketWProc)(const int s, const unsigned dwProcessId, PWSAProtocol_InfoW lpProtocolInfo);

Just for "fun" I built the dev snapshot.  There were no errors on build but
I got the same errors I got from using the released version 10  on 
using an IdTCPClient in a project

Damon Register

Damon Register <damon.w.register@lmco.com> wrote:
>On Mon, 18 Jul 2005 09:51:58 -0700, "Remy Lebeau \(TeamB\)" <no.spam@no.spam.com> wrote:
>
>>
>>>   [C++ Error] IdWinSock2.hpp(370): E2257 , expected
>>
>>That doesn't help.  You need to show the actual code that the compiler is
>>complaining about.
>
>[C++ Error] IdWinSock2.hpp(373): E2257 , expected
>typedef TWSAProtocol_InfoW *LPWSAProtocol_InfoW;
>
>[C++ Error] IdWinSock2.hpp(746): E2303 Type name expected
>typedef int __stdcall (*TWSAEnumProtocolsAProc)(System::PInteger lpiProtocols, PWSAProtocol_InfoA lpProtocolBuffer, unsigned &lpdwBufferLength);
>
>[C++ Error] IdWinSock2.hpp(748): E2303 Type name expected
>typedef int __stdcall (*TWSAEnumProtocolsWProc)(System::PInteger lpiProtocols, PWSAProtocol_InfoW lpProtocolBuffer, unsigned &lpdwBufferLength);
>
>[C++ Error] IdWinSock2.hpp(750): E2303 Type name expected
>typedef int __stdcall (*TWSAEnumProtocolsProc)(System::PInteger lpiProtocols, PWSAProtocol_InfoA lpProtocolBuffer, unsigned &lpdwBufferLength);
>
>[C++ Error] IdWinSock2.hpp(764): E2303 Type name expected
>typedef int __stdcall (*TWSADuplicateSocketAProc)(const int s, const unsigned dwProcessId, PWSAProtocol_InfoA lpProtocolInfo);
>
>[C++ Error] IdWinSock2.hpp(766): E2303 Type name expected
>typedef int __stdcall (*TWSADuplicateSocketWProc)(const int s, const unsigned dwProcessId, PWSAProtocol_InfoW lpProtocolInfo);
>
>Just for "fun" I built the dev snapshot.  There were no errors on build but
>I got the same errors I got from using the released version 10  on 
>using an IdTCPClient in a project
>
>Damon Register

Damon: I got as far as you did, and got to the same error. It took several weeks, off and on.

Indy 10 has a feature that would be useful to me. I would like to install it in BCB 6. But for now, I am rolling back to 9.

I noted discussion of installing Indy 10 in February, and held off until it was a "sure thing". Or sis months, whichever came first. It looks like another six months.

I'm a standalone developer, and don't have time for messing around like I did in the old days.

On 1 Aug 2005 05:44:40 -0700, "hal davitt" <tech_email@mindspring.com> wrote:

>Indy 10 has a feature that would be useful to me. I would like to install it in BCB 6. 
>But for now, I am rolling back to 9.
That's what I had to do.  What was it in Indy 10 that you wanted?

>I noted discussion of installing Indy 10 in February, and held off until it was a "sure thing". 
>Or sis months, whichever came first. It looks like another six months.
It doesn't seem very promising.  I would love to tackle it myself but I don't have
sufficient knowledge in that area to do it.  

Damon Register