C++Builder 2007:

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

dclIndyCore50.dpk
dclIndyCore60.dpk
dclIndyCore70.dpk
dclIndyCore90.dpk
dclIndyCore90Net.dpk
dclIndyCore100.dpk
dclIndyCore100Net.dpk
dclIndyCore110.dpk
dclIndyCore110Net.dpk
dclIndyCore120.dpk
dclIndyCore120Net.dpk

thanks,

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

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

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)"  wrote in message 
news:47674582$1@newsgroups.borland.com...
>
> "roladdon"  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 

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

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

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)"  wrote in message 
news:4766eb53$1@newsgroups.borland.com...
>
> "Joe Pasquariello"  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)"  wrote in message 
news:4766ce43@newsgroups.borland.com...
>
> "roladdon"  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
>