🚀 go-pugleaf

"roladdon" <roladdon@PutMyServerHere.ca> wrote in message 
news:4765b072$1@newsgroups.borland.com...

> I want to update Indy to the latest version.
> wich of the packages do I have to compile ?

The numbers in the package names coorespond to the version of the compiler 
they are meant for (50 for BCB/D v5, 60 for BCB/D v6, etc).  The packages 
with "Net" in the name are for .NET only.


Gambit 

Remy,

I'm not clear on this either. Should we use "100", "110", or "120" with C++
2007? Thanks.

Joe

"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message
news:4766b27c$1@newsgroups.borland.com...
>
> "roladdon" <roladdon@PutMyServerHere.ca> wrote in message
> news:4765b072$1@newsgroups.borland.com...
>
> > I want to update Indy to the latest version.
> > wich of the packages do I have to compile ?
>
> The numbers in the package names coorespond to the version of the compiler
> they are meant for (50 for BCB/D v5, 60 for BCB/D v6, etc).  The packages
> with "Net" in the name are for .NET only.
>
>
> Gambit
>
>

I have  - CBuilder 2007 :
"CodeGearT C++Builder� 2007  Version 11.0.2804.9245 Copyright � 2007 
CodeGearT. All Rights Reserved"
So it's version 11 - right ? - so use:    dclIndyCore110.dpk  ?

I downloaded the latest dev. snapshot zip file from 
ftp://indy.fulgan.com/ZIP/indy10.zip

When I try to open  (File->Open) \Lib\Core\dclIndyCore110.dpk  in 
Cbuilder2007 - nothing happens.
No error message either. - but the file is also not loaded.

What am I doing wrong?

thanks,

Roland

"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message 
news:4766b27c$1@newsgroups.borland.com...
>
> "roladdon" <roladdon@PutMyServerHere.ca> wrote in message 
> news:4765b072$1@newsgroups.borland.com...
>
>> I want to update Indy to the latest version.
>> wich of the packages do I have to compile ?
>
> The numbers in the package names coorespond to the version of the compiler 
> they are meant for (50 for BCB/D v5, 60 for BCB/D v6, etc).  The packages 
> with "Net" in the name are for .NET only.
>
>
> Gambit
> 

"Joe Pasquariello" <joep@fenway.com> wrote in message 
news:4766c3fb$1@newsgroups.borland.com...

> I'm not clear on this either. Should we use "100", "110",
> or "120" with C++ 2007?

"110" is for BDS 2006, but 2007 is backwards compatible with 2006, so either 
"110" or "120" will work.  I have "110" installed myself, but only because 
there were no "120" packages available yet at the time.


Gambit 

"roladdon" <roladdon@PutMyServerHere.ca> wrote in message 
news:4766c462$1@newsgroups.borland.com...

> I downloaded the latest dev. snapshot zip file from 
> ftp://indy.fulgan.com/ZIP/indy10.zip
>
> When I try to open  (File->Open) \Lib\Core\dclIndyCore110.dpk
> in Cbuilder2007 - nothing happens.
> No error message either. - but the file is also not loaded.

If you don't have the Delphi personality installed, then you can't open DPKs 
in the IDE.  You will have to compile them usung the command-line dcc32.exe 
compiler instead.


Gambit 

Thanks. I've seen BDS2006 referred to as C10, and I've seen one component
vendor refer to C++ 2007 as C11, but I hadn't seen any references to version
12. Is this how CodeGear refers to the compiler versions internally? It
doesn't seem to be used consistently by 3rd-party component vendors.

"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message
news:4766cdf5@newsgroups.borland.com...
>
> "Joe Pasquariello" <joep@fenway.com> wrote in message
> news:4766c3fb$1@newsgroups.borland.com...
>
> > I'm not clear on this either. Should we use "100", "110",
> > or "120" with C++ 2007?
>
> "110" is for BDS 2006, but 2007 is backwards compatible with 2006, so
either
> "110" or "120" will work.  I have "110" installed myself, but only because
> there were no "120" packages available yet at the time.
>
>
> Gambit
>
>

"Joe Pasquariello" <joep@fenway.com> wrote in message 
news:4766d83d$1@newsgroups.borland.com...

> Thanks. I've seen BDS2006 referred to as C10, and I've seen one
> component vendor refer to C++ 2007 as C11, but I hadn't seen
> any references to version 12.

C++Builder 2007 and RAD studio 2007 were released separately.  Accordingly 
to IdCompilerDefines.inc, 10 is for BDS 2006, 11 is for the pre-studio 
releases of C++/Delphi 2007, and 12 is RAD Studio 2007.

> Is this how CodeGear refers to the compiler versions internally?

No.  The compiler has its own version number that is separate from the IDE 
version number.  The package numbers don't coorespond to either version 
number specifically, mainly because Borland/CodeGear themselves haven't 
referred to products by sequential release numbers since Delphi 8.  Delphi 9 
was Delphi 2005 (there was no C++ 2005) , C++/Delphi 10 was BDS 2006, etc. 
As the product lines continue to merge, the release numbers get more 
blurred.


Gambit 

Will this work without the delphi personality?
I found this in the help file:

_________________________________________________________
ms-help://borland.bds5/devcommon/compdesigntimepkgdelphi_xml.html :

C++Builder supports compiling design-time packages that contain Delphi
source files. However, if any of those Delphi sources make reference to
IDE-supplied design-time units such as DesignIntf, DesignEditors, and
ToolsAPI that exist in DesignIDE100.bpl, you must take steps to ensure that
the references can be resolved by the C++Builder package.

To compile design-time packages that contain Delphi source
  1.. The Delphi compiler must be able to resolve units in the DesignIDE
package. To enable this, in the C++Builder package project, go to
ProjectOptionsDelphi CompilerOther Options.
  2.. Add -LUDesignIDE to the Additional Options field.
  3.. The C++ linker must be able to resolve the reference inside the
compiled design-time .obj to link. To allow this, in the C++Builder package
project, select the ProjectAdd To ProjectRequires tab.
  4.. In the Package name field, enter designide.bpi and click OK.
You can now compile and install your C++Builder package.

____________________________________________________________________
thanks,

Roland


"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message 
news:4766ce43@newsgroups.borland.com...
>
> "roladdon" <roladdon@PutMyServerHere.ca> wrote in message 
> news:4766c462$1@newsgroups.borland.com...
>
>> I downloaded the latest dev. snapshot zip file from 
>> ftp://indy.fulgan.com/ZIP/indy10.zip
>>
>> When I try to open  (File->Open) \Lib\Core\dclIndyCore110.dpk
>> in Cbuilder2007 - nothing happens.
>> No error message either. - but the file is also not loaded.
>
> If you don't have the Delphi personality installed, then you can't open 
> DPKs in the IDE.  You will have to compile them usung the command-line 
> dcc32.exe compiler instead.
>
>
> Gambit
> 

Inany case it's confusing - because under help->about it says:

"CodeGearT C++Builder� 2007  Version 11.0.2804.9245 Copyright � 2007
CodeGearT. All Rights Reserved"

thanks,
Roland

"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message 
news:4766eb53$1@newsgroups.borland.com...
>
> "Joe Pasquariello" <joep@fenway.com> wrote in message 
> news:4766d83d$1@newsgroups.borland.com...
>
>> Thanks. I've seen BDS2006 referred to as C10, and I've seen one
>> component vendor refer to C++ 2007 as C11, but I hadn't seen
>> any references to version 12.
>
> C++Builder 2007 and RAD studio 2007 were released separately.  Accordingly 
> to IdCompilerDefines.inc, 10 is for BDS 2006, 11 is for the pre-studio 
> releases of C++/Delphi 2007, and 12 is RAD Studio 2007.
>
>> Is this how CodeGear refers to the compiler versions internally?
>
> No.  The compiler has its own version number that is separate from the IDE 
> version number.  The package numbers don't coorespond to either version 
> number specifically, mainly because Borland/CodeGear themselves haven't 
> referred to products by sequential release numbers since Delphi 8.  Delphi 
> 9 was Delphi 2005 (there was no C++ 2005) , C++/Delphi 10 was BDS 2006, 
> etc. As the product lines continue to merge, the release numbers get more 
> blurred.
>
>
> Gambit
> 

"roladdon" <roladdon@PutMyServerHere.ca> wrote in message 
news:4766f66e$1@newsgroups.borland.com...

> Will this work without the delphi personality?

Yes.  Those steps have always existed in every version of BCB.


Gambit 

OK - I did a manual compile - I changed one of the existing  .bat files (see 
source code below)
(it looks like it worked - but I havn't installed the components into 
CBuilder2007 yet)

I am looking at the difference between what's in
     C:\Program Files\CodeGear\RAD Studio\5.0\bin
and what I generated with my   fullc12.bat  file

C:\Program Files\CodeGear\RAD Studio\5.0\bin
also contains:
     deployindy100.bpl, indy100.bpl  and  dclindy100.bpl

Do I need theese ?
and if so - How do I generate them?

thanks,
Roland

FileName: fullc12.bat
________________________________________________________
@echo off

if (%1)==() goto test_command
if (%1)==(start) goto start
goto endok

:test_command
if (%COMSPEC%)==() goto no_command
%COMSPEC% /E:9216 /C %0 start %1 %2 %3
goto endok

:no_command
echo No Command Interpreter found
goto endok

:start
call clean.bat
REM computil SetupC6

SET NDC12=C:\Progra~1\CodeGear\RADStu~1\5.0
SET NDWINSYS=C:\WINDOWS\system32

if not exist ..\C120\*.* md ..\C120 >nul
if exist ..\C120\*.* call clean.bat ..\C120\

if (%NDC12%)==() goto enderror
if (%NDWINSYS%)==() goto enderror

ECHO ****************
ECHO  Compile System
ECHO ****************
CD System
if not exist IndySystem120.res Copy IndySystem100.res IndySystem120.res
%NDC12%\Bin\dcc32.exe IndySystem120.dpk /Oobjs /m /h /w 
/N..\..\C120 -$d-l-n+p+r-s-t-w- %2 %3 %4
if errorlevel 1 goto enderror
ECHO  Compile System Success
copy *120.bpl ..\..\C120 >nul
copy *120.dcp ..\..\C120 >nul
REM copy ..\..\C120\IndySystem120.bpl %NDWINSYS% >nul
CD ..

ECHO **************
ECHO  Compile Core
ECHO **************
CD Core
if not exist IndyCore120.res Copy IndyCore100.res IndyCore120.res
%NDC12%\Bin\dcc32.exe IndyCore120.dpk /Oobjs /m /h /w /N..\..\C120 
/U..\..\C120 -$d-l-n+p+r-s-t-w- %2 %3 %4
if errorlevel 1 goto enderror
if not exist dclIndyCore120.res Copy dclIndyCore100.res dclIndyCore120.res
%NDC12%\Bin\dcc32.exe dclIndyCore120.dpk /Oobjs /m /h /w /z /N..\..\C120 
/U..\..\C120 -$d-l-n+p+r-s-t-w- %2 %3 %4
if errorlevel 1 goto enderror
copy *120.bpl ..\..\C120 >nul
copy *120.dcp ..\..\C120 >nul
REM copy ..\..\C120\IndyCore120.bpl %NDWINSYS% >nul
REM copy ..\..\C120\dclIndyCore120.bpl %NDWINSYS% >nul
CD ..

ECHO *******************
ECHO  Compile Protocols
ECHO *******************
CD Protocols

ECHO ************************
ECHO  IdCompressionIntercept
ECHO ************************
%NDC12%\Bin\dcc32.exe -B -M -N..\..\C120 /U..\..\C120 -H -W -Z 
IdCompressionIntercept.pas -$d-l-
if errorlevel 1 goto enderror
if not exist IndyProtocols120.res Copy IndyProtocols100.res 
IndyProtocols120.res
%NDC12%\Bin\dcc32.exe IndyProtocols120.dpk /Oobjs /m /h /w /N..\..\C120 
/U..\..\C120 -$d-l-n+p+r-s-t-w- %2 %3 %4
if errorlevel 1 goto enderror
if not exist dclIndyProtocols120.res Copy dclIndyProtocols90.res 
dclIndyProtocols120.res
%NDC12%\Bin\dcc32.exe dclIndyProtocols120.dpk /Oobjs /m /h /w /N..\..\C120 
/U..\..\C120 -$d-l-n+p+r-s-t-w- %2 %3 %4
if errorlevel 1 goto enderror

copy *120.bpl ..\..\C120 >nul
copy *120.dcp ..\..\C120 >nul
REM copy ..\..\C120\IndyProtocols120.bpl %NDWINSYS% >nul
REM copy ..\..\C120\dclIndyProtocols120.bpl %NDWINSYS% >nul
CD ..

goto endok
:enderror
CD ..
call clean.bat
echo Error!
:endok
@pause

"roladdon" <roladdon@PutMyServerHere.ca> wrote in message
news:476719a0$1@newsgroups.borland.com...

> C:\Program Files\CodeGear\RAD Studio\5.0\bin
> also contains:
>      deployindy100.bpl, indy100.bpl  and  dclindy100.bpl

I don't know what deployindy100 is.  I've never seen that before.  But the
other two files are for Indy 9, not Indy 10.


Gambit

So what do you suggest to remove old Indy?
Yes - delete the old packages.
but then -
1) Should I remove everything with "Indy" in it, in the  CodeGear and in the 
Win directory - just to be on the save side.
or
2) should I simply add a include path to the new directory putting it first 
in the list without deleting anything

Roland 

I installed deployindy100.bpl
it says:
"codegear depolyment manager indy packages"
it does not have any components.
(it did come with my original CBuilder2007 install)

Roland


"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message 
news:47674582$1@newsgroups.borland.com...
>
> "roladdon" <roladdon@PutMyServerHere.ca> wrote in message
> news:476719a0$1@newsgroups.borland.com...
>
>> C:\Program Files\CodeGear\RAD Studio\5.0\bin
>> also contains:
>>      deployindy100.bpl, indy100.bpl  and  dclindy100.bpl
>
> I don't know what deployindy100 is.  I've never seen that before.  But the
> other two files are for Indy 9, not Indy 10.
>
>
> Gambit
>
> 

I figured it out.
It's best to remove all the old indy files.
The chance is to high that different file versions are mixed up.
Also - then none of the existing project files need to be changed.

Roland

"roladdon" <roladdon@PutMyServerHere.ca> wrote in message 
news:4767e8d4$1@newsgroups.borland.com...
> So what do you suggest to remove old Indy?
> Yes - delete the old packages.
> but then -
> 1) Should I remove everything with "Indy" in it, in the  CodeGear and in 
> the Win directory - just to be on the save side.
> or
> 2) should I simply add a include path to the new directory putting it 
> first in the list without deleting anything
>
> Roland
> 

Roland,

It sounds like you've made a lot of progress. Would you be willing to share
what you learned so that we can try to develop a procedure that others can
use and avoid some of the learning curve?

Joe


"roladdon" <roladdon@PutMyServerHere.ca> wrote in message
news:476969f7$1@newsgroups.borland.com...
> I figured it out.
> It's best to remove all the old indy files.
> The chance is to high that different file versions are mixed up.
> Also - then none of the existing project files need to be changed.
>
> Roland
>
> "roladdon" <roladdon@PutMyServerHere.ca> wrote in message
> news:4767e8d4$1@newsgroups.borland.com...
> > So what do you suggest to remove old Indy?
> > Yes - delete the old packages.
> > but then -
> > 1) Should I remove everything with "Indy" in it, in the  CodeGear and in
> > the Win directory - just to be on the save side.
> > or
> > 2) should I simply add a include path to the new directory putting it
> > first in the list without deleting anything
> >
> > Roland
> >
>
>

This is the bat to backup and remove old Indy - this works on my computer - 
may need to be adjusted to fit yours

BackupRemoveIndyRadStudio.bat
_________________________________________________________
@echo off

if not (%COMSPEC%)==() goto start
echo No Command Interpreter found
goto EndExit

:start

SET NDCBuilder=C:\Progra~1\CodeGear\RADStu~1\5.0
SET NDCBuilderBackUp=C:\Progra~1\CodeGear\RADStu~1\BackUp5.0
if not exist %NDCBuilderBackUp%\*.* md %NDCBuilderBackUp% >nul

if (%NDCBuilder%)==() goto enderrmsg
if not exist %NDCBuilder% goto enderrmsg
if not exist %NDCBuilderBackUp% goto enderrmsg

if not exist %NDCBuilderBackUp%\Bin\*.* md %NDCBuilderBackUp%\Bin >nul
move %NDCBuilder%\Bin\*Indy*.bpl %NDCBuilderBackUp%\Bin
move %NDCBuilder%\Bin\*Indy*.jdbg %NDCBuilderBackUp%\Bin


if not exist %NDCBuilderBackUp%\include\*.* md %NDCBuilderBackUp%\include 
 >nul
if not exist %NDCBuilderBackUp%\include\Indy10\*.* md 
%NDCBuilderBackUp%\include\Indy10 >nul
move %NDCBuilder%\include\Indy10\*.* %NDCBuilderBackUp%\include\Indy10


if not exist %NDCBuilderBackUp%\source\*.* md %NDCBuilderBackUp%\source >nul
if not exist %NDCBuilderBackUp%\source\Indy\*.* md 
%NDCBuilderBackUp%\source\Indy >nul
if not exist %NDCBuilderBackUp%\source\Indy\Indy10\*.* md 
%NDCBuilderBackUp%\source\Indy\Indy10 >nul

if not exist %NDCBuilderBackUp%\source\Indy\Indy10\System\*.* md 
%NDCBuilderBackUp%\source\Indy\Indy10\System >nul
move %NDCBuilder%\source\Indy\Indy10\System\*.* 
%NDCBuilderBackUp%\source\Indy\Indy10\System

if not exist %NDCBuilderBackUp%\source\Indy\Indy10\Protocols\*.* md 
%NDCBuilderBackUp%\source\Indy\Indy10\Protocols >nul
move %NDCBuilder%\source\Indy\Indy10\Protocols\*.* 
%NDCBuilderBackUp%\source\Indy\Indy10\Protocols


if not exist %NDCBuilderBackUp%\source\Indy\Indy10\Core\*.* md 
%NDCBuilderBackUp%\source\Indy\Indy10\Core >nul
move %NDCBuilder%\source\Indy\Indy10\Core\*.* 
%NDCBuilderBackUp%\source\Indy\Indy10\Core

if not exist %NDCBuilderBackUp%\Help\*.* md %NDCBuilderBackUp%\Help >nul
if not exist %NDCBuilderBackUp%\Help\Doc\*.* md %NDCBuilderBackUp%\Help\Doc 
 >nul
if not exist %NDCBuilderBackUp%\Help\Doc\Indy\*.* md 
%NDCBuilderBackUp%\Help\Doc\Indy >nul
move %NDCBuilder%\Help\Doc\Indy\*.* %NDCBuilderBackUp%\Help\Doc\Indy

if not exist %NDCBuilderBackUp%\lib\*.* md %NDCBuilderBackUp%\lib >nul
if not exist %NDCBuilderBackUp%\lib\Indy10\*.* md 
%NDCBuilderBackUp%\lib\Indy10 >nul
move %NDCBuilder%\lib\Indy10\*.* %NDCBuilderBackUp%\lib\Indy10

if not exist %NDCBuilderBackUp%\lib\release\*.* md 
%NDCBuilderBackUp%\lib\release >nul
move %NDCBuilder%\lib\release\*Indy*.bpi %NDCBuilderBackUp%\lib\release
move %NDCBuilder%\lib\release\*Indy*.lib %NDCBuilderBackUp%\lib\release

if not exist %NDCBuilderBackUp%\lib\debug\*.* md 
%NDCBuilderBackUp%\lib\debug >nul
move %NDCBuilder%\lib\debug\*Indy*.bpi %NDCBuilderBackUp%\lib\debug
move %NDCBuilder%\lib\debug\*Indy*.lib %NDCBuilderBackUp%\lib\debug


if not exist %NDCBuilderBackUp%\lib\debug\Indy10\*.* md 
%NDCBuilderBackUp%\lib\debug\Indy10 >nul
move %NDCBuilder%\lib\debug\Indy10\*.* %NDCBuilderBackUp%\lib\debug\Indy10

goto EndExit
:enderrmsg
Echo Error ! ! !

:EndExit
Echo End Batch File
@Pause
_________________________________________________________ 

This is the bat to recreate the exact CBuilder2007 directory structure.
Put it into the same dir where the other  Indy bat files are. (Full4.bat, 
Full5.Bat, ......)
The Directory created is called "C120"  simply copy all items in the dir to 
C:\Program Files\CodeGear\RAD Studio\5.0
Again - this works on my computer - may need to be djusted to fit yours - 
run at your own risk.
The issue remaining is the difference between debug and release version:
    What is it that should be specified  in the .dpk  file  and commandline.


Fullc120.bat
______________________________________________
@echo off

if not (%COMSPEC%)==() goto start
echo No Command Interpreter found
goto EndExit

:start
call clean.bat

SET NDCBuilder=C:\Progra~1\CodeGear\RADStu~1\5.0
SET NDWINSYS=C:\WINDOWS\system32
SET NDIdSource=E:\d\Cbuild~3\Indy10

SET NDIdSystem=%NDIdSource%\C120\source\Indy\Indy10\System
SET NDIdCore=%NDIdSource%\C120\source\Indy\Indy10\Core
SET NDIdProtocols=%NDIdSource%\C120\source\Indy\Indy10\Protocols
Set NDIdDcu=%NDIdSource%\C120\lib\Indy10
Set NDIdDcp=%NDIdSource%\C120\lib\Indy10
Set NDIdHpp=%NDIdSource%\C120\include\Indy10
Set NDIdBpi=%NDIdSource%\C120\lib\release
Set NDIdLib=%NDIdSource%\C120\lib\release
Set NDIdBpl=%NDIdSource%\C120\Bin

Rem Debug directories

Set dNDIdDcu=%NDIdSource%\C120\lib\debug\Indy10
Set dNDIdBpi=%NDIdSource%\C120\lib\debug
Set dNDIdLib=%NDIdSource%\C120\lib\debug

if (%NDCBuilder%)==() goto enderrmsg
if not exist %NDCBuilder% goto enderrmsg
if not exist %NDWINSYS% goto enderrmsg

@Echo Delete manually the  C120Bin  directory now
@Pause
if not exist %NDIdSource%\C120\Bin\*.* md %NDIdSource%\C120\Bin >nul

if not exist %NDIdSource%\C120\include\*.* md %NDIdSource%\C120\include >nul
if not exist %NDIdSource%\C120\include\Indy10\*.* md 
%NDIdSource%\C120\include\Indy10 >nul

if not exist %NDIdSource%\C120\source\*.* md %NDIdSource%\C120\source >nul
if not exist %NDIdSource%\C120\source\Indy\*.* md 
%NDIdSource%\C120\source\Indy >nul
if not exist %NDIdSource%\C120\source\Indy\Indy10\*.* md 
%NDIdSource%\C120\source\Indy\Indy10 >nul
if not exist %NDIdSource%\C120\source\Indy\Indy10\System\*.* md 
%NDIdSource%\C120\source\Indy\Indy10\System >nul
if not exist %NDIdSource%\C120\source\Indy\Indy10\System\Obj\*.* md 
%NDIdSource%\C120\source\Indy\Indy10\System\obj >nul

if not exist %NDIdSource%\C120\source\Indy\Indy10\Protocols\*.* md 
%NDIdSource%\C120\source\Indy\Indy10\Protocols >nul
if not exist %NDIdSource%\C120\source\Indy\Indy10\Protocols\Obj\*.* md 
%NDIdSource%\C120\source\Indy\Indy10\Protocols\Obj >nul

if not exist %NDIdSource%\C120\source\Indy\Indy10\Core\*.* md 
%NDIdSource%\C120\source\Indy\Indy10\Core >nul
if not exist %NDIdSource%\C120\source\Indy\Indy10\Core\Obj\*.* md 
%NDIdSource%\C120\source\Indy\Indy10\Core\Obj >nul

if not exist %NDIdSource%\C120\Help\*.* md %NDIdSource%\C120\Help >nul
if not exist %NDIdSource%\C120\Help\Doc\*.* md %NDIdSource%\C120\Help\Doc 
 >nul
if not exist %NDIdSource%\C120\Help\Doc\Indy\*.* md 
%NDIdSource%\C120\Help\Doc\Indy >nul

if not exist %NDIdSource%\C120\lib\*.* md %NDIdSource%\C120\lib >nul
if not exist %NDIdSource%\C120\lib\Indy10\*.* md 
%NDIdSource%\C120\lib\Indy10 >nul
if not exist %NDIdSource%\C120\lib\release\*.* md 
%NDIdSource%\C120\lib\release >nul
if not exist %NDIdSource%\C120\lib\debug\*.* md %NDIdSource%\C120\lib\debug 
 >nul
if not exist %NDIdSource%\C120\lib\debug\Indy10\*.* md 
%NDIdSource%\C120\lib\debug\Indy10 >nul

REM * REM * - Debug Build  add /V  switch: D+ O- W+ M+ R+ Q+ I+ Y+ L+
REM ***************************************************
REM Compile Runtime Package IndySystem120
REM ***************************************************
if exist %NDIdSource%\lib\System\*.pas copy %NDIdSource%\lib\System\*.pas 
%NDIdSystem% >nul
if exist %NDIdSource%\lib\System\*.dpk copy %NDIdSource%\lib\System\*.dpk 
%NDIdSystem% >nul
if exist %NDIdSource%\lib\System\*.obj copy %NDIdSource%\lib\System\*.obj 
%NDIdSystem% >nul
if exist %NDIdSource%\lib\System\*.inc copy %NDIdSource%\lib\System\*.inc 
%NDIdSystem% >nul
if exist %NDIdSource%\lib\System\*.res copy %NDIdSource%\lib\System\*.res 
%NDIdSystem% >nul
if exist %NDIdSource%\lib\System\*.dcr copy %NDIdSource%\lib\System\*.dcr 
%NDIdSystem% >nul
if exist %NDIdSource%\lib\System\*.rsp copy %NDIdSource%\lib\System\*.rsp 
%NDIdSystem% >nul
CD %NDIdSystem%
%NDCBuilder%\bin\dcc32.exe IndySystem120.dpk /B /V /O%dNDIdLib% /DBCB /M /H 
/W /JPHN /JL /E%dNDIdLib% /LE%NDIdBpl% /LN%NDIdDcp% /N0%dNDIdDcu% 
/NH%NDIdHpp% /NO%dNDIdLib% /NB%dNDIdBpi% /-DRC -$d+O-n+p+r+s-t-w+y+m+q+i+l+ 
%2 %3 %4


REM ***************************************************
REM Compile Runtime Package IndyCore120
REM ***************************************************
if exist %NDIdSource%\lib\Core\*.pas copy %NDIdSource%\lib\Core\*.pas 
%NDIdCore% >nul
if exist %NDIdSource%\lib\Core\*.dpk copy %NDIdSource%\lib\Core\*.dpk 
%NDIdCore% >nul
if exist %NDIdSource%\lib\Core\*.obj copy %NDIdSource%\lib\Core\*.obj 
%NDIdCore% >nul
if exist %NDIdSource%\lib\Core\*.inc copy %NDIdSource%\lib\Core\*.inc 
%NDIdCore% >nul
if exist %NDIdSource%\lib\Core\*.res copy %NDIdSource%\lib\Core\*.res 
%NDIdCore% >nul
if exist %NDIdSource%\lib\Core\*.dcr copy %NDIdSource%\lib\Core\*.dcr 
%NDIdCore% >nul
if exist %NDIdSource%\lib\Core\*.rsp copy %NDIdSource%\lib\Core\*.rsp 
%NDIdCore% >nul
CD %NDIdCore%
%NDCBuilder%\bin\dcc32.exe IndyCore120.dpk /B /V /O%dNDIdLib% /DBCB /M /H /W 
/JPHN /JL /E%dNDIdLib% /LE%NDIdBpl% /LN%NDIdDcp% /N0%dNDIdDcu% /NH%NDIdHpp% 
/NO%dNDIdLib% /NB%dNDIdBpi% /-DRC -$d+O-n+p+r+s-t-w+y+m+q+i+l+ %2 %3 %4


REM ***************************************************
REM Compile Designtime Package dclIndyCore120
REM ***************************************************
%NDCBuilder%\bin\dcc32.exe dclIndyCore120.dpk /B /V /O%dNDIdLib% /DBCB /M /H 
/W /JPHN /JL /E%dNDIdLib% /LE%NDIdBpl% /LN%NDIdDcp% /N0%dNDIdDcu% 
/NH%NDIdHpp% /NO%dNDIdLib% /NB%dNDIdBpi% /-DRC -$d+O-n+p+r+s-t-w+y+m+q+i+l+ 
%2 %3 %4


REM ***************************************************
REM Compile Runtime Package IndyProtocols120
REM ***************************************************
if exist %NDIdSource%\lib\Protocols\*.pas copy 
%NDIdSource%\lib\Protocols\*.pas %NDIdProtocols% >nul
if exist %NDIdSource%\lib\Protocols\*.dpk copy 
%NDIdSource%\lib\Protocols\*.dpk %NDIdProtocols% >nul
if exist %NDIdSource%\lib\Protocols\*.obj copy 
%NDIdSource%\lib\Protocols\*.obj %NDIdProtocols% >nul
if exist %NDIdSource%\lib\Protocols\*.inc copy 
%NDIdSource%\lib\Protocols\*.inc %NDIdProtocols% >nul
if exist %NDIdSource%\lib\Protocols\*.res copy 
%NDIdSource%\lib\Protocols\*.res %NDIdProtocols% >nul
if exist %NDIdSource%\lib\Protocols\*.dcr copy 
%NDIdSource%\lib\Protocols\*.dcr %NDIdProtocols% >nul
if exist %NDIdSource%\lib\Protocols\*.rsp copy 
%NDIdSource%\lib\Protocols\*.rsp %NDIdProtocols% >nul
CD %NDIdProtocols%
%NDCBuilder%\bin\dcc32.exe IndyProtocols120.dpk /B /O%dNDIdLib% /DBCB /M /H 
/W /JPHN /JL /E%dNDIdLib% /LE%NDIdBpl% /LN%NDIdDcp% /N0%dNDIdDcu% 
/NH%NDIdHpp% /NO%dNDIdLib% /NB%dNDIdBpi% /-DRC -$d+O-n+p+r+s-t-w+y+m+q+i+l+ 
%2 %3 %4


REM ***************************************************
REM Compile Designtime Package dclIndyProtocols120
REM ***************************************************
%NDCBuilder%\bin\dcc32.exe dclIndyProtocols120.dpk /B /V /O%dNDIdLib% /DBCB 
/M /H /W /JPHN /JL /E%dNDIdLib% /LE%NDIdBpl% /LN%NDIdDcp% /N0%dNDIdDcu% 
/NH%NDIdHpp% /NO%dNDIdLib% /NB%dNDIdBpi% /-DRC -$d+O-n+p+r+s-t-w+y+m+q+i+l+ 
%2 %3 %4
REM * REM * - Debug Build End



REM * REM * - Release Build
REM ***************************************************
REM Compile Runtime Package IndySystem120
REM ***************************************************
if exist %NDIdSource%\lib\System\*.pas copy %NDIdSource%\lib\System\*.pas 
%NDIdSystem% >nul
if exist %NDIdSource%\lib\System\*.dpk copy %NDIdSource%\lib\System\*.dpk 
%NDIdSystem% >nul
if exist %NDIdSource%\lib\System\*.obj copy %NDIdSource%\lib\System\*.obj 
%NDIdSystem% >nul
if exist %NDIdSource%\lib\System\*.inc copy %NDIdSource%\lib\System\*.inc 
%NDIdSystem% >nul
if exist %NDIdSource%\lib\System\*.res copy %NDIdSource%\lib\System\*.res 
%NDIdSystem% >nul
if exist %NDIdSource%\lib\System\*.dcr copy %NDIdSource%\lib\System\*.dcr 
%NDIdSystem% >nul
if exist %NDIdSource%\lib\System\*.rsp copy %NDIdSource%\lib\System\*.rsp 
%NDIdSystem% >nul
CD %NDIdSystem%
%NDCBuilder%\bin\dcc32.exe IndySystem120.dpk /B /O%NDIdLib% /DBCB /M /H /W 
/JPHN /JL /E%NDIdLib% /LE%NDIdBpl% /LN%NDIdDcp% /N0%NDIdDcu% /NH%NDIdHpp% 
/NO%NDIdLib% /NB%NDIdBpi% /-DRC -$d-l-n+p+r-s-t-w-y- %2 %3 %4


REM ***************************************************
REM Compile Runtime Package IndyCore120
REM ***************************************************
if exist %NDIdSource%\lib\Core\*.pas copy %NDIdSource%\lib\Core\*.pas 
%NDIdCore% >nul
if exist %NDIdSource%\lib\Core\*.dpk copy %NDIdSource%\lib\Core\*.dpk 
%NDIdCore% >nul
if exist %NDIdSource%\lib\Core\*.obj copy %NDIdSource%\lib\Core\*.obj 
%NDIdCore% >nul
if exist %NDIdSource%\lib\Core\*.inc copy %NDIdSource%\lib\Core\*.inc 
%NDIdCore% >nul
if exist %NDIdSource%\lib\Core\*.res copy %NDIdSource%\lib\Core\*.res 
%NDIdCore% >nul
if exist %NDIdSource%\lib\Core\*.dcr copy %NDIdSource%\lib\Core\*.dcr 
%NDIdCore% >nul
if exist %NDIdSource%\lib\Core\*.rsp copy %NDIdSource%\lib\Core\*.rsp 
%NDIdCore% >nul
CD %NDIdCore%
%NDCBuilder%\bin\dcc32.exe IndyCore120.dpk /B /O%NDIdLib% /DBCB /M /H /W 
/JPHN /JL /E%NDIdLib% /LE%NDIdBpl% /LN%NDIdDcp% /N0%NDIdDcu% /NH%NDIdHpp% 
/NO%NDIdLib% /NB%NDIdBpi% /-DRC -$d-l-n+p+r-s-t-w-y- %2 %3 %4


REM ***************************************************
REM Compile Designtime Package dclIndyCore120
REM ***************************************************
%NDCBuilder%\bin\dcc32.exe dclIndyCore120.dpk /B /O%NDIdLib% /DBCB /M /H /W 
/JPHN /JL /E%NDIdLib% /LE%NDIdBpl% /LN%NDIdDcp% /N0%NDIdDcu% /NH%NDIdHpp% 
/NO%NDIdLib% /NB%NDIdBpi% /-DRC -$d-l-n+p+r-s-t-w-y- %2 %3 %4


REM ***************************************************
REM Compile Runtime Package IndyProtocols120
REM ***************************************************
if exist %NDIdSource%\lib\Protocols\*.pas copy 
%NDIdSource%\lib\Protocols\*.pas %NDIdProtocols% >nul
if exist %NDIdSource%\lib\Protocols\*.dpk copy 
%NDIdSource%\lib\Protocols\*.dpk %NDIdProtocols% >nul
if exist %NDIdSource%\lib\Protocols\*.obj copy 
%NDIdSource%\lib\Protocols\*.obj %NDIdProtocols% >nul
if exist %NDIdSource%\lib\Protocols\*.inc copy 
%NDIdSource%\lib\Protocols\*.inc %NDIdProtocols% >nul
if exist %NDIdSource%\lib\Protocols\*.res copy 
%NDIdSource%\lib\Protocols\*.res %NDIdProtocols% >nul
if exist %NDIdSource%\lib\Protocols\*.dcr copy 
%NDIdSource%\lib\Protocols\*.dcr %NDIdProtocols% >nul
if exist %NDIdSource%\lib\Protocols\*.rsp copy 
%NDIdSource%\lib\Protocols\*.rsp %NDIdProtocols% >nul
CD %NDIdProtocols%
%NDCBuilder%\bin\dcc32.exe IndyProtocols120.dpk /B /O%NDIdLib% /DBCB /M /H 
/W /JPHN /JL /E%NDIdLib% /LE%NDIdBpl% /LN%NDIdDcp% /N0%NDIdDcu% /NH%NDIdHpp% 
/NO%NDIdLib% /NB%NDIdBpi% /-DRC -$d-l-n+p+r-s-t-w-y- %2 %3 %4

REM ***************************************************
REM Compile Designtime Package dclIndyProtocols120
REM ***************************************************
%NDCBuilder%\bin\dcc32.exe dclIndyProtocols120.dpk /B /O%NDIdLib% /DBCB /M 
/H /W /JPHN /JL /E%NDIdLib% /LE%NDIdBpl% /LN%NDIdDcp% /N0%NDIdDcu% 
/NH%NDIdHpp% /NO%NDIdLib% /NB%NDIdBpi% /-DRC -$d-l-n+p+r-s-t-w-y- %2 %3 %4

REM * REM * - Release Build End

REM ***************************************************
REM Delete third-party .obj files
REM before compiling the .lib file
REM ***************************************************
del adler32.obj > nul
del compress.obj > nul
del crc32.obj > nul
del deflate.obj > nul
del example.obj > nul
del gzio.obj > nul
del infback.obj > nul
del inffast.obj > nul
del inflate.obj > nul
del inftrees.obj > nul
del minigzip.obj > nul
del trees.obj > nul
del uncompr.obj > nul
del zutil.obj > nul

goto EndExit

:enderror
call ..\Lib\clean.bat
cd ..\Lib
goto EndExit

:enderrmsg
echo Error!
goto EndExit

:endok
:EndExit
Echo End Batch File
@Pause

______________________________________________ 

When I try to build it with the fullc120.bat file I always get the error
message that it haven't found the files "indysystem120.res"
"dclindycore.res" and so on. In other words it doesn't find the
indy*.res files. I did a search in all those indy directories and I too
cannot find them. How did it work in your batch-file?

Ups - forgot about that
I simply copied the *100.res files to *120.res

Roland

"riweber" <weberedv@atnet.at> wrote in message 
news:4781f6b2$1@newsgroups.borland.com...
> When I try to build it with the fullc120.bat file I always get the error
> message that it haven't found the files "indysystem120.res"
> "dclindycore.res" and so on. In other words it doesn't find the
> indy*.res files. I did a search in all those indy directories and I too
> cannot find them. How did it work in your batch-file? 

The evil that is line wrapping.

.T

Joe Pasquariello wrote:
> 
> It sounds like you've made a lot of progress. Would you be willing to share
> what you learned so that we can try to develop a procedure that others can
> use and avoid some of the learning curve?
> 

I have taken the two batch files that Roland posted and modified them 
slightly. I have posted a zip file that contains his original batch 
files, my modified batch files (the ones with the *V2.bat names), and 
some instructional text files in the attachments group with the subject 
"Updating RAD Studio to the newer Indy 10".

My modifications retain the existing Indy Help files (they are better 
than no help at all), and reduce the number of unnecessary files copied 
into the source directories. They also build the missing *.res files 
from the *.rc files include in the SVN checkout.

I downloaded the latest Indy 10 source from the SVN server using 
TortoiseSVN.

Hopefully the new batch files and instructions help others to update to 
the newer version of Indy 10.

Dennis Cote