Re: VCLE35.lib file error when compiling CPPB3 file in CPPB5

Article View: borland.public.cppbuilder.upgrade

Article #2326

Back to borland.public.cppbuilder.upgrade Previous Next

#2326

From: Craig Farrell
Date: Mon, 06 Mar 2000 00:00

13 lines
1032 bytes

Hi David,

If you've already deleted all the likely intermediate
files (like *.CSM, *.#?? *.IL? *.OBJ *.TDS), then consider
more obscure ways that a BCB3 binary is being brought
into that project. For example, maybe there is a 
#pragma link "something" 
...where something.obj is being found in it's BCB3-compiled
state? Maybe the project re-uses BCB3-built packages
or components and some .BPI or .LIB files for the
old package are being found?

--Craig

Technical Details

Message-ID: <38C4164E.320EAA9C@insprise.com>

Path: arc1-ca.pugleaf.net!unknown!not-for-mail

References: <38c32a9e@dnews>

Show Full Headers

Complete Article Headers

X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 10529a,4e9533c476983cae
X-Google-Attributes: gid10529a,public
From: Craig Farrell <cNO_SPAM.please.farrell@insprise.com>
Subject: Re: VCLE35.lib file error when compiling CPPB3 file in CPPB5
Date: 2000/03/06
Message-ID: <38C4164E.320EAA9C@insprise.com>
X-Deja-AN: 593954595
Content-Transfer-Encoding: 7bit
References: <38c32a9e@dnews>
Content-Type: text/plain; charset=us-ascii
X-Trace: 6 Mar 2000 12:33:09 -0800, 10.143.13.127
MIME-Version: 1.0
Newsgroups: borland.public.cppbuilder.upgrade

Reply to Parent Message