🚀 go-pugleaf

I simply copied this exe file from Indy9 pack, and it works for Indy10.
Also I modified FullC6.bat to produce obj and hpp files ( switch -JPHN 
is absent)
After installation I tested the indy10 example and got many error for 
the IdWinsok2.hpp file, and I commented all erronous line, by this way I 
could compile example.

Ed wrote:
> Thank you Vladimir, I did try the fullc5 bat file, before making any posts, 
> and used that with the development snapshot.
> 
> It was error after error, there was a delphi project that needed to be 
> compiled into an exe before the bat file would even run, then on and on from 
> there.
> 
> So I tried the other method that I referred to, but they do not seem to work 
> either. But in my case, perserverance often makes up for a lack of talent. 
> Someday I will figure it out.
> Ed
> "Vladimir Zhuchko" <zhuchko@jinr.ru> wrote in message 
> news:43c8cff3@newsgroups.borland.com...
> 
>>I could compile Indy10 for CB6 using FullC6.bat file, I think it's possible 
>>to do this using FullC5.bat for CB5.
>>But after that you will get package that can be installed to builder, but 
>>you will get many problems with the indy hpp files for the real indy 
>>examples.
>>
>>Ed wrote:
>>
>>>http://www.indyproject.org/Sockets/Docs/Indy10Instal.en.html
>>>
>>>
>>>If open IndySystem with Builder, (step 1 of step 1), I get no project 
>>>compile options. I cannot compile. If I open Builder first, then open the 
>>>Delphi package file, I can compile but it is actually then a member of 
>>>the C++ Builder project (Project1), with Unit1.cpp added by Builder.  It 
>>>may be that I need to try the command line compiler? The words Open and 
>>>compile led me to believe that I should Open then in Builder.
>>>
>>>Same result for step 2 of step 1 and step 3 of step 1.
>>>
>>>As you can see there is  No step 2  under the Installation section.
>>> Unless you count the two step ones...
>>>the first being to download the development snapshot.
>>>
>>>
>>>I thought it could explain why I cannot get step 3 to work. Or I am 
>>>missing
>>>something obvious. I can just never end up with an installable C++ 
>>>builder
>>>package
>>>as a result of those steps, so assumed I must be compiling wrong.
>>>Thank you for looking at my post!
>>>Ed
>>>----- Original Message ----- 
>>>From: "Remy Lebeau (TeamB)" <no.spam@no.spam.com>
>>>Newsgroups: borland.public.cppbuilder.internet.socket
>>>Sent: Friday, January 13, 2006 9:49 AM
>>>Subject: Re: Builder 5 and Indy 10 source instructions
>>>
>>>
>>>
>>>
>>>>"Ed" <enaillon@nvinet.com> wrote in message
>>>>news:43c7af9c$1@newsgroups.borland.com...
>>>>
>>>>
>>>>
>>>>>I have found the installation from source instructions on the
>>>>>indyproject.org site very frustrating.
>>>>
>>>>How so?
>>>>
>>>>
>>>>
>>>>>The site that deals with Indy10Install for BCB has 7 lines of
>>>>>non-specific instruction.
>>>>
>>>>Can you elaborate more?
>>>>
>>>>
>>>>
>>>>>Step one says says Open and Compile four different delphi dpk files.
>>>>
>>>>What is non-specific about that?
>>>>
>>>>
>>>>
>>>>>Are they opened a a new project?
>>>>
>>>>No.  DPK files are Delphi packages, just as BPK file are C++ packages.
>>>>Packages are their own projects, just as BPR file are their own C++
>>>>projects.
>>>>
>>>>
>>>>
>>>>>Just compile the Unit?
>>>>
>>>>The DPK/BPK files are compilable as themselves.  They contain a list of
>>>>source units for the compiler to process.   They are like makefiles (but
>>>>not).
>>>>
>>>>
>>>>
>>>>>Should the project be named anything in particular?
>>>>
>>>>You should not be making new projects to begin with.
>>>>
>>>>
>>>>
>>>>>Should I name them with the bpk extension?
>>>>
>>>>Not unless you have created actual C++ packages.
>>>>
>>>>
>>>>
>>>>>They are delphi package files
>>>>
>>>>Yes.
>>>>
>>>>
>>>>
>>>>>so do not seem to be a valid package to Builder.
>>>>
>>>>BCB includes a command-line Delphi compiler, dcc32.exe, that can compile
>>>>DPK
>>>>files.
>>>>
>>>>
>>>>
>>>>>Then step 3 says...(where the heck is step 2 guys? the page says step
>>>>>one...step  three.. )
>>>>
>>>>What page are you referring to exactly?
>>>>
>>>>
>>>>Gambit
>>>>
>>>>
>>>
>>>
>>>"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message 
>>>news:43c7e795$1@newsgroups.borland.com...
>>>
>>>
>>>>"Ed" <enaillon@nvinet.com> wrote in message
>>>>news:43c7af9c$1@newsgroups.borland.com...
>>>>
>>>>
>>>>
>>>>>I have found the installation from source instructions on the
>>>>>indyproject.org site very frustrating.
>>>>
>>>>How so?
>>>>
>>>>
>>>>
>>>>>The site that deals with Indy10Install for BCB has 7 lines of
>>>>>non-specific instruction.
>>>>
>>>>Can you elaborate more?
>>>>
>>>>
>>>>
>>>>>Step one says says Open and Compile four different delphi dpk files.
>>>>
>>>>What is non-specific about that?
>>>>
>>>>
>>>>
>>>>>Are they opened a a new project?
>>>>
>>>>No.  DPK files are Delphi packages, just as BPK file are C++ packages.
>>>>Packages are their own projects, just as BPR file are their own C++
>>>>projects.
>>>>
>>>>
>>>>
>>>>>Just compile the Unit?
>>>>
>>>>The DPK/BPK files are compilable as themselves.  They contain a list of
>>>>source units for the compiler to process.   They are like makefiles (but
>>>>not).
>>>>
>>>>
>>>>
>>>>>Should the project be named anything in particular?
>>>>
>>>>You should not be making new projects to begin with.
>>>>
>>>>
>>>>
>>>>>Should I name them with the bpk extension?
>>>>
>>>>Not unless you have created actual C++ packages.
>>>>
>>>>
>>>>
>>>>>They are delphi package files
>>>>
>>>>Yes.
>>>>
>>>>
>>>>
>>>>>so do not seem to be a valid package to Builder.
>>>>
>>>>BCB includes a command-line Delphi compiler, dcc32.exe, that can compile 
>>>>DPK
>>>>files.
>>>>
>>>>
>>>>
>>>>>Then step 3 says...(where the heck is step 2 guys? the page says step
>>>>>one...step  three.. )
>>>>
>>>>What page are you referring to exactly?
>>>>
>>>>
>>>>Gambit
>>>>
>>>>
>>>
>>>
>