yang686526

dwgdirect application size
dwgdirect application size
i would like to know the size of very basic applications compiled and linked with dwgdirect c++ version 2.3.1
a very simple application i have written using dwgdirect c++ libraries (based on odreadex) which basically opens a dwg file and then saves it back as an older format dwg file is about 17.5mb in size in either exe / dll form. [application compiled and linked using borland builder 6].
only the very core dwgdirect libs have been included to ensure a successful link.
is this the norm? could someone please provide sizes of exe's built from odreadex and odcopyex for comparison.
some previous application built using dwgdirect was very much smaller in size.
regards
keith
the size of readex built with vc6 is about 7m (release)
quote:
some previous application built using dwgdirect was very much smaller in size.
which previous version do you mean? it seems that the size of libraries did not change significantly since 2.0 at least.
sergey slezkin
hi sergey
i will check the application size built from the older dwgdirect libs (other than the current version).
i am assuming that your odreadex at 7mb still requires the dll's to be present as well?
the borland builder application at 17mb in exe form does not have any dependencies on external dll's (or at least this is my take on it).
regards
keith
vc6 release odreadex.exe (7m size) is statically linked with dd.
odreadexdll.exe (which requires dd dlls to run) is of 360k size.
sergey slezkin
hi sergey
is it possible to list the exact *.cpp *.h and *.lib files required (absolute minimum configuration) to compile the odreadex.exe?
i have noticed the sizes of msvc (release code) produced as both exe (static linked) and odreadexdllexe ?(which requires dlls present) and noticed this discrepancy and i am trying to understand why the difference between my borland builder code (at 17mb) versus the msvc code (at 7mb).
regards
keith
vc6 readex project includes:
cpp files (besides 4 files from readex folder:
\exservices
exhostappservices.cpp, exsystemservices.cpp,
exundocontroller.cpp, odfilebuf.cpp
\common\tostring.cpp
libraries:
dd_spatialindex_dll.lib dd_alloc_dll.lib dd_gs_dll.lib dd_db_dll.lib dd_ge_dll.lib dd_root_dll.lib dd_acisbuilder_dll.lib dd_gi_dll.lib
sergey slezkin
hi sergey
apologies for raising this again but i have now compiled the same source code using the latest version of dwgdirect and the borland exe now stands at 18.4mb.
i have included only the cpp, h and lib files listed in your previously email and linked successfully.
i have also checked against a previous version of the same program using older dwgdirect libraries and it was around 8mb.
all the program actually does is load a dwg and give the user the option of saving it back in another dwg format. eg ac 2007 -> ac 2000
i am not sure how borland libraries are created from other msc code for example but i would like to hear from other borland users how large their exe's are.
regards
keith