T
tom
Ok i realize some will scoff at this question ...
but i've never created dlls b4. always static libs because generally i
need speed in num theory/cryptographic uses.
I created a static lib of some math routines ... comes out to about 19
megs
created a dll of the same math routines [same source and header files]
came out to 600 kb
I take it I have to keep the obj files around (to go with the dll) and
the dll is just some type of interface stub???? cause how the BLEEPIN
heck could it be 1/1000th the size of a static lib? lol
[going to go compile the stuff with gcc later this week but for now i
was using vis studio 2003]
i know the "purpose" of a dll vs static etc blah blah yackety smackety
i just dont get why the actual code involved would be 1/1000th the
size with the same compiler options one being stuffed into a static
lib the other into a dll lib [unless ... it still needs to get at the
actual code in the objs which makes the most sense to me ...] (or the
dll is a stub interface to the tarballed routines and vis studio
stuffed a rolled up obj in some other dir on me??? i really hate the
lack of "detailed" documentation with winblows ]
c++ya,
tc
but i've never created dlls b4. always static libs because generally i
need speed in num theory/cryptographic uses.
I created a static lib of some math routines ... comes out to about 19
megs
created a dll of the same math routines [same source and header files]
came out to 600 kb
I take it I have to keep the obj files around (to go with the dll) and
the dll is just some type of interface stub???? cause how the BLEEPIN
heck could it be 1/1000th the size of a static lib? lol
[going to go compile the stuff with gcc later this week but for now i
was using vis studio 2003]
i know the "purpose" of a dll vs static etc blah blah yackety smackety
i just dont get why the actual code involved would be 1/1000th the
size with the same compiler options one being stuffed into a static
lib the other into a dll lib [unless ... it still needs to get at the
actual code in the objs which makes the most sense to me ...] (or the
dll is a stub interface to the tarballed routines and vis studio
stuffed a rolled up obj in some other dir on me??? i really hate the
lack of "detailed" documentation with winblows ]
c++ya,
tc