If you run it from a bash you must add the .exe extension: Administrator@hyperv-target2 /c/kern $ msbuild sh: msbuild: command not found
Administrator@hyperv-target2 /c/kern $ msbuild.exe Microsoft (R) Build Engine version 12.0.21005.1 [Microsoft .NET Framework, version 4.0.30319.33440] Copyright (C) Microsoft Corporation. All rights reserved. MSBUILD : error MSB1003: Specify a project or solution file. The current working directory does not contain a project or solution file. -----Original Message----- From: Ben Pfaff [mailto:b...@nicira.com] Sent: Thursday, August 28, 2014 8:50 AM To: Alin Serdean Cc: dev@openvswitch.org; Eitan Eliahu; Saurabh Shah; Nithin Raju Subject: Re: [ovs-dev] [PATCH] Add build of ovsext.sln using MSBuild On Thu, Aug 28, 2014 at 01:49:24PM +0000, Alin Serdean wrote: > +if VSTUDIO_DDK > +ALL_LOCAL += ovsext_make > +ovsext_make: datapath-windows/ovsext.sln > + MSBuild.exe datapath-windows/ovsext.sln /target:Build > /property:Configuration="$(VSTUDIO_CONFIG)" Isn't it unusual to include the .exe extension as part of the program invocation? _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
