Hi everyone. Has anyone tried building MySQL with Visual Studio .NET 2003? I find two problems:
1) The files /strings/Strings.asm and /strings/Strxmov.asm do not compile due to a command-line parameter in the custom-build call to ml.exe. It seems the upgrade from the .dsp file shipped with the MySQL source to the .vcproj file produced by Visual Studio .NET adds two extra quote marks, so that: ml /Cx /nologo /DDOS386 /DM_I386 /Zm /coff /c /Fo $(Outdir)\$(InputName).obj $(InputPath) becomes: ml /Cx /nologo /DDOS386 /DM_I386 /Zm /coff /c /Fo "$(Outdir)"\"$(InputName).obj" "$(InputPath)" These extra quote marks cause the problem. I was able to fix it by removing them. This is a bug in Visual Studio .NET and not in the MySQL source. 2) The bdb source code includes iostream.h, which no longer exists in Visual Studio .NET 2003 for the purpose of C++ standards compatibility. I was able to fix this by replacing the line: #include <iostream.h> with: #include <iostream> using namespace std; in the files /bdb/include/db_cxx.h and /bdb/build_win32/db_config.h. I will post this information to the MySQL documentation (comments) at http://www.mysql.com/doc/en/Windows_VC++_Build.html. My apologies if this message should only have gone to the Win32 list. Sincerely, Matt Solnit <[EMAIL PROTECTED]> -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
