Bug #503 "strings" can't compile in VS.NET 2003
Submitted: 26 May 2003 4:55 Modified: 18 Jul 2003 11:04
Reporter: Meng Wang Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Compiling Severity:S3 (Non-critical)
Version:4.0.13 OS:Microsoft Windows (Windows 2000 server)
Assigned to: Bugs System CPU Architecture:Any

[26 May 2003 4:55] Meng Wang
Description:
i have try compile in vc.net 2003 "strings" get an error :

MASM : fatal error A1017: missing source filename

how to fix it's? 

How to repeat:
i have try compile in vc.net 2003 "strings" get an error :

MASM : fatal error A1017: missing source filename

how to fix it's?
[26 May 2003 5:27] Miguel Solorzano
I have compiled the 4.0.13 source release with Visual Studio .NET 2002.
Please verify if you have at \string directory the strings.asm and the
strxmov.asm files. These files are compiled with custom build command
using the ml.exe compiler assembler:

ml /Cx /nologo /DDOS386 /DM_I386 /Zm /coff /c /Fo $(Outdir)\$(InputName).obj $(InputPath)
[26 May 2003 8:30] Meng Wang
/string? i have strings.asm and Strxmov.asm at /srtings :)

<File
			RelativePath="Strings.asm">
			<FileConfiguration
				Name="Release|Win32">
				<Tool
					Name="VCCustomBuildTool"
					CommandLine="ml /Cx /nologo /DDOS386 /DM_I386 /Zm /coff /c /Fo &quot;$(Outdir)&quot;\&quot;$(InputName)&quot;.obj &quot;$(InputPath)&quot;
"
					Outputs="$(OutDir)\$(InputName).obj"/>
			</FileConfiguration>
			<FileConfiguration
				Name="Debug|Win32">
				<Tool
					Name="VCCustomBuildTool"
					CommandLine="ml /Cx /nologo /DDOS386 /DM_I386 /Zm /coff /c /Fo &quot;$(Outdir)&quot;\&quot;$(InputName)&quot;.obj &quot;$(InputPath)&quot;
"
					Outputs="$(OutDir)\$(InputName).obj"/>
			</FileConfiguration>
		</File>

		<File
			RelativePath="Strxmov.asm">
			<FileConfiguration
				Name="Release|Win32">
				<Tool
					Name="VCCustomBuildTool"
					CommandLine="ml /Cx /nologo /DDOS386 /DM_I386 /Zm /coff /c /Fo &quot;$(Outdir)&quot;\&quot;$(InputName)&quot;.obj &quot;$(InputPath)&quot;
"
					Outputs="$(OutDir)\$(InputName).obj"/>
			</FileConfiguration>
			<FileConfiguration
				Name="Debug|Win32">
				<Tool
					Name="VCCustomBuildTool"
					CommandLine="ml /Cx /nologo /DDOS386 /DM_I386 /Zm /coff /c /Fo &quot;$(Outdir)&quot;\&quot;$(InputName)&quot;.obj &quot;$(InputPath)&quot;
"
					Outputs="$(OutDir)\$(InputName).obj"/>
			</FileConfiguration>
		</File>
[30 Jun 2003 2:04] Lenz Grimmer
Greg, could you please take a look at this? Thanks in advance.
[2 Jul 2003 20:51] Meng Wang
in VC++ Projects files (*.vcproj).
[3 Jul 2003 8:37] Michael Widenius
We have tested 4.0 with VC 6.0 and VS. NET without any problems.

I suspect that something is wrong with the assembler handling on VS .NET 2003 but can't verify as I don't have access to this just now.

To go around this problem, please us the .c version of the assembler string functions instead.  You can find a readme file about this in the strings directory.
[18 Jul 2003 1:56] Meng Wang
used .c version without any problems.
[18 Jul 2003 11:04] Greg Weir
VS.NET currently will only compile the strings library in its .c version, without the assembler 
modules.
[21 Sep 2003 1:23] Meng Wang
compiled in vs.net 2003 with::

ml /Cx /nologo /DDOS386 /DM_I386 /Zm /coff /c /Fo $(Outdir)\$(InputName).obj $(InputPath)

:)