yang686526

size of activex control..!!

size of activex control..!!
sir,
i've developed an mfc activex control for displaying the dwg and dxf files using the dwgdirect 1.11 library. i used vc++ 6.0. but the size of the component seems to be aroung 8.59 mb. and not even that, i've gone through the samle sdi application for viewing the files, which have been provided by open desing alliance, and its size too seems to be the same (8.59 mb). the compiler option is set as shared linking. so i just want to know is there any way to reduce the size of the component.
i've also gone through the opendwg toolkit/viewkit library. and also developed a sample win32 application for viewing that. but its size is much less, when compaired to the one, which is build using the new dwgdirect 1.11 library. i also noticed that they are not providing any support to the old one i.e open dwg toolkit/viewkit.
i've also noticed that the new library require two dll files, which i've been listed below, for running the application in a machine.
1. mfc042d.dll
2. msvcp60d.dll
if i make a package of all these, the size comes aroung 10mb.
so i need to know is there any way to reduce the size of the control.
and how can we avoid these dependencies (the above 2 dll's) .
rajesh parameswaran

rajuinnet
# 7th july 2004, 02:03 am

registered user join date: jan 2002
posts: 88
size of your activex
hi,
you have a sample odamfcappdll which use dll.
i have created an activex which use dwgdirect dll, and the size is now 2 mb.
thanks,
laurent

lg
# 7th july 2004, 11:27 am

moderator join date: mar 2002
posts: 2,994
i think 2m is the size of application itself without dd dlls.
an application statically linked with dwgdirect may be of less size than all dd dlls. for example odreadex and odwriteex samples statically linked with dd have the size of 4.5m and odamfcapp using much more functionality is of 6.5m size.
the size can be reduced by turning off acis support (surely 3dsolids would not be rendered in this case and acis objects loaded from file would not be converted between dwg 2004 and minor dwg and dxf).
we are also going to provide more flexibility to avoid linking with unnecessary functionality in future.
btw, rajesh, are you sure mfc042d.dll and msvcp60d.dll are the correct names? they seem to be debug dlls.
sergey slezkin

sslezkin
# 7th july 2004, 10:01 pm

registered user join date: jul 2004
location: india
posts: 82

size of control reduced to 1/2
hi mr.laurent & mr.sergey slezkin
i would like to thank u all for the positive reply. i solved the problem by reducing the size of the ocx to one half. the earlier one was debug build and when i tried release version the size seems to be one half of the earlier one. now its size is 4.02 mb.
thank u very much
regards,
rajesh parameswaran

rajuinnet
# 15th july 2004, 10:06 pm

registered user join date: jul 2004
location: india
posts: 82

size issue solved without using release build.
hi all,
i found that without using the release build, we can reduce the size of the application. all u have to do is:
on the link tab, in the project options field, type in "/opt:ref". this tells the linker to continue optimizing away unreferenced code. this is the default when debug information is turned off, but it defaults to off when you tell the linker to generate debug information. failing to specify this will cause your executables and dlls to get 10-20% larger. you should also specify /ignore:4089 to tell the linker to not generate warnings if it optimizes away all references to a dll (this tip works with vc++ .net also).
u can get more details from the following link..
---------------------------------------
regards,
rajesh parameswaran.

rajuinnet

none
? | ?
thread tools



display modes
linear mode


search this thread

rate this thread
excellent
good
average
bad
terrible

posting rules
you may post new threads
you may post replies
you may post attachments
you may edit your posts
is on
are on
code is off
html code is off
forum jump
user control panel private messages subscriptions who's online search forums forums home general topics news questions and remarks business issues industry commentary general software issues documentation issues future directions dwg libraries dwgdirect.net dwgdirect, c++ version dwgdirectx, activex version adtdirect/c3ddirect opendwg toolkit/viewkit dgn libraries dgndirect, c++ version (2.x+) dgndirect libraries (legacy 0.99xx)
all times are gmt -7. the time now is 01:06 amfff">.
- - -
copyright ?2000 - 2009, jelsoft enterprises ltd.
copyright 1998-2008 open design alliance inc.
size of your activex
hi,
you have a sample odamfcappdll which use dll.
i have created an activex which use dwgdirect dll, and the size is now 2 mb.
thanks,
laurent
i think 2m is the size of application itself without dd dlls.
an application statically linked with dwgdirect may be of less size than all dd dlls. for example odreadex and odwriteex samples statically linked with dd have the size of 4.5m and odamfcapp using much more functionality is of 6.5m size.
the size can be reduced by turning off acis support (surely 3dsolids would not be rendered in this case and acis objects loaded from file would not be converted between dwg 2004 and minor dwg and dxf).
we are also going to provide more flexibility to avoid linking with unnecessary functionality in future.
btw, rajesh, are you sure mfc042d.dll and msvcp60d.dll are the correct names? they seem to be debug dlls.
sergey slezkin

size of control reduced to 1/2
hi mr.laurent & mr.sergey slezkin
i would like to thank u all for the positive reply. i solved the problem by reducing the size of the ocx to one half. the earlier one was debug build and when i tried release version the size seems to be one half of the earlier one. now its size is 4.02 mb.
thank u very much
regards,
rajesh parameswaran

size issue solved without using release build.
hi all,
i found that without using the release build, we can reduce the size of the application. all u have to do is:
on the link tab, in the project options field, type in "/opt:ref". this tells the linker to continue optimizing away unreferenced code. this is the default when debug information is turned off, but it defaults to off when you tell the linker to generate debug information. failing to specify this will cause your executables and dlls to get 10-20% larger. you should also specify /ignore:4089 to tell the linker to not generate warnings if it optimizes away all references to a dll (this tip works with vc++ .net also).
u can get more details from the following link..
---------------------------------------
regards,
rajesh parameswaran.