🚀 go-pugleaf

Alisdair,

Funny how this work. I actually thought I had done all the steps you 
outlined before except I would always have added to my project  the rtl.lib 
and vcl.lib. When I run this I get a FATAL LINK TERMINATION and the <F1> 
help on this says call Borland Tech support.
Then I noticed you said build the project and add the libraries as needed 
for unresolved references, so I decided to take the vcl.lib and rtl.lib out 
see what unresolved references I got. Lo and behold built with link error 
and runs as a stand alone app. Thanks a lot. Now I'll see if this works on a 
console app without VCL also.

-- 
William Riley
William_R1@verifone.com
(916) 630-4040
3755 Atherton Rd
Rocklin, CA 95765

"AlisdairM" <alisdair.meredith@uk.renaultf1.com> wrote in message 
news:44215aac@newsgroups.borland.com...
> William Riley wrote:
>
>> I am new to Windows and Borland C++ (using the Personal Edition) hope
>> this is a good place to ask this question.  I would like to
>> distribute an app file that the user can put on his system and run
>> without having to install any of the Borland *.bpl or DLLs (stand
>> alone app). From the C++ Builder help files it would seem that this
>> is possible. Basically all I can find is that you can add to your
>> project the corresponding *.lib files and build the project. But this
>> does not seem to work. I am not quite sure what the "Build with
>> runtime packages" means on the Project|Options|Packages page, but if
>> I uncheck it I get a rather rude Fatal Linker Termination error.  So
>> currently the app that I want to distribute always says it needs the
>> vcl60.bpl and rtl60.bpl and it runs fine when installed on the target
>> system. Note unchecking "Use dynamic RTL" gets rid of the need to
>> supply BORLNDMM.DLL with the app.  Now what are the corresponding
>> *.lib for vcl60.bpl and rtl60.bpl? Looking in the lib directory where
>> the help says to look I find vcl.lib and rtl.lib under the Release
>> and Debug folders. From other statements in the help files I assume
>> that this covers vcl60.bpl and rtl60.bpl but adding these *.lib's
>> (either from the Release or Debug folders) to my project and building
>> does not change the need to deploy vcl60.bpl and rtl60.bpl on the
>> target system.  I think I must be missing something since I cannot
>> figure out how to produce a stand alone console app. Adding the
>> obvious *.lib file to the project makes no difference either.  Any
>> help or suggestions appreciated.
>
> There are two project options you need to set to finish this <g>
>
> On the Project | Options | Linker page you must UNcheck the box 'use
> dynamic RTL'
>
> On the Packages page, you must also uncheck the box for "build with
> runtime packages"
>
> After this you may get some linker errors about missing symbols.  If
> so, you need to add the libraries where these can be found.
>
> These options should only be necessary for the final .EXE project,
> although we apply them to all our library projects as well, just to be
> consistent/safe.
>
> -- 
> AlisdairM(TeamB)