You
don't need to use the default runtime packages. Ie Build as a single EXE but
make sure there are no references to any of your custom package units etc in the
.EXE
Then
you can use the LoadPackage() (Can't remember the exact name) to dynamically
load your extra runtime packages as required.
In
your case the "Build with runtime packages" is a misnomer.
You
can if you want to rebuild the VCL packages into any set of packages you
require. E.g We have totally re-packaged the VCL, and have about 60% of the base
VCL into a single package - used by all our apps.
Myles.
-----Original Message-----
From: Jeremy Coulter [mailto:[EMAIL PROTECTED]
Sent: Monday, 2 June 2003 5:03 p.m.
To: Multiple recipients of list delphi
Subject: [DUG]: Modulizing Apps. with PackagesHi all. Yeah I know, its sad to be having a day off, but still thinking about work :-)Anyway, I have finally got a project where I will or want to use packages to modulize the app.I have already developed the first part based on an article in the Delphi Informant Mag.The only thing I am kinda confused about is, to get the app. that looks for and loads the packages at runtime, I have to set the "Compile with Runtime Support", or whatever its called, switch in the project settings.This means that I need to now supply the 6mb VCL packages and what ever else I use, like ADO, etc.This is not going to be any good for this project as it has to go to over 100 places.SO, can I do the above slightly differently so I can just distribute the EXE without have to also send out the runtime BPL's too?Or am I better to use some 3rd party plugin tool?Cheers,Jeremy Coulter------------------------------------------------------------------------All email scanned with Nortons Antivurus 2002------------------------------------------------------------------------
