[DUG] Runtime packages

Myles Penlington myles at ams.co.nz
Tue Feb 26 10:20:26 NZDT 2008


Applications and packages all have to be linked/compiled with the same
set of packages, else you get the duplicate/already exist messages.

We use our own set of packages instead - i.e. we have 2 package sets - a
designtime set and a runtime set (which are very different - the design
time set uses the standard vcl/bpl packages, the runtime set uses our
own set of runtime packages).

Myles.

-----Original Message-----
From: delphi-bounces at listserver.123.net.nz
[mailto:delphi-bounces at listserver.123.net.nz] On Behalf Of Robert martin
Sent: Tuesday, 26 February 2008 10:11 a.m.
To: NZ Borland Developers Group - Delphi List
Subject: [DUG] Runtime packages

Hi

Trying to convert a dll into a runtime package.  Have changed the host 
app to use reuntime packages but left most packages (except vcl;rtl) as 
statically linked.  I have another package that is to be loaded 
dynamically.  However when I try to load it I get a message '... 
WildSoftD2007.bpl was not found...'.  This is a package containing all 
our custom components and both apps use these components. 

I thought my run time package would statically include this.  Any ideas 
what I am doing wrong ?

If I copy the bpl into the exe directory I miss this message and get a 
'class TQuikRep' already exists in package, error message.  I am hoping 
that fixing my first problem will then fix the second.  Yes we have a 
component that uses quickReports as a base class.

-- 
Rob Martin
Software Engineer

phone +64 03 377 0495
fax   +64 03 377 0496
web www.chreos.com

Wild Software Ltd

_______________________________________________
NZ Borland Developers Group - Delphi mailing list
Post: delphi at listserver.123.net.nz
Admin: http://delphi.org.nz/mailman/listinfo/delphi
Unsubscribe: send an email to delphi-request at listserver.123.net.nz with
Subject: unsubscribe

Attention:
This communication is confidential and may be legally privileged.  If you are not the intended recipient, please do not use, disclose, copy or distribute it, other than to return it to us with your confirmation that it has been deleted from your system.



More information about the Delphi mailing list