Board index » cppbuilder » How to proper Build for 'Deployment' in BDS..

2006-08-30 08:54:45 PM
cppbuilder107
What I know and what I do:
-----------------------------
- Set the standard Build Configuration 'Release Build' to 'Active'.
- Uncheck 'Use dynamic RTL'.
- Uncheck 'Build with runtime packages'.
But do I now Build the Project with unwanted LIB's/Runtime packages and
DLL's?
How should I approach this?
Also,
If I examine the .exe I see:
---------------------------
- Not-used mouse-pointers
for example and SQL-hourglass (which I didn't use or have tried in the
project)
(I know they are 'part of' the default pointers, but other unused default
pointers are NOT in the .exe)
- Not-used Bitmaps (which I didn't use or have tried in the project)
BBABORT
BBALL
BBCANCEL
BBCLOSE
BBHELP
BBIGNORE
BBNO
BBOK
BBRETRY
BBYES
PREVIEWGLYPH
- A TLoginDialog (which I didn't use or have tried in the project)
Jasper
 

What you're choosing to do is build with statically linked libraries
thus including the normal RTL libs in your exe. This may mean that you
have a whole bunch of functionality that you do not require or use
built into your appliaction (though by the sounds of it you probably do
use a few of the items you've mentioned below even if you don't know
it) but you don't need the libraries on the final client so the install
is often as simple as copying the executable.
Hope that helps
Regards
Daniel
JasperP wrote:

JasperP wrote:
been this way (with C++ Builder at least). It has always seemed wasteful
to me but it is a benign waste :-) My guess is that it could be fixed
but since there are so many other, more important things to fix that
these annoyances have been left alone.
The worst of these, to me at least, is the including of unused libraries
and packages in the project file. When I pass a working project to a
colleague who doesn't happen to have one of the libraries referenced in
the project file, he can't build it until I go in and edit the project
file removing unnecessary libraries and packages.
Sorry for the non-answer.
Regards,
Jim Dodd
Onset Computer Corp.
 

{smallsort}

In article <44f6fbf0$ XXXX@XXXXX.COM >,
Jim Dodd < XXXX@XXXXX.COM >wrote:
for most of these where you can say "Remove this from project"
--
-David
Quis custodiet custodes ipsos?
 

"David Dean" < XXXX@XXXXX.COM >wrote in message
want to remove idectrls.lib, which doesn't actually exist on any of our
systems, and the "phantom" idectrls.lib entry does not exist anywhere in any
bdsproj file. You tell it to remove the reference and you get a linker error
for the exact file you told it to remove. I'm afraid it's not one of the
great things IMHO, but it would be if it worked every time :)
D.Mills
 

In article < XXXX@XXXXX.COM >,
"D. Mills" < XXXX@XXXXX.COM >wrote:
saves a lot of hassle. If you have good test cases where it fails,
please submit them to QC.
--
-David
Quis custodiet custodes ipsos?
 

Jim Dodd wrote:
this.
Looks like the including of unused libraries and packages can only be
avoided if you do a check-per-item and that would be a bit of a waste of
time each time.
Jasper
 

"David Dean" < XXXX@XXXXX.COM >wrote in message
I would if I had any way of reproducing it, other than several projects we
have always eventually generate the errors, with no apparent rhyme or
reason, so until then I won't put it into QC. Deleting the .dsk file seems
to fix it at least temporarily anyway, so perhaps they are getting
corrupted, I'll try turning off all the autosave desktop stuff and see if it
goes away.
D.Mills