🚀 go-pugleaf

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