From: Erik de C. L. <ml...@me...> - 2008-05-26 21:00:47
|
Earnie Boyd wrote: > I would put the .dll files with the .exe files. The Windows OS will > find it in that directory. Yes, but only for those .exe files in the same directory. > If this is a development library then > you'll also have header files and import libraries as well I assume. This library is already used by hundreds if not thousands of existing windows programs. > So if I have package foo then I would install into foo/bin, foo/lib, > foo/include, foo/samples and foo/docs. That was my intention. > No other consideration should > be made as to where to install and no other consideration for modifying > PATH should be done in the install. The developers who use your dll > will need to ship it with their executable to make the executable > functioning. The thing is, I expect the majority of people who install my DLL to be users, not developers. To expect these users to run my installer and then find all the old versions of the library and copy the new version over the top of the old is simply too much for most dumb users. I expect developers who use my library to use my installer for my library. My installer would find the existing version of the library in the windows system directory, check its version and only replace it if the new version is older than the new version. Personally I think this is far more sane than the way things are normally done on the windows platform. Erik -- ----------------------------------------------------------------- Erik de Castro Lopo ----------------------------------------------------------------- "C++ is the only current language making COBOL look good." -- Bertrand Meyer |