🚀 go-pugleaf

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