RELEASE NOTES ------------- This README describes some specific details for running MICO under Windows using the Visual-C++ compiler from Microsoft. Beware that the port isn't finished yet. The BOA daemon as well as the services are not yet ported (although, of course if these components are running on Unix machines, they are already accessible via IIOP). PREREQUISITS ------------ You will need Visual-C++ 5.0 Service Pack 3 to compile MICO for Windows. Note that without Service Pack 3 (Microsoft terminology for bug fixes), you won't be able to compile the sources. Although MICO should run under Windows 95/98, the Makefiles make use of some features only found in NT's shell cmd.exe. Therefore you have to compile MICO under NT (or buy our book... ;-) You don't need flex and bison; the MICO sources already contain the files generated by these tools. SP3 is available from: http://www.microsoft.com/msdownload/vs97sp/full.asp HOW TO INSTALL THE SOURCES -------------------------- Unzip the files at any location. You do not need to run the configure script (which would be pretty useless anyways). HOW TO COMPILE -------------- Simply change to the directory where you have unzipped the MICO sources and type: nmake /f Makefile.win32 this will build all the necessary DLLs and executables in a subdirectory called "win32-bin", which will be created during the make process. The content of this directory is the only thing you need for building MICO applications. You can move it to your preferred location. You should modify the PATH environment variable to include this directory. If, for example, the MICO sources were unziped in C:\temp\mico, then type the following: PATH C:\temp\mico\win32-bin;%PATH% Take a look at mico\demo\mfc\README to see an example that uses MICO in conjunction with the MFC class library. PROBLEMS -------- Porting MICO to Visual-C++ was a major pain. Sometimes a MICO application will crash inside mico.dll. As far as we can tell this is related to a bug in the Microsoft Linker when dealing with global constructors. If this happens to you, try to link typecode.obj and util.obj statically with your application (a copy of these object files can be found in win32-bin\lib). This usually resolved our problems... sig... HELP ---- Feel free to send comments, patches, or whatever over the mailing list!