Moving DCLUSR package from BCB6 to BDS2006

Alberto

CBuilder Developer

Moving DCLUSR package from BCB6 to BDS2006

2006-05-24 10:39:12 PM
cppbuilder22
Is there a way to easily move the dclusr60.bpl package from BCB6 to
BDS2006 ?
Or should I have to recompile all the ad-hoc components that I have there ?
Thanks
Alberto

Remy Lebeau (TeamB)

CBuilder Developer

2006-05-25 01:45:43 AM

Re:Moving DCLUSR package from BCB6 to BDS2006

"Alberto" < XXXX@XXXXX.COM >wrote in message

Quote

Is there a way to easily move the dclusr60.bpl package from
BCB6 to BDS2006 ? Or should I have to recompile all the
ad-hoc components that I have there ?
Packages are version-specific. You cannot use an older binary in a newer

IDE. You have to recompile it.
Gambit

Alberto

CBuilder Developer

2006-05-25 04:28:57 AM

Re:Moving DCLUSR package from BCB6 to BDS2006

Remy Lebeau (TeamB) wrote:

Quote

>Is there a way to easily move the dclusr60.bpl package from
>BCB6 to BDS2006 ? Or should I have to recompile all the
>ad-hoc components that I have there ?
>

Packages are version-specific. You cannot use an older binary in a newer
IDE. You have to recompile it.

Thanks, that's what I suspected. I created a new .bdsprj with all the

components of the old dclusr package (16 different components, some C++,
some Pascal). The package compiles and links without errors, and I find
my widgets in the components palette. The problems start when I try to
use some of those components with a very simple, test application that
compiles and links correctly under BCB6. With BDS the linker complains
saying that "Fatal: Unable to open file 'EXTCTRLS.OBJ'"
Any clues on the missing porting step? Thanks
Alberto

{smallsort}

David Dean

CBuilder Developer

2006-05-25 04:42:28 AM

Re:Moving DCLUSR package from BCB6 to BDS2006

In article <4474c207$ XXXX@XXXXX.COM >,
Alberto < XXXX@XXXXX.COM >wrote:

Quote

I created a new .bdsprj with all the
components of the old dclusr package (16 different components, some C++,
some Pascal). The package compiles and links without errors, and I find
my widgets in the components palette. The problems start when I try to
use some of those components with a very simple, test application that
compiles and links correctly under BCB6. With BDS the linker complains
saying that "Fatal: Unable to open file 'EXTCTRLS.OBJ'"
Any clues on the missing porting step? Thanks
Building Pascal components in the C++ personality is bad news. Remove

them, then make a Delphi Package for them, and set the compiler options
to "Generate all C++ files" and then install them.
Much of the time when the linker asks for *.obj it is because of a
#pragma link line in the source code. Delete it, and make sure your
linker path includes all the directories where the *.lib files are for
the component you are trying to use.
--
-David
Quis custodiet custodes ipsos?

Alberto

CBuilder Developer

2006-05-25 04:46:59 AM

Re:Moving DCLUSR package from BCB6 to BDS2006

David Dean wrote:

Quote

Building Pascal components in the C++ personality is bad news. Remove
them, then make a Delphi Package for them, and set the compiler options
to "Generate all C++ files" and then install them.
Much of the time when the linker asks for *.obj it is because of a
#pragma link line in the source code. Delete it, and make sure your
linker path includes all the directories where the *.lib files are for
the component you are trying to use.

Thanks for the answer. But when I compile the C++ and Pascal components,

all is ok, the package is built and installed without errors.
Only when I try to use it in an application that unresolved comes out...
or have I misunderstood what you said ?
Alberto

David Dean

CBuilder Developer

2006-05-25 04:55:23 AM

Re:Moving DCLUSR package from BCB6 to BDS2006

In article <4474c641$ XXXX@XXXXX.COM >,
Alberto < XXXX@XXXXX.COM >wrote:

Quote

Thanks for the answer. But when I compile the C++ and Pascal components,
all is ok, the package is built and installed without errors.
Only when I try to use it in an application that unresolved comes out...
or have I misunderstood what you said ?
Yes, you have misunderstood. The problems don't appear until you try

and use the components, but the cause seems to be on how they were
built. It is probably a bug, but I haven't been able to create a simple
test case to demonstrate it. (Probably because my pascal is too rusty)
--
-David
Quis custodiet custodes ipsos?

Alberto

CBuilder Developer

2006-05-25 05:32:46 AM

Re:Moving DCLUSR package from BCB6 to BDS2006

David Dean wrote:

Quote

Yes, you have misunderstood. The problems don't appear until you try
and use the components, but the cause seems to be on how they were
built. It is probably a bug, but I haven't been able to create a simple
test case to demonstrate it. (Probably because my pascal is too rusty)

Problem solved. I knew already that projects *must not* be converted

when changing compiler version, but they must be recreated.
But I fell in that trap again. Letting BDS creating a project from
scratch solved everything. Thanks.
Alberto