🚀 go-pugleaf

VCLE40.LIB is a BCB4 library.  It is an artifact of trying to translate the 
old project into the new one.

Make a list of the items in the project.  Create a new project and add those 
items to it.

.  Ed

> SAM wrote in message
> news:4301e9e2$1@newsgroups.borland.com...
>
> I have an old project written in with BCB4.0 Professional.
> I will port it to BCB6, but I get always the Linker fatal error:
> VCLE40.lib not found.
>
> How can I avoid this error.
> Where is the VCLE40 setting?
> Is it in the project setting. I scanned the *.bpr file, but
> nothing found!
> Is it a wrong linker option?
>
> Thanks for any help.

Thanks Ed for the tip.
Now it works fine, but there are now some strange
Linker warnings after build project.

here is one example:
...
[Linker Warning] Public symbol '_DATEN' defined in both module
  D:\...\unit6.obj and in D:\...\unit4.obj
...

but DATEN is a global variable defined in
unit1.cpp only - e.g. unsigned short DATEN;

Thanks for any help.

-Sam

"Ed Mulroy" <dont_email_me@bitbuc.ket> wrote:
>VCLE40.LIB is a BCB4 library.  It is an artifact of trying to translate the 
>old project into the new one.
>
>Make a list of the items in the project.  Create a new project and add those 
>items to it.
>
>.  Ed
>
>> SAM wrote in message
>> news:4301e9e2$1@newsgroups.borland.com...
>>
>> I have an old project written in with BCB4.0 Professional.
>> I will port it to BCB6, but I get always the Linker fatal error:
>> VCLE40.lib not found.
>>
>> How can I avoid this error.
>> Where is the VCLE40 setting?
>> Is it in the project setting. I scanned the *.bpr file, but
>> nothing found!
>> Is it a wrong linker option?
>>
>> Thanks for any help.
>
>

> [Linker Warning] Public symbol '_DATEN' defined in both module
>  D:\...\unit6.obj and in D:\...\unit4.obj
>
> but DATEN is a global variable defined in
> unit1.cpp only - e.g. unsigned short DATEN;

The error suggests that DATEN is declared in a header file.  The leading 
underscore is a consequence of how public names are formed for variables in 
C and C++.

The preprocessor merges included files into the source and presents the 
merged result to the compiler.  When the linker phase begins it sees a 
same-name symbol from each object file which included the header file.

The solution is not difficult or exotic - it's been the same since the days 
of K&R C.  Declare the variable with the keyword extern in the header file 
and then put the real declaration in one and only one source file.

.  Ed

> Sam wrote in message
> news:4304e616$1@newsgroups.borland.com...
>
> Thanks Ed for the tip.
> Now it works fine, but there are now some strange
> Linker warnings after build project.
>
> here is one example:
> ...
> [Linker Warning] Public symbol '_DATEN' defined in both module
>  D:\...\unit6.obj and in D:\...\unit4.obj
> ...
>
> but DATEN is a global variable defined in
> unit1.cpp only - e.g. unsigned short DATEN;