From: AGIS S. <ag...@ag...> - 2001-02-20 06:37:07
|
Hi, I volunteered to convert a large gcc application so that it could be called as a dll from MSVC or MSVB. For this I chose Mingw and have been working through compiling a large number of dependent GNU (and other) libraries - libproj, libpbm for example. There are nine libraries used in total, and I am now at the stage of having successfully compiled them all as Mingw static libraries (.a files), as well as the object files for the main program. As you may have guessed, I wasn't expecting such a large project when I volunteered! I have not taken the last step of building the main program executable because the code also has a reliance on sockets for which I am expecting to link winsock.dll later. I had hoped to somehow combine the static libraries and the program objects into a single dll file, with an appropriate export for just the main program. The calling MSVC program will only need to execute the main program. On getting this far I can't find a way to do that easily as, from my reading of the dll tool documentation, there is no way to just include the static libraries in the dll build. Is my only option to make separate dlls for each of the dependent libraries? Has anyone built something similar to what I am proposing, or are there bigger hurdles that I haven't seen yet? I'm already over time on this and need to decide how or whether to continue. Any advice is very welcome. Regards Neil Klaer ___________________________________________________________________________ AGIS Software ag...@ag... http://www.agismap.com PO Box 441, Franklin, Tasmania 7113, Australia Ph +61 419 107625 Fax +61 3 62663708 ___________________________________________________________________________ |