You can thn use mingw to run configure and use CC=cl m.
On 4/30/05, Karsten Ohme <[EMAIL PROTECTED]> wrote: > >> What about [1]MinGW? It supports autoconf/automake and the gcc compiler > >> for building native Win32 applications, with no need of the Cygwin > >> wrapper DLLs. > > > > > > I have heard, that libraries with this are said to be not compatible > > with any other libraries or applications build with MSVC. Actually I see > > no reason for this and I have also not found arguments for this. But I > > have no experience in using MinGW. Maybe somebody has the time. > > The many different installation packages are confusing. Actually I want > > only to download everything needed, but they are offering there their > > whole history, which is not explained. I hope the 50 MB piece is a > > bundled version. > > I have examined the situation by example and wanted to compile a new > Java Wrapper for MuscleCard. Apart from the fact, that unconditionally > which runtime version I use (msvcrt, crtdll, ... (But I do not exactly, > how the different runtime version /MD /MT /ML + debugging versions)) it > complains about unresolved symbols. > > I Quote from the MinGW mailing list: > > > But surely, for C code, gcc with -fnative-struct > > and using the msvcrt.dll C runtime, and MSVC (cl -MD) > > produce totally compatible code? My experience is that an > > executable built with gcc can use DLLs built with MSVC, and > > vice versa, without problems. > > So it is the best to use always the /MD switch and so use msvcrt. > > Paul Garceau writes: > > Far better to rebuild all of your .dlls with either one or the > > other toolset. Trying to build something that uses both during > > runtime is, imho, an invitation to disaster. > > Umm, for C++ code of course as the name mangling and ABI is > different. But surely, for C code, gcc with -fnative-struct > and using the msvcrt.dll C runtime, and MSVC (cl -MD) > produce totally compatible code? My experience is that an > executable built with gcc can use DLLs built with MSVC, and > vice versa, without problems. > > So, C++ seems to be a problem, but this message is from 2001. > > So, I have no result, if the resulting dll is usable. But a problem I > found is, that the MinGW distribution has no winscard.h header files and > also not the important libraries to link. So you need it from another > location. > > So, I found another solution: > > Microsoft has yesterday released > > Windows Server 2003 SP1 SDK with libraries and header files and nmake: > > http://www.microsoft.com/downloads/details.aspx?familyid=EBA0128F-A770-45F1-86F3-7AB010B398A3&displaylang=en > > And also available is a C/C++ compiler suite. > > Microsoft Visual C++ Toolkit 2003 > > http://msdn.microsoft.com/msdn-online/shared/components/ratings/ratings.aspx?ContentID=8140ad56-d23c-428e-b733-6ddfede7152d&mnp2=1&Config=/visualc/ratingscnfg.xml&Print=Default.aspx?print=true&HideDiscuss=1 > > http://www.microsoft.com/downloads/details.aspx?FamilyID=9B3A2CA6-3647-4070-9F41-A333C6B9181D&displaylang=en > > The Runtime libraries are missing, but you can get the msvcrt.lib here: > > NET Framework SDK Version 1.1 > > http://www.microsoft.com/downloads/details.aspx?FamilyID=9B3A2CA6-3647-4070-9F41-A333C6B9181D&displaylang=en > > This is also a free solution and I have nmake makefiles for this. > > Karsten > _______________________________________________ > Muscle mailing list > [email protected] > http://lists.drizzle.com/mailman/listinfo/muscle > -- Martin Paljak [EMAIL PROTECTED] http://martin.paljak.pri.ee/ +372.5156495 - phone _______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
