Thread View: borland.public.cppbuilder.internet.socket
8 messages
8 total messages
Started by Peter Evans
Sat, 24 Dec 2005 02:28
Getting going with Indy 10 and BCB6Pro
Author: Peter Evans
Date: Sat, 24 Dec 2005 02:28
Date: Sat, 24 Dec 2005 02:28
22 lines
1711 bytes
1711 bytes
I have downloaded the latest Indy10 Development Snapshot. Is this where to
start?
In \Lib I see Fullc6.bat - do I use this to compile the system?
Where do I put \Lib to make the Fullc6.bat work? (I have my BCB6Pro in
d:\Program Files\Borland\CBuilder6.)
The steps given are:
Open and compile in the following order:
1.. IndySystem (in Lib\System)
2.. IndyCore (in Lib\Core)
3.. IndyProtocols (in Lib\Protocols)
4.. (leaving out SuperCore for the moment)
How do I do these compiles as I normally use the BCB IDE Alt-P, M option for
that or are they ? (By use of the .bat?)
I would be very grateful to have help on getting going.
TIA,
Peter Evans.
Re: Getting going with Indy 10 and BCB6Pro
Author: Remy Lebeau (TeamB)
Date: Mon, 02 Jan 2006 22:56
Date: Mon, 02 Jan 2006 22:56
10 lines
1202 bytes
1202 bytes
"Peter Evans" <peter-evans@pelcaro.com> wrote in message news:43acb1ff@newsgroups.borland.com... >I have downloaded the latest Indy10 Development Snapshot. Indy 10 does not yet officially support C++ at this time. Gambit
Re: Getting going with Indy 10 and BCB6Pro
Author: Peter Evans
Date: Tue, 03 Jan 2006 19:41
Date: Tue, 03 Jan 2006 19:41
17 lines
1523 bytes
1523 bytes
Thank you Remy for your reply. Peter Evans. "Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message news:43b9b1b0@newsgroups.borland.com... > > "Peter Evans" <peter-evans@pelcaro.com> wrote in message > news:43acb1ff@newsgroups.borland.com... > >>I have downloaded the latest Indy10 Development Snapshot. > > Indy 10 does not yet officially support C++ at this time. > > > Gambit >
Re: Getting going with Indy 10 and BCB6Pro
Author: Vladimir
Date: Tue, 10 Jan 2006 08:50
Date: Tue, 10 Jan 2006 08:50
32 lines
2093 bytes
2093 bytes
I could compile Indy10 for BCB6, but for this I changed FullC6.bat file to get bpl, lib, hpp files. After that I could install Indy10 to CB6 (befor I had to remove Indy9). When I tried to compile some exapmles, I got many error message for idwinsock2.hpp file, to fix these errors I commented erronous lines in the hpp file and got to work indy10 for cb6. The same may be for BDS2006. The main work, as I can is to change IdWinsock2.pas file (as was made for Indy9). Peter Evans wrote: > Thank you Remy for your reply. > > Peter Evans. > > "Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message > news:43b9b1b0@newsgroups.borland.com... > >>"Peter Evans" <peter-evans@pelcaro.com> wrote in message >>news:43acb1ff@newsgroups.borland.com... >> >> >>>I have downloaded the latest Indy10 Development Snapshot. >> >>Indy 10 does not yet officially support C++ at this time. >> >> >>Gambit >> > > >
Re: Getting going with Indy 10 and BCB6Pro
Author: Remy Lebeau (TeamB)
Date: Tue, 10 Jan 2006 19:01
Date: Tue, 10 Jan 2006 19:01
22 lines
1684 bytes
1684 bytes
"Vladimir" <zhuchko@jinr.ru> wrote in message news:43c37569$1@newsgroups.borland.com... > I could compile Indy10 for BCB6, but for this I changed > FullC6.bat file to get bpl, lib, hpp files. The FullC#.bat files should have already outputted those. > When I tried to compile some exapmles, I got many error > message for idwinsock2.hpp file That is because IdWinSock2.pas is not ready for C++ yet. > The main work, as I can is to change IdWinsock2.pas file > (as was made for Indy9). That is a major part of it. But do not use the version from Indy 9. Indy 10's version of IdWinSock2.pas has stuff in it that Indy 9's didn't. Gambit
Re: Getting going with Indy 10 and BCB6Pro
Author: Vladimir
Date: Wed, 11 Jan 2006 06:50
Date: Wed, 11 Jan 2006 06:50
36 lines
2190 bytes
2190 bytes
Remy Lebeau (TeamB) wrote: > "Vladimir" <zhuchko@jinr.ru> wrote in message > news:43c37569$1@newsgroups.borland.com... > > >>I could compile Indy10 for BCB6, but for this I changed >>FullC6.bat file to get bpl, lib, hpp files. > > > The FullC#.bat files should have already outputted those. No, FullC6 is not ready yet, within the command lines the switch -JPHN is absent. > > >>When I tried to compile some examples, I got many error >>message for idwinsock2.hpp file > > > That is because IdWinSock2.pas is not ready for C++ yet. > > >>The main work, as I can is to change IdWinsock2.pas file >>(as was made for Indy9). > > > That is a major part of it. But do not use the version from Indy 9. Indy > 10's version of IdWinSock2.pas has stuff in it that Indy 9's didn't. Yes, I know, but after compilation of the Indy10 I just commented error's lines within idwinsok2.hpp file and then could compile some indy10 examples. > > > Gambit > >
Re: Getting going with Indy 10 and BCB6Pro
Author: Remy Lebeau (TeamB)
Date: Wed, 11 Jan 2006 10:19
Date: Wed, 11 Jan 2006 10:19
13 lines
1537 bytes
1537 bytes
"Vladimir" <zhuchko@jinr.ru> wrote in message news:43c4aaac@newsgroups.borland.com... > Yes, I know, but after compilation of the Indy10 I just commented > error's lines within idwinsok2.hpp file and then could compile some > indy10 examples. The whole point of making IdWinSock2.pas be C++-aware is so that manual edits of IdWinSock2.hpp are not needed at all. Gambit
Re: Getting going with Indy 10 and BCB6Pro
Author: Vladimir
Date: Wed, 11 Jan 2006 10:45
Date: Wed, 11 Jan 2006 10:45
18 lines
1852 bytes
1852 bytes
Remy Lebeau (TeamB) wrote: > "Vladimir" <zhuchko@jinr.ru> wrote in message > news:43c4aaac@newsgroups.borland.com... > > >>Yes, I know, but after compilation of the Indy10 I just commented >>error's lines within idwinsok2.hpp file and then could compile some >>indy10 examples. > > > The whole point of making IdWinSock2.pas be C++-aware is so that manual > edits of IdWinSock2.hpp are not needed at all. > > > Gambit > > Yes, I know, but this is in the future ... (when?)
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