🚀 go-pugleaf

"Stefan Hoffmeister (TeamB)" wrote:
> 
> : Mark Borgerson <mark@oes.to> wrote:
> 
> >4.0 using CPPBuilder standard edition??
> >I'm talking about the Linker Error:
> > File not found:  VCLDB40.lib,   etc.
> 
> You do not have any database files in the "learning edition" of C++Builder
> 4.0.

I didn't have any database files in my standard version 1.0 either!! So why
does the updater insist on putting them in the .mak file???  My code doesn't
use them, or I wouldn't get executable code when I remove them from the .mak
file.
> 
> >I have also considered copying over the libraries from a trial version
> >of the enterprise edition that I got in the mail.  Since I never
> >use the libraries, this shouldn't do anything except let me convert
> >the projects without silly linker errors.
> 
> If I was you, I wouldn't do it. One never knows which trial code is
> present in the code that is linked in...

But I'm not using any of the code from the trial libraries!!!  I'm just
putting them in the .lib directory so that the linker can open them,
decide that no code in them is being called, then close them again!  
That should be ok as long as none of the code in the database 
libraries is called, shouldn't it??   I think I'll try this and then
check to see if I get the same executable that I get by editing the
.mak file.

If I knew how to make up a dummy, empty library, I'd probably use that,
just to make sure that there were no side effects.

I think it really boils down to an annoying bug in the updater---whoever
wrote it didn't consider that there might be users who stick with the
standard edition because we don't need another 100MB of stuff on our
hard disks for database and internet stuff we don't use.  (Plus
another couple hundred bucks in tool costs!)

Mark Borgerson