🚀 go-pugleaf

Eduardo Jauch escreveu:
> Hello...
> 
> I try to follow the steps in the Knowledge of Indy to install...
> 
> But when I try to add the package dclindy60.bpl, I receive this error:
> 
> Enter point do not finded.
> 
> @Idresourcestrings@_RSBindinAny
> 
> 
> Anyone can help me?

I'll forget this and try the version 10...

Eduardo Jauch escreveu:
> Eduardo Jauch escreveu:
>> Hello...
>>
>> I try to follow the steps in the Knowledge of Indy to install...
>>
>> But when I try to add the package dclindy60.bpl, I receive this error:
>>
>> Enter point do not finded.
>>
>> @Idresourcestrings@_RSBindinAny
>>
>>
>> Anyone can help me?
> 
> I'll forget this and try the version 10...

I compiled the computil file with dcc32.
Then run the fullc6.bat

Get these warnings:

N�o foi poss�vel encontrar C:\Indy10\*.dcu
N�o foi poss�vel encontrar C:\Indy10\*.dcp
Adding compile_ok file
N�o foi poss�vel encontrar C:\Indy10\compile_run


When I tried to add the IndySystem60.bpl, get an error:

Can't be instaled because is not a design time package...

What I do?

Another question...

Where are the *.lib and the *.hpp???

From the Indy website, although I used this with 9.0.50 DevSnapshot.


How do I install Indy into Borland C++ Builder?

. Close the Borland C++ Builder IDE if it is open.

. Temporarily copy IDPAS32.obj to a temporary directory.  You do not want to 
delete that file because it is NOT part of the Indy package.

. Remove all Indy files including dclindy*.bpl, dclindy.*, dclindy*.bpl, 
indy*.lib, id*.pas, id*.hpp, id*.obj, and id*.dcu. Take care that you only 
remove the old Indy files and not something else. Be sure that you also 
remove any indy*.bpl from your Windows\System32 directory.

. Restore IDPAS32.obj from the temporary directory you created earlier to 
the directory where it was originally located.

. Remove all old Indy Help files, indy.*,  from the Help subdirectory and 
replace them with the new ones.

. Place the new version of Indy in a directory of your choice.  When 
unzipping, please keep the \source directory for the archive intact because 
that is used by some build batch files.

. In the source directory, there are several batch files.  Run the 
appropriate one for your version of Borland C++ Builder:

. FULLC4.BAT - Borland C++ Builder 4

. FULLC5.BAT - Borland C++ Builder 5

. FULLC6.BAT - Borland C++ Builder 6

. These batch files create subdirectories in the main Indy directory folder. 
They are (C4 for C++Builder 4, C5 for C+Builder 5, and C6 for C++Builder 6). 
These directories contain:

. The Indy .DCU files

. The Indy .HPP files

. The Indy .LIB file

. The Indy .OBJ files

. The Indy Design-Time .BPL

. Open the Borland C++ Builder IDE.

. In your C++Builder IDE, add the Indy design-time package with 
Component|Install Package...|Add...  Go to the subdirectory where the Indy 
.DCU's and Design-Time .BPL was placed by the batch file.  Add the 
Design-Time .BPL that is listed.  It usually is named dclIndy followed by 
the Borland C++ Builder version and an 0.

. Add the path where the .DCU's are located to your environment.  Do this 
with Tools|Environment Options...|Library...|Library Path...

. Add the path where the .HPP's are located to your project. Do this with 
Project|Options|Directories|Conditionals|Include path. Check the box Default 
and click OK to save this setting.


"Eduardo Jauch" <eduardo.jauch@gmail.com> wrote in message 
news:45c4222b$1@newsgroups.borland.com...
> Another question...
>
> Where are the *.lib and the *.hpp??? 

Jello Paul :)

I tried to folow this...

But with the version 10, there are no sub-directories in C6...
And there are no HPP, nor the BPI or LIB files that are asked when I 
load the BPL files...

And 3 of the 5 BPL file are not really BPL...

I really don't know if I'm making some mistake (I must of course)...

> But with the version 10, there are no sub-directories in C6...
> And there are no HPP,

I also tried install indy10 in Builder 6 - it not possible (no HPP files...)

I thought that in Indy 9 is converted (compiled) the PAS files in to the HPP 
files, they weren't there to start off with (just looked at my archive).

Regards,

Paul

"Natasha" <vmyletterbox@yandex.ru> wrote in message 
news:45c5ed1c@newsgroups.borland.com...
>
>> But with the version 10, there are no sub-directories in C6...
>> And there are no HPP,
>
> I also tried install indy10 in Builder 6 - it not possible (no HPP 
> files...)
>
>
> 

"Paul at NCF" <notplmacca@clara.co.uk> wrote in message
news:45c78d7b$1@newsgroups.borland.com...

> I thought that in Indy 9 is converted (compiled) the PAS files in to
> the HPP files, they weren't there to start off with (just looked at
my archive).

Yes, the Pascal compiler does produce HPP files during compiling -
IF - the command-line parameters tell it to.  Which leads me to think
that people are not installing Indy in the correct manner to begin
with.  I do compile both Indy 9 and 10 from command-line scripts, and
HPP files are always generated properly.


Gambit

Remy Lebeau (TeamB) escreveu:
> "Paul at NCF" <notplmacca@clara.co.uk> wrote in message
> news:45c78d7b$1@newsgroups.borland.com...
> 
>> I thought that in Indy 9 is converted (compiled) the PAS files in to
>> the HPP files, they weren't there to start off with (just looked at
> my archive).
> 
> Yes, the Pascal compiler does produce HPP files during compiling -
> IF - the command-line parameters tell it to.  Which leads me to think
> that people are not installing Indy in the correct manner to begin
> with.  I do compile both Indy 9 and 10 from command-line scripts, and
> HPP files are always generated properly.
> 
> 
> Gambit
> 
> 

Hum...

Can you shw the line to compile the units? I don't find what parameter 
use...

Thanks :)

Remy Lebeau (TeamB) wrote:
> "Paul at NCF" <notplmacca@clara.co.uk> wrote in message
> news:45c78d7b$1@newsgroups.borland.com...
> 
>> I thought that in Indy 9 is converted (compiled) the PAS files in to
>> the HPP files, they weren't there to start off with (just looked at
> my archive).
> 
> Yes, the Pascal compiler does produce HPP files during compiling -
> IF - the command-line parameters tell it to.  Which leads me to think
> that people are not installing Indy in the correct manner to begin
> with.  I do compile both Indy 9 and 10 from command-line scripts, and
> HPP files are always generated properly.
> 
> 
> Gambit

Comprehensive documentation would be welcome.  But I can also see how 
time-consuming such a production might be in a moving project that has 
to support 5 versions of two compilers....

I see people asking both about BCB6 and BDS 2006, sometimes for Indy 10. 
  Last year, when I migrated from another library to Indy, I spent some 
quality time getting Indy 9 to work enough with C++ in BDS 2006 in one 
project that I could build working software.  I think I link specific 
OBJ files to get it all to work.  It's not good--hard to understand why 
it works and certainly hard to reproduce.  (Some LIBs are also linked.)

Yesterday I decided to try Indy 10 with C++ in BDS 2006 again--because 
it looks like you've worked to make Indy 10 work with Borland's more 
recent C++ compiler and IDE environments.  I've done these things:

- added a SetupCA (10) to computil.dpr that knows where to find BDS 
2006's bin directory.

- updated fullc6.bat to be aware of BDS 2006, including using dcc32's 
command line switches that make HPP and OBJ files during the compile 
(-NO, -NH, -JPH).  These changes appear to compile without error.  I now 
see HPP and OBJ files but don't really know what other files should be made.

- So I get five BPLs in the C6 directory (as before), but also get HPP 
and OBJ files there.  I'd guess I could add that directory--C6--to my 
include path, install the BPL files, and be pretty close to having a 
working VCL approach for Indy 10 in a C++ VCL project.  Do you agree?

- I'd also like to have working LIBs.  When I worked on this last year, 
the fullc6.bat file made LIB files using a response file I got from the 
zip file for some other version of Indy 9.  Fullc6.bat doesn't seem to 
make LIBs now, so I don't know what LIB files need to be made or which 
OBJ files to put in each.  Without that knowledge it would likely be a 
fool's errand to spend much more time on this--I might have cascading 
unresolved references and never know how to get back on track.

So I look forward to your guidance, Remy.


Thanks!

Frank Burleigh escreveu:

> 
> - added a SetupCA (10) to computil.dpr that knows where to find BDS 
> 2006's bin directory.
> 

How you add this? What is exactly SetupCA (10)?

> - updated fullc6.bat to be aware of BDS 2006, including using dcc32's 
> command line switches that make HPP and OBJ files during the compile 
> (-NO, -NH, -JPH).  These changes appear to compile without error.  I now 
> see HPP and OBJ files but don't really know what other files should be 
> made.
> 
> - So I get five BPLs in the C6 directory (as before), but also get HPP 
> and OBJ files there.  I'd guess I could add that directory--C6--to my 
> include path, install the BPL files, and be pretty close to having a 
> working VCL approach for Indy 10 in a C++ VCL project.  Do you agree?
> 
> - I'd also like to have working LIBs.  When I worked on this last year, 
> the fullc6.bat file made LIB files using a response file I got from the 
> zip file for some other version of Indy 9.  Fullc6.bat doesn't seem to 
> make LIBs now, so I don't know what LIB files need to be made or which 
> OBJ files to put in each.  Without that knowledge it would likely be a 
> fool's errand to spend much more time on this--I might have cascading 
> unresolved references and never know how to get back on track.
> 

I think that only TWO of these BPL files are really BPL... (Only two my 
BCB 6 understand luke that...

 From what I see, I think that the other THREE BPL, are really BPI... 
(I'll try to change the extension and see if works...)

Please, what files are needed and how to create the hree lib files that 
my projects allways asking and are in nowhere...
And FULLC6 Don't create them. I take a look in the bat file...

Thanks :)

Remy Lebeau (TeamB) escreveu:
> "Paul at NCF" <notplmacca@clara.co.uk> wrote in message
> news:45c78d7b$1@newsgroups.borland.com...
> 
>> I thought that in Indy 9 is converted (compiled) the PAS files in to
>> the HPP files, they weren't there to start off with (just looked at
> my archive).
> 
> Yes, the Pascal compiler does produce HPP files during compiling -
> IF - the command-line parameters tell it to.  Which leads me to think
> that people are not installing Indy in the correct manner to begin
> with.  I do compile both Indy 9 and 10 from command-line scripts, and
> HPP files are always generated properly.
> 
> 
> Gambit
> 
> 

Eduardo Jauch wrote:
> Frank Burleigh escreveu:
> 
>>
>> - added a SetupCA (10) to computil.dpr that knows where to find BDS 
>> 2006's bin directory.
>>
> 
> How you add this? What is exactly SetupCA (10)?

If you're still using BCB6 I don't think you need to do this.  My edits 
to the computil.dpr unit just add the path to BDS 2006's bin directory 
so that Remy's batch file can compile.  After the edits, you compile 
computil.exe like this:

dcc32 computil.dpr

Remy's build process needs computil.exe to manipulate some environment 
variables and to create a setenv.bat file.

[sni[]

> 
> I think that only TWO of these BPL files are really BPL... (Only two my 
> BCB 6 understand luke that...
> 
>  From what I see, I think that the other THREE BPL, are really BPI... 
> (I'll try to change the extension and see if works...)
> 

Ok.  Thanks for that.  What *are* BPI files, anyway?

Frank Burleigh escreveu:
> Eduardo Jauch wrote:
>> Frank Burleigh escreveu:
>>
>>>
>>> - added a SetupCA (10) to computil.dpr that knows where to find BDS 
>>> 2006's bin directory.
>>>
>>
>> How you add this? What is exactly SetupCA (10)?
> 
> If you're still using BCB6 I don't think you need to do this.  My edits 
> to the computil.dpr unit just add the path to BDS 2006's bin directory 
> so that Remy's batch file can compile.  After the edits, you compile 
> computil.exe like this:
> 
> dcc32 computil.dpr
> 
> Remy's build process needs computil.exe to manipulate some environment 
> variables and to create a setenv.bat file.
> 
> [sni[]

OK :)

> 
>>
>> I think that only TWO of these BPL files are really BPL... (Only two 
>> my BCB 6 understand luke that...
>>
>>  From what I see, I think that the other THREE BPL, are really BPI... 
>> (I'll try to change the extension and see if works...)
>>
> 
> Ok.  Thanks for that.  What *are* BPI files, anyway?

I don't know for shure...

The help says this:

"...when you statically link with the BPL's import library, which has 
the extension .BPI (for "Borland Package Import Library)..."

So I think that are librarys linked statically...

Anyway, I figured that the files I THINK were BPI, don't where...

The Fullc�.bat have problems with path, and the three bpi files needed 
are on other directories then C6...

The LIB's are not created, so I create myself using the obj's in the 
Core (IndyCore60.lib), System (IndySystem60.lib) and Protocols 
(IndyProtocols.lib), but there are few files that I don't know if must 
be included or not in the libs...

"Frank Burleigh" <burleigh@indiana.edu> wrote in message
news:45c9dcbc$1@newsgroups.borland.com...

> If you're still using BCB6 I don't think you need to do this.  My
edits
> to the computil.dpr unit just add the path to BDS 2006's bin
directory
> so that Remy's batch file can compile.

The .bat files are not needed in order to compile Indy for BDS 2006.
With the merging of C++ and Delphi into a single unified IDE, the .dpk
files can be loaded and compiled directly in the IDE for installing
Indy in both personalities.  That is why computil.exe was never
updated to look for BDS's compiler.

The only downside to compiling the .dpk files inside the IDE is that
the "BCB" conditional has to be defined manually inside the Core
package, or else IdIPAddress.pas will not compile correctly (an
"unsupported language feature" error will occur).  The .bat files
define "BCB" at the command-line level for the compiler to pick up
automatically.

> Remy's build process needs computil.exe to manipulate some
> environment variables and to create a setenv.bat file.

It is not my build process.  Indy was using .bat files long before I
started using Indy.

> What *are* BPI files, anyway?

A .bpi file is an import lib for a .bpl library.  When runtime
packages are enabled in the project, .bpi/bpl are used.  When runtime
packages are disabled, a static .lib is used instead.


Gambit

Remy Lebeau (TeamB) wrote:
> "Frank Burleigh" <burleigh@indiana.edu> wrote in message
> news:45c9dcbc$1@newsgroups.borland.com...
> 
>> If you're still using BCB6 I don't think you need to do this.  My
> edits
>> to the computil.dpr unit just add the path to BDS 2006's bin
> directory
>> so that Remy's batch file can compile.
> 
> The .bat files are not needed in order to compile Indy for BDS 2006.
> With the merging of C++ and Delphi into a single unified IDE, the .dpk
> files can be loaded and compiled directly in the IDE for installing
> Indy in both personalities.  That is why computil.exe was never
> updated to look for BDS's compiler.
> 
> The only downside to compiling the .dpk files inside the IDE is that
> the "BCB" conditional has to be defined manually inside the Core
> package, or else IdIPAddress.pas will not compile correctly (an
> "unsupported language feature" error will occur).  The .bat files
> define "BCB" at the command-line level for the compiler to pick up
> automatically.

I predict the text above will be seen in future as some of the best 
information and news for all people who need help!

So I did these steps:

1. Deleted all that I'd done earlier and unzipped indy10.zip.

2. Opened and compiled these projects:

- lib\system\IndySystem100.bdsproj
- lib\core\dclIndyCore100.bdsproj (no complaints about idipaddress)
- lib\protocols\dclIndyProtocols100.bdsproj

3. That left these files in my bpl output directory:

02/07/2007  09:15 PM           390,656 dclIndyCore100.bpl
02/07/2007  09:15 PM            56,953 dclIndyCore100.dcp
02/07/2007  09:16 PM           292,864 dclIndyProtocols100.bpl
02/07/2007  09:16 PM            40,653 dclIndyProtocols100.dcp
02/07/2007  09:14 PM           303,104 IndyCore100.bpl
02/07/2007  09:14 PM           707,814 IndyCore100.dcp
02/07/2007  09:16 PM         1,795,584 IndyProtocols100.bpl
02/07/2007  09:16 PM         3,084,529 IndyProtocols100.dcp
02/07/2007  09:13 PM           145,408 IndySystem100.bpl
02/07/2007  09:13 PM           372,357 IndySystem100.dcp

4. I told BDS to remove Indy Core and Indy Protocols but I have not yet 
deleted the original dcu and dcp files from ($BDS)\lib\indy10, nor have 
I removed from ($BDS)\bin all the Indy related files there.  These newly 
compiled BPLs do not exactly parallel what I see in BDS's bin directory. 
  Maybe Indy's a little restructured, maybe some bin\* files relate to 
.net, etc.

5. ($BDS)\lib\indy10 contains one OBJ file: idantifreeze.obj.

6. I imagine the next step would be to replace the old DCUs with the 
newly-compiled ones, remove the Indy BPLs from ($BDS\bin, place the new 
BPLs somewhere sensible, then add dclIndyProtocols100 and dclIndyCore100 
to the packages.

But I think I'll stop in hopes Remy will comment on this direction.

Also, what does the file prefix "dcl" mean--it's used a lot besides in Indy.

>> Remy's build process needs computil.exe to manipulate some
>> environment variables and to create a setenv.bat file.
> 
> It is not my build process.  Indy was using .bat files long before I
> started using Indy.

No offense intended. ;-)

>> What *are* BPI files, anyway?
> 
> A .bpi file is an import lib for a .bpl library.  When runtime
> packages are enabled in the project, .bpi/bpl are used.  When runtime
> packages are disabled, a static .lib is used instead.

So there's still the question how to make LIBs for C++ development where 
Indy objects might be created with new()...

> Gambit

Thanks Remy.

"Frank Burleigh" <burleigh@indiana.edu> wrote in message
news:45ca8ed2@newsgroups.borland.com...

> 2. Opened and compiled these projects:
<snip>
> - lib\core\dclIndyCore100.bdsproj (no complaints about idipaddress)

If you have the C++ personality loaded at the time, then you should
get an "unsupported language feature: property of array type" error.
TIdIPAddress has an IPv6 property that can't be used in C++.  That is
why it has an {$IFDEF BCB}block wrapped around it in IdIPAddress.pas.

> These newly compiled BPLs do not exactly parallel what I see
> in BDS's bin directory.

I wouldn't expect them to.  There have been changes to Indy since BDS
was released.

> what does the file prefix "dcl" mean--it's used a lot besides in
Indy.

"dcl" packages are usually design-time packages.


Gambit