🚀 go-pugleaf

Thanks for your solution.  It worked great for the BPLs and Borland DLLs, 
but my deployment executable still seems to be dependent on 3rd party DLLs. 
Any suggestions on how to remove these dependencies from the deployment 
executable?  Thanks.

V/r,

Jorly


"Vladimir Stefanovic" <spam@not.needed> wrote in message 
news:4194e705@newsgroups.borland.com...
> Try with:
>
> Project / Options / Packages / [ uncheck] Build with runtime pacgages
> Project / Options / Linker / [ uncheck] Use dynamic RTL
>
> --
>
>
> Best regards,
> Vladimir Stefanovic
>
> Jorly Metzger <jmetzger@progeny.net> wrote in message
> news:4194dab0$1@newsgroups.borland.com...
>> My client wants a single executable for my application.  However,
> since
>> their workstations do not have Borland C++ Builder installed, I have
> to
>> include third party *.bpl files used in my project (nat_inst.bpl,
> rapid.bpl,
>> etc) and standard *.dll files (borlndmm.dll, cc3260mt.dll, etc) with
> my
>> delivery.
>>
>> Does anybody know if it is possible to build your single executable
> to
>> incorporate these DLLs and BPLs so that the external files are not
> necessary
>> with your deployment?
>>
>> Thanks.
>>
>> Jorly
>>
>>
>
>