Thread View: borland.public.cppbuilder.deployment
4 messages
4 total messages
Started by SVC
Wed, 08 Dec 2004 18:14
Unable to open file 'VCLE50.LIB'
Author: SVC
Date: Wed, 08 Dec 2004 18:14
Date: Wed, 08 Dec 2004 18:14
13 lines
1092 bytes
1092 bytes
Greetings, I just updated my C++builder 5 with builder 6.0. When I try to compile my existing projects, I keep on getting the error: [Linker Fatal Error] Fatal: Unable to open file 'VCLE50.LIB' Any hints? Thanks, S.
Re: Unable to open file 'VCLE50.LIB'
Author: Ed Mulroy [TeamB]
Date: Wed, 08 Dec 2004 20:05
Date: Wed, 08 Dec 2004 20:05
20 lines
1543 bytes
1543 bytes
I think that happens when you upgrade a project from one compiler version to the next. Try this: With the IDE not running, open the project file, the *.bpr file, in an editor and remove the 50 from all occurances of the name. . Ed > SVC wrote in > message news:41b74470$1@newsgroups.borland.com... > > Greetings, > > I just updated my C++builder 5 with builder 6.0. When I try to > compile my existing projects, I keep on getting the error: > > [Linker Fatal Error] Fatal: Unable to open file 'VCLE50.LIB' > > Any hints?
Re: Unable to open file 'VCLE50.LIB'
Author: SVC
Date: Wed, 08 Dec 2004 20:56
Date: Wed, 08 Dec 2004 20:56
17 lines
1364 bytes
1364 bytes
"Ed Mulroy [TeamB]" <dont_email_me@bitbuc.ket> wrote: >I think that happens when you upgrade a project from one >compiler version to the next. > >Try this: >With the IDE not running, open the project file, the *.bpr file, in >an editor and remove the 50 from all occurances of the name. > >. Ed > I check the bpr file and there is no *50.lib entries. I don't know where the compiler is getting this instruction to include the VCLE50.LIB since it is NOT in the bpr file. S.
Re: Unable to open file 'VCLE50.LIB'
Author: Ed Mulroy [TeamB]
Date: Thu, 09 Dec 2004 01:14
Date: Thu, 09 Dec 2004 01:14
25 lines
1779 bytes
1779 bytes
That implies the library is specified somewhere else. Unlikely, but easy and quick to check is in the source code and heade files. Check if there is a USELIB macro or a #pragma link specifying it. More likely is that a library which uses the VCL but which was built with version 5 calls for VCLE50.LIB And least likely is the DFM file because I've no idea why it should be in there, but humor me and run this command while at the project directory grep -id "vcle50" *.dfm . Ed > SVC wrote in message > news:41b76a6d$1@newsgroups.borland.com... > > I check the bpr file and there is no *50.lib entries. > > I don't know where the compiler is getting this > instruction to include the VCLE50.LIB since it is > NOT in the bpr file.
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads