At 02:48 PM 6/2/00 -0700, Andrew Begel wrote: Excellent! I usually build using the "gcc no cygwin" method. This is unnecessary since the normal way to build with no cygwin it to call configure like this: ./configure i586-pc-mingw32 These, too, get taken care of by calling configure like above. This one I'll have to look into. ditto. ditto. The normal way to make this work would be to define an API that looks something like this: 1. Each DLL is required to export a set of specific functions with specific names so that the loading application (XEmacs in this case) can hook everything up. 2. Each DLL can expect the application (XEmacs in this case) to export a set of specific functions with specific names so that the DLL can gain access to those aspects of the application that it needs. These kinds of mechanisms eliminate the need to do what you describe below. From your description, I suspect that some significant work needs to be done with regard to defining the API. What would be extremely useful is if you could make a list of the kinds of things that you need access to in the application and another list of the kinds of things that you expect to provide to the application. This kind of information would be useful in beginning the definition of the API. Craig Lanning