HOW TO INSTALL Indy 10.5.7 in Delphi 2007 IDe from * Tiburon.zip * distribu

Date 25/05/2010
By Davide Spano
e-mail davide.spano@armfield.co.uk




**********************************************************************************
HOW TO INSTALL Indy 10.5.7 in Delphi 2007 IDe from * Tiburon.zip * distribution
**********************************************************************************

  
- 0 What version of Indy I have in my IDE?

  To find out..

   Create a new VCL project with a form and drag whatever of the components that are in the IDE
   Indy tool palette section (TIdTCPClient or other) then right click and select

   About Internet Direct (Indy)...

   You get a nice picture telling clearly what version yo've GOT
    

 -1 Download the Tiburon.zip distribution. At the time ofwriting You find the distribution 
   at the following URI

	http://indy.fulgan.com/ZIP/

   if it is not just google it I am sure you'll find something

-2 Unzip the folder somewhere on your system or network.It contains a lot but do not 
   dispair

-3 Start your Delphi 2007 IDE and make sure no project is loaded, it has to be blank!

-4 Now in Tools-->Option you get a window with a tree and many branches but you care 
   of just two things
 
   - Enviroment Variables: 
    
      this a list of strings that allow Delphi 2007 IDE to shorten the system location
      names (brutally speaking!)

   - Library -Win32 under Delphi Options:

     this is quite more complicated and we go through it bit by bit in a simple way in the
     the following description.There is a help button in the RB corner and you mightwant to
     give a read to that in order to get an idea of what this is all about 		

-5  Let's begin from *Library path*
    
    The IDE needs small blocks of code to make available all the features it is made of i.e.
    components for Run Time and design time and source code of these component for when you
    are debugging hence, you have a way to tell the IDE Where on the system it should look 
    for these blocks.

    On my system for example the Enviromental Variable $(BDS) is

    C:\Program Files\CodeGear\RAD Studio\5.0

    probably this is the case also on yours, but if not do not despair the substance won't change

    have a look here at my library path:
    
    $(BDS)\lib;
    $(BDS)\Source\Indy2009\System;
    $(BDS)\Source\Indy2009\Core;
    $(BDS)\Source\Indy2009\Protocols;
    $(BDS)\bpl;
    $(BDS)\Dcp;
   
    Yours doen't have to be the same this is just to give you an idea of what it might look like
    and now I am going to be more specific

    $(BDS)\lib;
   
    it's very likely also in your library path because there - Code Gear - Embarcadero or whoever      
    makes the IDE put a lot of their stuff which is then used by the IDE itself. Do not touch anything
    here if you don't no what you are doing
   
    You might also have 
	  
    $(BDS)\lib\Indy10                 (this contains the .dcu files for the Indy 10 library)

    this is the same as the $(BDS)\lib I have just talked about, but its importance is limited to the
    Indy features of the IDE. These are actually the features that you want to substitute with a newer 
    version as you can see all these files begin with an Id- prefix and if you suspect that there might
    some other location of your system with such files do a search and find out!

    All these file must 'disappear' either hidden (I prefer this) or deleted to make room for those 
    obtained from the Tiburon.zip you have downloaded, but let's do a step at a time..

    What I did is simply to rename $(BDS)\lib\Indy10 with something like OldIndy_10_v1.1.5 because
    the version of Indy 10 I was using was the 1.1.5 (and I am going to upgrade to the 1.5.7). By
    renaming the folder the IDE will not see it the next time you restart it because this folder is
    not in the library path!

    Of course another option is just the removal of $(BDS)\lib\Indy10 from you library path without
    renaming anything, you choose the method you prefer most the substance is that the IDE must no 
    longer see the old Indy 10 file rather it should see the new files
 			

-6  Some other Indy files are in  	
     
    $(BDS)\bin


    these are not dcu files, rather they are binary files that is .bpl file and also these must be
    hidden.Notice that  $(BDS)\bin might not show in your library path but it is icluded by default
    in fact many aother .bpl files essential to the IDE are also here. These .bpl files are the result
    of the compilation of packages.You will compile some packages shortly

    The way I do this is to create a folder called 

    Indy10_v1.1.5

    this let me avoid deleting anything, you never know! 

    What you should find here are the following


    ****** Run Time binary for Indy 10 **********
    
    Indy100.bpl
    IndyCore100.bpl
    IndyProtocols100.bpl
    IndySystem100.bpl


    ****** Design Time for Indy 10 ********
     
     dclindy100.bpl                    //put this away first 
     dclIndyCore100.bpl                //wait for step [8] to put this away 
     dclIndyCore100.bpl                //wait for step [8] to put this away


    ****** Som DLLs if you have RAD studio ******
    
    dclIndyCore.dll
    dclIndyProtocols.dll
 
    ************ Some .jdbg files ***************
    
    Indy100.jdbg
    dclIndy100.jdbg	


    I suspect the dlls are for CBuilder if you work with RAD Studio rather than with just Delphi
    ,but I do not knot this detail for sure you might find out it googling..the same goes for those
   .jdbg files I do not idea what they are for hence, I store them all together in a folder so that
    I might find out one day!
 
    As far as delphi is concerned instead
 
    the dcl.. files are the result of a compilation of Design Time packages and are those to used 
    by the IDE to make available the Indy components on the tool palette while the Indy..100.bpl 
    files are pretty much the same but contain only the Run Time part of the compile packages.
    To make it clear if you want to use the Indy components from the tool palette you need the IDE
    to find both and not just that tose that are dcl.. prefixed the Design Time must also be installed
    in the IDE and we'll do that shortly

    You could also decide that you do not need the Design Time part and in this case there is not
    *installation* process for the IDE to be performed and only the Run Time part of the newly
    compiled packages has to be found by the IDE. 
    Follow up and you'll understand..


-7 At this point all the old files in $(BDS)\bin and $(BDS)\lib have been put aside in some 
   folders I advice you to look also in 

   C:\Windows\System32 
   
   here you should not find files for Indy like dlls or bpls even though you almost surely find
   som .bpl files if you find Indy files the story is the same store them in a folder well marked
   as old Indy something. Ipersonally did not find anything here!

   The other place is in your share document folder where RAD studio puts something, or you might 
   put something. On my system for example
 

   C:\Documents and Settings\All Users\Documents\RAD Studio\5.0\Bpl 
   C:\Documents and Settings\All Users\Documents\RAD Studio\5.0\Dcp

   I use these two folder to store some other .bpl and .dcp files of thirdy party or my own components
   and I did not find anything related to Indy here either but this might not in your case.Same story here
   to, put what you find aside in a safe folder.


-8 Now you system should be clean of the old files ready to receive the file for the new version of Indy 10
   that we are going to compile, but first a last thing!
   Indy 10 comes already installed when you buy the Delphi 2007 IDE and you find the components in the palette
   but now you have place the ([6]) 
    
   ****** Design Time for Indy 10 ********
     
     dclindy100.bpl
     dclIndyCore100.bpl       //before unistall and put it away
     dclIndyProtocols100.bpl       //before unistall and put it away

   away and if you close the IDE and reopen it you get an error because the IDE cannot find them any longer
   said that before closing the IDE you have to thell it that you want un-install the Indy components from the
   IDE hence, it will not try to load these Design Time code next time you open the IDE.
   To do this do 
  
   Components-->Install Packages

   you should get a list of Design time packages (.bpl files) that  the IDE loads when open and you should find  

   dclIndyCore100.bpl            //before unistall and put it away
   dclIndyProtocols100.bpl       //before unistall and put it away   

   and you also should see there location as system folder when you select them.Remove them using the remove 
   button, and if you think you have messed up something cancel and repeat until you are sure that just thes two
   packages are removed!
   
   After that put the 

   dclIndyCore100.bpl            //before unistall and put it away
   dclIndyProtocols100.bpl       //before unistall and put it away 


   away with the others. If then you restart the IDE and begin with a new Form you'll notice that the Indy component 
   are no longer there. Eventually, your system is clean as if Indy 10 wasn't there in the first place.

-9 Now we start with the second part of the job which consist of putting on the new Indy 10 
  
   File-->Open 

   Go to the IndyTiburon folder you have unzipped earlier where you find three relevant subfolders
 
   -System
   -Core
   -Protocol

   Inside these there are the .dpk projects (delphi packageproject) that you need to compile to create the new 
   Indy 10 (1.5.7) library files (.bpl files) 

   load the following projects in the ordr they are listed 

   IndySystem110.bpl
   IndyCore110.bpl
   IndyProtocols110.bpl
   dcIndyCore110.bpl
   dcIndyProtocols110.bpl


   Notice that now there is a 110 while we put away the 100 version of the files, the correspondence
   should be     
  	

	BDS2006 --> 100
	RAD2007 --> 110 or 100
	RAD2009 --> 120

        RAD2010 -->130 OR 140 (NOT SURE)

   I got this info here
  
   https://forums.embarcadero.com/thread.jspa?messageID=134027

-10 Let's compile!
   
    This is the part where you might get in trouble above all if you are running in MS Vista as I do
    ,the general advice is do notchange anything in the opsions of the 5 projects that are currently
    loaded in the IDE and that you are abot to compile.
    Go to

    Tool-->Options 

    you get the usal window, make sure that *package output directory* points to a directory on your
    system that the IDE can see (no antivirus or thing like that, no network restriction and similar) 
    for instance I decided to point to a folder like

    $(BDS)\bin\CurrentIndy10_1.5.7

    Where I created a new * CurrentIndy10_1.5.7 * that will contain everything about the new Indy 10
    ,this solution is not elegant but it is practical and if you upadte regularly makes it easier to
    repeat the process.
    Hence after compilation the output of the compilation process will be sent to this folder and as 
    you compile the list of the .bpl and .dcp files will grow, but let's do the first bit

    Select IndySystem110.bpl and Compile

    as I said if the system is clean and there are not restriction of the system to writing data to the 
    output folder and so on you should get the  

    IndySystem110.bpl
    IndySystem110.dcp


    compiled into the folder hurray!

    If you get an error it is probably the case in which you cannot write there or the IDE is not cleaned
    but you should not get an error on compiling IndySystem110.bpl

    Now you might think that you can go on to IndyCore110.bpl and you are right except for the fact that you 
    might fail the compilation with an error, why?
   
    Well, chances are that the 

    $(BDS)\bin\CurrentIndy10_1.5.7

    is not in the IDE library path. This is essential because to compile 

    IndyCore110.bpl
  
    the compiler will need to find the the IndySystem110.bpl ( and the IndySystem110.dcp ) infact if you look
    in the Project Manager for the IndyCore110.bpl project in its Required folder you'll find that it needs

    rtl.dcp (Runtime Library of VCL on which almost any .bpl project depends on )
    IndySystem110.dcp  (the one the you've just compiled!) 

    Hence

    Tool-->Options

    and add the library path 
  
    $(BDS)\bin\CurrentIndy10_1.5.7

    now  recompile the project

    IndyCore110.bpl

    and you should get a successful compilation and the list of files in the $(BDS)\bin\CurrentIndy10_1.5.7 grows
     
    At this point you understand that the series
    
    IndySystem110.bpl
    IndyCore110.bpl
    IndyProtocols110.bpl
    dcIndyCore110.bpl
    dcIndyProtocols110.bpl

    must be respected because any project requires something that was compiled in the step the precedes

-11 Now if you want the Design time Support that is the Indy components to be installed in the tool palette
    you need to perform another step. Yo might decide to do without this but I find better to have the tool
    palette with the Indy comps on


    yOU MIGHT NOT KNOW this but if you right click on

    IndySystem110.bpl   

    and select options in the *Description* section you'll find the **Runtime only** option selected
    while for 

    dcIndyCore110.bpl
    dcIndyProtocols110.bpl

    you'll find the ** Design time ** option selected that confirm what I anticipated earlier


    Only 

    dcIndyCore110.bpl
    dcIndyProtocols110.bpl


    will be installed being DT packages


    Select the first and right click then select INSTALL and you get a message saying that a nuber of components 
    have been reghistered with the IDE, finally repeat with the last project and you get the same kind of message

    You can check that everything is ok go to 

    Components-->Install Packages 


    and you get the list of installed Design Time pachages where you oght to find
  
    dcIndyCore110.bpl
    dcIndyProtocols110.bpl

    from

    $(BDS)\bin\CurrentIndy10_1.5.7


   You are done.

   Now last check. Create a new VCL project with a form and drag whatever of the components that are in the IDE
   Indy tool palette section (TIdTCPClient or other) then right click and select

   About Internet Direct (Indy)...

   You get a nice picture telling clearly what version yo've just installed


-12 Source code and .dcu files? 

   If you stop your effort now you will be able to use the new Indy 10 1.5.7 but you will not be able to 
   debug properly and compile. This is because you need to tell the IDE where it can find

   .dcu files = delphi compiled units

   and the 

   .pas = source code for these unit 

   These can be BUILT (when you buid instead of compiling) and in this case in addition to .bpl and .dcp
   you get also .dcu files 

   then to store the .dcu you have to select the project you want to build in the project manager and 
   open the options page and in the section 

   Directories/Conditional

   the Output directory should point where you want the .dcu files to be written. In general though you
   don't need to build because the IndyTiburon folder that you dowloaded already contains all the .pas and
   .dcu files you need this is why I compiled and not built!

   Either way compile or Build then you have to tell the IDE where the .pas and .dcu can be found and that 
   is done adding the library path of the 

   (Where you put it..)/IndyTiburon/Lib


   /System
   /Core
   /Protocols

   And do not forget to remove the reference to 

   C:\Program Files\CodeGear\RAD Studio\5.0\source\Indy\Indy10\

   here you had the source code for the Indy 1.1.5 (old) version

   change name to the folder and avoid the IDE mistake this for the right code in the 

   (Where you put it..)/IndyTiburon/Lib


   /System
   /Core
   /Protocols

   IN REGARD the old dcu files these were

   $(BDS)\lib\Indy10 

  but if you have changed this directory and removed all the reference to it in 

   Tool --> Options -->Library -Win 32

   in 
      -Library Path 
      -Browsing Path
      -Debug DCU path 

   and added the refences to the 
 
   (Where you put it..)/IndyTiburon/Lib


   /System
   /Core
   /Protocols

   then you are done for real and you'll be able to compile and debug properly with the new Indy 10 
   library you have just installed
********************************************************************************************************************




Other links you might want to visit and that I thank for the help given to me

	
https://forums.embarcadero.com/thread.jspa?threadID=23496
htthttps://forums.embarcadero.com/thread.jspa?messageID=134027
http://forums2.atozed.com/viewtopic.php?f=7&t=3110&p=5074
http://forums2.atozed.com/viewtopic.php?f=7&p=2445		
https://forums.embarcadero.com/thread.jspa?threadID=34955&tstart=0              
https://forums.embarcadero.com/thread.jspa?threadID=19011                           
https://forums.embarcadero.com/thread.jspa?threadID=25267&tstart=0
https://forums.embarcadero.com/thread.jspa?messageID=130770
https://forums.embarcadero.com/thread.jspa?messageID=134027
0
Davide
5/26/2010 7:43:44 AM
embarcadero.delphi.tools 5366 articles. 3 followers. Follow

2 Replies
1736 Views

Similar Articles

[PageSpeed] 23

Wow... great reference... thanks to share.......



"Davide Spano" ha scritto nel messaggio 
news:246267@forums.embarcadero.com...
> Date 25/05/2010
> By Davide Spano
> e-mail davide.spano@armfield.co.uk
>
>
>
>
> **********************************************************************************
> HOW TO INSTALL Indy 10.5.7 in Delphi 2007 IDe from * Tiburon.zip * 
> distribution
> **********************************************************************************
>
>
> - 0 What version of Indy I have in my IDE?
>
>  To find out..
>
>   Create a new VCL project with a form and drag whatever of the components 
> that are in the IDE
>   Indy tool palette section (TIdTCPClient or other) then right click and 
> select
>
>   About Internet Direct (Indy)...
>
>   You get a nice picture telling clearly what version yo've GOT
>
>
> -1 Download the Tiburon.zip distribution. At the time ofwriting You find 
> the distribution
>   at the following URI
>
> http://indy.fulgan.com/ZIP/
>
>   if it is not just google it I am sure you'll find something
>
> -2 Unzip the folder somewhere on your system or network.It contains a lot 
> but do not
>   dispair
>
> -3 Start your Delphi 2007 IDE and make sure no project is loaded, it has 
> to be blank!
>
> -4 Now in Tools-->Option you get a window with a tree and many branches 
> but you care
>   of just two things
>
>   - Enviroment Variables:
>
>      this a list of strings that allow Delphi 2007 IDE to shorten the 
> system location
>      names (brutally speaking!)
>
>   - Library -Win32 under Delphi Options:
>
>     this is quite more complicated and we go through it bit by bit in a 
> simple way in the
>     the following description.There is a help button in the RB corner and 
> you mightwant to
>     give a read to that in order to get an idea of what this is all about
>
> -5  Let's begin from *Library path*
>
>    The IDE needs small blocks of code to make available all the features 
> it is made of i.e.
>    components for Run Time and design time and source code of these 
> component for when you
>    are debugging hence, you have a way to tell the IDE Where on the system 
> it should look
>    for these blocks.
>
>    On my system for example the Enviromental Variable $(BDS) is
>
>    C:\Program Files\CodeGear\RAD Studio\5.0
>
>    probably this is the case also on yours, but if not do not despair the 
> substance won't change
>
>    have a look here at my library path:
>
>    $(BDS)\lib;
>    $(BDS)\Source\Indy2009\System;
>    $(BDS)\Source\Indy2009\Core;
>    $(BDS)\Source\Indy2009\Protocols;
>    $(BDS)\bpl;
>    $(BDS)\Dcp;
>
>    Yours doen't have to be the same this is just to give you an idea of 
> what it might look like
>    and now I am going to be more specific
>
>    $(BDS)\lib;
>
>    it's very likely also in your library path because there - Code Gear - 
> Embarcadero or whoever
>    makes the IDE put a lot of their stuff which is then used by the IDE 
> itself. Do not touch anything
>    here if you don't no what you are doing
>
>    You might also have
>
>    $(BDS)\lib\Indy10                 (this contains the .dcu files for the 
> Indy 10 library)
>
>    this is the same as the $(BDS)\lib I have just talked about, but its 
> importance is limited to the
>    Indy features of the IDE. These are actually the features that you want 
> to substitute with a newer
>    version as you can see all these files begin with an Id- prefix and if 
> you suspect that there might
>    some other location of your system with such files do a search and find 
> out!
>
>    All these file must 'disappear' either hidden (I prefer this) or 
> deleted to make room for those
>    obtained from the Tiburon.zip you have downloaded, but let's do a step 
> at a time..
>
>    What I did is simply to rename $(BDS)\lib\Indy10 with something like 
> OldIndy_10_v1.1.5 because
>    the version of Indy 10 I was using was the 1.1.5 (and I am going to 
> upgrade to the 1.5.7). By
>    renaming the folder the IDE will not see it the next time you restart 
> it because this folder is
>    not in the library path!
>
>    Of course another option is just the removal of $(BDS)\lib\Indy10 from 
> you library path without
>    renaming anything, you choose the method you prefer most the substance 
> is that the IDE must no
>    longer see the old Indy 10 file rather it should see the new files
>
>
> -6  Some other Indy files are in
>
>    $(BDS)\bin
>
>
>    these are not dcu files, rather they are binary files that is .bpl file 
> and also these must be
>    hidden.Notice that  $(BDS)\bin might not show in your library path but 
> it is icluded by default
>    in fact many aother .bpl files essential to the IDE are also here. 
> These .bpl files are the result
>    of the compilation of packages.You will compile some packages shortly
>
>    The way I do this is to create a folder called
>
>    Indy10_v1.1.5
>
>    this let me avoid deleting anything, you never know!
>
>    What you should find here are the following
>
>
>    ****** Run Time binary for Indy 10 **********
>
>    Indy100.bpl
>    IndyCore100.bpl
>    IndyProtocols100.bpl
>    IndySystem100.bpl
>
>
>    ****** Design Time for Indy 10 ********
>
>     dclindy100.bpl                    //put this away first
>     dclIndyCore100.bpl                //wait for step [8] to put this away
>     dclIndyCore100.bpl                //wait for step [8] to put this away
>
>
>    ****** Som DLLs if you have RAD studio ******
>
>    dclIndyCore.dll
>    dclIndyProtocols.dll
>
>    ************ Some .jdbg files ***************
>
>    Indy100.jdbg
>    dclIndy100.jdbg
>
>
>    I suspect the dlls are for CBuilder if you work with RAD Studio rather 
> than with just Delphi
>    ,but I do not knot this detail for sure you might find out it 
> googling..the same goes for those
>   .jdbg files I do not idea what they are for hence, I store them all 
> together in a folder so that
>    I might find out one day!
>
>    As far as delphi is concerned instead
>
>    the dcl.. files are the result of a compilation of Design Time packages 
> and are those to used
>    by the IDE to make available the Indy components on the tool palette 
> while the Indy..100.bpl
>    files are pretty much the same but contain only the Run Time part of 
> the compile packages.
>    To make it clear if you want to use the Indy components from the tool 
> palette you need the IDE
>    to find both and not just that tose that are dcl.. prefixed the Design 
> Time must also be installed
>    in the IDE and we'll do that shortly
>
>    You could also decide that you do not need the Design Time part and in 
> this case there is not
>    *installation* process for the IDE to be performed and only the Run 
> Time part of the newly
>    compiled packages has to be found by the IDE.
>    Follow up and you'll understand..
>
>
> -7 At this point all the old files in $(BDS)\bin and $(BDS)\lib have been 
> put aside in some
>   folders I advice you to look also in
>
>   C:\Windows\System32
>
>   here you should not find files for Indy like dlls or bpls even though 
> you almost surely find
>   som .bpl files if you find Indy files the story is the same store them 
> in a folder well marked
>   as old Indy something. Ipersonally did not find anything here!
>
>   The other place is in your share document folder where RAD studio puts 
> something, or you might
>   put something. On my system for example
>
>
>   C:\Documents and Settings\All Users\Documents\RAD Studio\5.0\Bpl
>   C:\Documents and Settings\All Users\Documents\RAD Studio\5.0\Dcp
>
>   I use these two folder to store some other .bpl and .dcp files of thirdy 
> party or my own components
>   and I did not find anything related to Indy here either but this might 
> not in your case.Same story here
>   to, put what you find aside in a safe folder.
>
>
> -8 Now you system should be clean of the old files ready to receive the 
> file for the new version of Indy 10
>   that we are going to compile, but first a last thing!
>   Indy 10 comes already installed when you buy the Delphi 2007 IDE and you 
> find the components in the palette
>   but now you have place the ([6])
>
>   ****** Design Time for Indy 10 ********
>
>     dclindy100.bpl
>     dclIndyCore100.bpl       //before unistall and put it away
>     dclIndyProtocols100.bpl       //before unistall and put it away
>
>   away and if you close the IDE and reopen it you get an error because the 
> IDE cannot find them any longer
>   said that before closing the IDE you have to thell it that you want 
> un-install the Indy components from the
>   IDE hence, it will not try to load these Design Time code next time you 
> open the IDE.
>   To do this do
>
>   Components-->Install Packages
>
>   you should get a list of Design time packages (.bpl files) that  the IDE 
> loads when open and you should find
>
>   dclIndyCore100.bpl            //before unistall and put it away
>   dclIndyProtocols100.bpl       //before unistall and put it away
>
>   and you also should see there location as system folder when you select 
> them.Remove them using the remove
>   button, and if you think you have messed up something cancel and repeat 
> until you are sure that just thes two
>   packages are removed!
>
>   After that put the
>
>   dclIndyCore100.bpl            //before unistall and put it away
>   dclIndyProtocols100.bpl       //before unistall and put it away
>
>
>   away with the others. If then you restart the IDE and begin with a new 
> Form you'll notice that the Indy component
>   are no longer there. Eventually, your system is clean as if Indy 10 
> wasn't there in the first place.
>
> -9 Now we start with the second part of the job which consist of putting 
> on the new Indy 10
>
>   File-->Open
>
>   Go to the IndyTiburon folder you have unzipped earlier where you find 
> three relevant subfolders
>
>   -System
>   -Core
>   -Protocol
>
>   Inside these there are the .dpk projects (delphi packageproject) that 
> you need to compile to create the new
>   Indy 10 (1.5.7) library files (.bpl files)
>
>   load the following projects in the ordr they are listed
>
>   IndySystem110.bpl
>   IndyCore110.bpl
>   IndyProtocols110.bpl
>   dcIndyCore110.bpl
>   dcIndyProtocols110.bpl
>
>
>   Notice that now there is a 110 while we put away the 100 version of the 
> files, the correspondence
>   should be
>
>
> BDS2006 --> 100
> RAD2007 --> 110 or 100
> RAD2009 --> 120
>
>        RAD2010 -->130 OR 140 (NOT SURE)
>
>   I got this info here
>
>   https://forums.embarcadero.com/thread.jspa?messageID=134027
>
> -10 Let's compile!
>
>    This is the part where you might get in trouble above all if you are 
> running in MS Vista as I do
>    ,the general advice is do notchange anything in the opsions of the 5 
> projects that are currently
>    loaded in the IDE and that you are abot to compile.
>    Go to
>
>    Tool-->Options
>
>    you get the usal window, make sure that *package output directory* 
> points to a directory on your
>    system that the IDE can see (no antivirus or thing like that, no 
> network restriction and similar)
>    for instance I decided to point to a folder like
>
>    $(BDS)\bin\CurrentIndy10_1.5.7
>
>    Where I created a new * CurrentIndy10_1.5.7 * that will contain 
> everything about the new Indy 10
>    ,this solution is not elegant but it is practical and if you upadte 
> regularly makes it easier to
>    repeat the process.
>    Hence after compilation the output of the compilation process will be 
> sent to this folder and as
>    you compile the list of the .bpl and .dcp files will grow, but let's do 
> the first bit
>
>    Select IndySystem110.bpl and Compile
>
>    as I said if the system is clean and there are not restriction of the 
> system to writing data to the
>    output folder and so on you should get the
>
>    IndySystem110.bpl
>    IndySystem110.dcp
>
>
>    compiled into the folder hurray!
>
>    If you get an error it is probably the case in which you cannot write 
> there or the IDE is not cleaned
>    but you should not get an error on compiling IndySystem110.bpl
>
>    Now you might think that you can go on to IndyCore110.bpl and you are 
> right except for the fact that you
>    might fail the compilation with an error, why?
>
>    Well, chances are that the
>
>    $(BDS)\bin\CurrentIndy10_1.5.7
>
>    is not in the IDE library path. This is essential because to compile
>
>    IndyCore110.bpl
>
>    the compiler will need to find the the IndySystem110.bpl ( and the 
> IndySystem110.dcp ) infact if you look
>    in the Project Manager for the IndyCore110.bpl project in its Required 
> folder you'll find that it needs
>
>    rtl.dcp (Runtime Library of VCL on which almost any .bpl project 
> depends on )
>    IndySystem110.dcp  (the one the you've just compiled!)
>
>    Hence
>
>    Tool-->Options
>
>    and add the library path
>
>    $(BDS)\bin\CurrentIndy10_1.5.7
>
>    now  recompile the project
>
>    IndyCore110.bpl
>
>    and you should get a successful compilation and the list of files in 
> the $(BDS)\bin\CurrentIndy10_1.5.7 grows
>
>    At this point you understand that the series
>
>    IndySystem110.bpl
>    IndyCore110.bpl
>    IndyProtocols110.bpl
>    dcIndyCore110.bpl
>    dcIndyProtocols110.bpl
>
>    must be respected because any project requires something that was 
> compiled in the step the precedes
>
> -11 Now if you want the Design time Support that is the Indy components to 
> be installed in the tool palette
>    you need to perform another step. Yo might decide to do without this 
> but I find better to have the tool
>    palette with the Indy comps on
>
>
>    yOU MIGHT NOT KNOW this but if you right click on
>
>    IndySystem110.bpl
>
>    and select options in the *Description* section you'll find the 
> **Runtime only** option selected
>    while for
>
>    dcIndyCore110.bpl
>    dcIndyProtocols110.bpl
>
>    you'll find the ** Design time ** option selected that confirm what I 
> anticipated earlier
>
>
>    Only
>
>    dcIndyCore110.bpl
>    dcIndyProtocols110.bpl
>
>
>    will be installed being DT packages
>
>
>    Select the first and right click then select INSTALL and you get a 
> message saying that a nuber of components
>    have been reghistered with the IDE, finally repeat with the last 
> project and you get the same kind of message
>
>    You can check that everything is ok go to
>
>    Components-->Install Packages
>
>
>    and you get the list of installed Design Time pachages where you oght 
> to find
>
>    dcIndyCore110.bpl
>    dcIndyProtocols110.bpl
>
>    from
>
>    $(BDS)\bin\CurrentIndy10_1.5.7
>
>
>   You are done.
>
>   Now last check. Create a new VCL project with a form and drag whatever 
> of the components that are in the IDE
>   Indy tool palette section (TIdTCPClient or other) then right click and 
> select
>
>   About Internet Direct (Indy)...
>
>   You get a nice picture telling clearly what version yo've just installed
>
>
> -12 Source code and .dcu files?
>
>   If you stop your effort now you will be able to use the new Indy 10 
> 1.5.7 but you will not be able to
>   debug properly and compile. This is because you need to tell the IDE 
> where it can find
>
>   .dcu files = delphi compiled units
>
>   and the
>
>   .pas = source code for these unit
>
>   These can be BUILT (when you buid instead of compiling) and in this case 
> in addition to .bpl and .dcp
>   you get also .dcu files
>
>   then to store the .dcu you have to select the project you want to build 
> in the project manager and
>   open the options page and in the section
>
>   Directories/Conditional
>
>   the Output directory should point where you want the .dcu files to be 
> written. In general though you
>   don't need to build because the IndyTiburon folder that you dowloaded 
> already contains all the .pas and
>   .dcu files you need this is why I compiled and not built!
>
>   Either way compile or Build then you have to tell the IDE where the .pas 
> and .dcu can be found and that
>   is done adding the library path of the
>
>   (Where you put it..)/IndyTiburon/Lib
>
>
>   /System
>   /Core
>   /Protocols
>
>   And do not forget to remove the reference to
>
>   C:\Program Files\CodeGear\RAD Studio\5.0\source\Indy\Indy10\
>
>   here you had the source code for the Indy 1.1.5 (old) version
>
>   change name to the folder and avoid the IDE mistake this for the right 
> code in the
>
>   (Where you put it..)/IndyTiburon/Lib
>
>
>   /System
>   /Core
>   /Protocols
>
>   IN REGARD the old dcu files these were
>
>   $(BDS)\lib\Indy10
>
>  but if you have changed this directory and removed all the reference to 
> it in
>
>   Tool --> Options -->Library -Win 32
>
>   in
>      -Library Path
>      -Browsing Path
>      -Debug DCU path
>
>   and added the refences to the
>
>   (Where you put it..)/IndyTiburon/Lib
>
>
>   /System
>   /Core
>   /Protocols
>
>   then you are done for real and you'll be able to compile and debug 
> properly with the new Indy 10
>   library you have just installed
> ********************************************************************************************************************
>
>
>
>
> Other links you might want to visit and that I thank for the help given to 
> me
>
>
> https://forums.embarcadero.com/thread.jspa?threadID=23496
> htthttps://forums.embarcadero.com/thread.jspa?messageID=134027
> http://forums2.atozed.com/viewtopic.php?f=7&t=3110&p=5074
> http://forums2.atozed.com/viewtopic.php?f=7&p=2445
> https://forums.embarcadero.com/thread.jspa?threadID=34955&tstart=0
> https://forums.embarcadero.com/thread.jspa?threadID=19011
> https://forums.embarcadero.com/thread.jspa?threadID=25267&tstart=0
> https://forums.embarcadero.com/thread.jspa?messageID=130770
> https://forums.embarcadero.com/thread.jspa?messageID=134027
0
Roberto
5/26/2010 10:20:33 PM
Roberto Icardi wrote:

> Wow... great reference... thanks to share.......

+1

> > ******************************************************************
> > HOW TO INSTALL Indy 10.5.7 in Delphi 2007 IDe from * Tiburon.zip * 
> > distribution
> > ******************************************************************
> > [snipped]

But, please, the next time, trim the post you're replying to, no need
to leave all 700+ lines in it, in this case.

-- 
Pieter

"If you pray for rain long enough, it eventually does fall. If
 you pray for floodwaters to abate, they eventually do. The same
 happens in the absence of prayers."
 -- Steve Allen
0
Pieter
5/26/2010 10:52:04 PM
Reply:

Similar Artilces:

Converting Delphi 2007 Indy 10.2.3 to Delphi 2009 Indy 10.5.5 [Edit]
Hello, I am currently attempting to port over a Delphi 2007 project that uses Indy 10.2.3 (very successfully) to Delphi 2009 and Indy 10.5.5 (I just got the latest development build this morning). I think I am running into an encoding issue, but am not sure. Specifically, IDHTTP with SSL calls an old CGI and the CGI returns a .zip file and I then save it to the disk. In 2007 and before this worked perfectly. In 2009, it is not. Here is the examples of the 2 different results (though cut way short in the post) I am getting back: 2007: 'PK'#3#4#$14#0#0#0#8#0'rLQ9žrPb€'#0...

Encoding issues with Delphi 2007 and Indy 10.5.5
Hi, I'm using the last snapshot of Indy 10 (Rev 3539) with Delphi 2007 under a French version of Windows Vista. I just discovered that some characters wasn't transferred correctly, probably since the Unicode update (AFAIK that worked fine with Indy 10.2.3). They are replaced by '?' on the other end of the connection. For instance, this code : procedure TForm2.Button1Click(Sender: TObject); begin IdTCPClient1.Connect; IdTCPClient1.IOHandler.WriteLn('£'); end; procedure TForm2.IdTCPServer1Execute(AContext: TIdContext); var S: string;...

Indy 10 Installation Delphi 5
Hi, As a result of this POODLE thing, I have to upgrade our Delphi 5 program to use TLS instead of SSL3, so I was trying to upgrade from Indy 9 to Indy 10 (does some version of Indy 9 support TLSv1.2?). So after running the batch file that comes with the installation (Full_5.bat) and installing the component in Delphi 5. I go and drop a idIOhandlerSSL or whatever onto an empty form and get an error: "Stack overflow - save your work and restart Delphi" Anyone know how to get the installation to work? Thanks! Orren wrote: > As a result of this POODLE thing, I have t...

Delphi 2007 to Delphi 7
I've written a class in Delphi 2007 that is not supported in Delphi 7. What would be the best way to achive what I've done in Delphi 2007 in Delphi 7? Thanks, Tom type BondConstants = class { Bond Types } type BondType = record const TREASURY = 3; AGENCY = 0; CORP = 1; MUNI = 2; SBA = 5; MBS = 4; CMO = 6; end; { Day Count Methods } type DayCount = record const ACTUAL_360 = 2; ACTUAL_365 = 1; ACTUAL_ACTUAL = 1; d30_360 = 0; ...

delphi 7 Indy 9 and Indy 10
Hi, I can upgrade to indy 10 in delphi 7. But I have discover that indy 9 and Indy 10 have some different properties, so i had to change my old programs that were made in indy 9 to upgrade it to new version, but it is a long work. So I want to know if it is possible to install in the same delphi 7 both versions indy 10 and indy 9. I have tried to do it but i received a error message: Cannot load package 'IndySystem70'. It contains unit 'IdWinSock2', which is also contained in package 'Indy70'. Some can give me ideas or a link to read how to install both versi...

Moving from Delphi 7 to Delphi 2007
Is there any compelling reason to move (quite a large project) from Delphi 7 to Delphi 2007? Specifically, is there better Vista/Win7/Win8 integration provided by Delphi 2007? (In the project I am already using a custom manifest file for Vista/Win7 etc.. and not the std XPMan component) Does 2007 add any new bugs to the scene? Thanks Rael Rael wrote: > Is there any compelling reason to move (quite a large project) from > Delphi 7 to Delphi 2007? If you are going to upgrade, why not upgrade to something newer? > In the project I am already using a custom man...

Delphi 2007 RTL in Delphi 7
I read somewhere that it is possible to use Delphi 2007's (or for that matter Delphi 2006's) RTL in Delphi 7 by just recompiling the source of RTL. Is this really possible? What are the benefits that we can derive using a higher version's RTL? TIA Yogi Yang Yogi Yang wrote: > I read somewhere that it is possible to use Delphi 2007's (or for > that matter Delphi 2006's) RTL in Delphi 7 by just recompiling the > source of RTL. If it actually compiles in Delphi 7, I guess it would be possible. OTOH, if one has Delphi 2007 already, I don't s...

Delphi 2007
Hi, I'm trying to install the latest build of Indy 10. I downloaded the following zip from "http://indy.fulgan.com/ZIP": *Monday, October 13, 2008 11:32 PM 6697544 indy10.zip* What I did with the zip: 1. I unzipped indy10.zip. 2. I removed my current Indy 10 from Delphi 2007 3. I opened Indy100Net.dpk and compiled it. I got the following 2 errors: [DCC Error] Indy100Net.dpk(4): E1030 Invalid compiler directive: 'ALIGN' [DCC Error] Indy100Net.dpk(30): E2202 Required package 'Borland.Delphi' not found package Indy100Net; {$R *.res} *{$...

Indy E-Mail Problem (Indy 10, Delphi 2007)
Hello, we use Indy 10 with Delphi 2007 to get E-Mail using IMAP. We recieved an E-Mail which is not handled correctly. The E-Mail looks like this {code} Return-Path: <test@mail.com>; From: "Test Tester" <test@mail.com>; To: <test@mail.com>; Subject: Order Date: Wed, 7 Mar 2012 16:50:40 +0100 Message-ID: <15D526BEB8091D43859549D9E16E370FBA3123> MIME-Version: 1.0 Content-Type: text/html; charset=US-ASCII Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQFk6K6fcF3...

Installing Delphi 7 and Delphi XE5 on same machine
Is there any implication installing Delphi 7 and XE5 on a same machine? Will it affect the 3rd party components, libraries, dll etc.? On 15/12/2013 23:56, Ebizit IT wrote: > Is there any implication installing Delphi 7 and XE5 on a same machine? Will it affect the 3rd party components, libraries, dll etc.? Ebizit, The usual guideline is to install in release order, Delphi 7 first, then XE5. I would also advise installing in a dedicated, security open directory such as: C:\Tools\Delphi-7 C:\Tools\Delphi-XE5 However, since I cannot afford the grossly inflated pric...

how to install indy on Delphi 2007
I have tried to install indy 10 but I'm doing something wrong because I get errors when I try to compile the core. where can I find the best way to install this regards Mats When I use the IndyTiburon and run de fullD11.dpk I get an error compiling E2466 Never-Build Package, IndyCore120 I have built the IndySystem120 without any error but when I run fullD11.dpk it still gives me this error. anu sugestions? regards Mats "Mats Carlsson" <master@rdit.se> skrev i meddelandet news:220408@forums.codegear.com... >I have tried to install indy 10...

Is possible to install delphi 7 and delphi 2009 upgrade?
I have delphi 7 interprise installed on my PC. Our company bought a delphi 2009 professional (upgrade). All of our projects now are made in delphi 7. We don't have time to move those projects to delphi 2009. Now, we are planning to create a new project using delphi 2009. Is it possible to install delphi 2009 in different windows profile without affecting delphi 7 projects? Edwin Aceron wrote: > I have delphi 7 interprise installed on my PC. Our company bought a > delphi 2009 professional (upgrade). All of our projects now are made > in delphi 7. We don't have time to move...

Project Manager Delphi 2007 vs Delphi 5
I am in the midst of moving from Delphi 5 to Delphi 2007. I have a .BAT file that I use to do some post processing on the executable after it is built. In Delphi 5, I just added the .BAT file to the project manager. Then when I wanted to execute the .BAT file I just right clicked its entry in the project manager and selected Execute. There doesn't seem to be anyway to add the .BAT file to the project manager in Delphi 2007. How can I set up something similar to what I had in Delphi 5? I thought about using a Post Build event but I don't necessarily want to execute the .BAT fi...

Memory usage in Delphi 2007 vs. Delphi 5
Going from Delphi 5 to Delphi 2007 and finding something way unexpected. The reportedly *same code, and same data,* uses about 104 MB in Delphi 5 and about 400 MB in Delphi 2007 according to the Windows Task Manager. Now, I know that it is not the most accurate way of measuring memory usage, but it gives us an idea of the proportion of memory use in Delphi 2007. Before we go deeper, we just created 20,000 objects and added them to an object list in Delphi 5 and 2007. The result in memory use still looks like 50 MB (Delphi 5) to 178 MB (Delphi 2007). We've downloaded ...

Web resources about - HOW TO INSTALL Indy 10.5.7 in Delphi 2007 IDe from * Tiburon.zip * distribu - embarcadero.delphi.tools

Bravais lattice - Wikipedia, the free encyclopedia
are known as the primitive vectors which lie in different directions and span the lattice. This discrete set of vectors must be closed under ...

Post-war “austerity”
... group as “erroneous,” although there were different degrees of correctness and error in both groups. The outstanding feature in the distribution ...

clipkit Gets T-Venture and IBB Backing
... their 24-strong team. With the increase in staff, the mis-sion for 2012 is to extend national and international partnerships focused on distribu-tion ...

Google Cancels eBooks Reseller Program, Dropping Indies
Login Register Publishers Lunch The Publishing Industry's Daily Essential Read Publishers Marketplace Site Guide Help Subscribe to RSS by Michael ...

Could Kickstarter Replace The NEA?
That's the buzz : One of the company’s three co-founders, Yancey Strickler , said that Kickstarter is on track to distribue over $150 million ...

Philosophie et Histoire
Quel but a cette quête mystérieuse de l’homme, qui cherche à retrouver ce qui n’existe plus, sans ignorer que le travail sera tout autant aléatoire ...

Africa: Regimes Under Attack From Satire and Cartoons
... CFA”, désigne la monnaie gabonaise qui était autrefois à l’effigie du défunt président Omar Bongo. Le terme se rapporte aussi à l’argent distribué ...

Sign Up for Research Updates - HCCI
... your privacy. We appreciate that you are trusting us with your information and we will not break that trust. We will never sell or distribu... ...

The Environment and the Economy
The Environment and the Economy

Quercus Results Decline Over 20 Percent On Larsson Falloff
Login Register Publishers Lunch The Publishing Industry's Daily Essential Read Publishers Marketplace Site Guide Help Subscribe to RSS by Michael ...

Resources last updated: 1/18/2016 9:36:59 PM