I was trying to avoid this, because I wanted to preserve the function names. However, this seems like a reasonable workflow, I will just cross my fingers that these functions are not used all over the place. Thanks for your help.
Mike
I was trying to avoid this, because I wanted to preserve the function names. However, this seems like a reasonable workflow, I will just cross my fingers that these functions are not used all over the place. Thanks for your help.
Mike
Correct. The static library is already in use and could be used as is in Visual Studio 6.0. However, with changes made in Visual Studio 2003 and above to remove the _io routines, I can no longer link the static libary directly into VS2005. To solve this I assume that I can create a wrapper DLL/import lib on top of the static lib using Visual Studio 6.0, but I'm not sure I understand what I need to do to accomplish this. I only wish to expose the functions that I use. There are about 40 of them.
Mike
I have a static lib that we no longer can find the source code for. We want to continue to use the library, but have problems with it in the context of Visual Studio 2005. It uses I/O routines that are no longer supported. I would like to build a mini DLL around this library exposing the functions from the library that we use, but I'm not sure how to do this. I have a static library and an include file that contains export statements for the library. I thought about using dumpbin to get the symbols out of the library, but there are a lot of symbols and I'm not sure what out of the symbols I'm suppose to pull for a .def file. Any one have ideas?
Mike
I have an application that produces images that are sent to a plotter (E size sheet). The images are huge, and when sent to the printer cause the spool files to become extremely large (sometimes killing the process). To reduce the spool size I thought that I would be able to band/tile the images to the printer and to force it to print and discard what I sent to reduce the spool file size. After looking at what was available in GDI and GDI+, I could not see a way to do this. I did see some information on BandInfo and NextBand, but neither one is well documented and NextBand states that it is no longer used. Does anyone have ideas as to how I can to this? Second, are there ways that I can compress the image to reduce the spool file size?