Open abelykh0 opened 3 years ago
@BenVillalobos, do you have any update on this issue? ETA?
This is a problem I had and still have, workaround is to kill MSBuild before each build (taskkill /f /im MSBuild.exe in cmd)
but i have a shit ton of other errors with nothing more than a stacktrace, msbuild is so fucking shit..
The workaround here is the solution I'd expect. MSBuild doesn't control the Linux.Makefile.Targets file. I see it's installed under VS, is this on the cpp side of things? @yuehuang010
It looks like ConsolidateSourcesToCopy
could do an existence check on the output directory if it doesn't exist.
@xXTurnerLP, to best reach the team, can you please create a ticket in DeveloperCommunity.
Issue Description
Linux Makefile project is not building from MSBuild (builds fine from Visual Studio)
Steps to Reproduce
In Visual Studio add a remote connection (Tools > Options > Cross Platform > Connection Manager > Add) In Visual Studio create a new "Makefile project" Rename it to "myprog"
Add file
main.cpp
like thisAdd file
makefile
(no extension) like this (note, it needs real tabs, not replaced by spaces, otherwise you'd get "*** missing separator")In Project Propertied > Remote Build specify: Build Command Line: make Outputs: $(Platform)/$(Configuration)/myprog
Make sure project builds from Visual Studio Delete
bin
andobj
files from the project folder Open "Developer Command Prompt for VS 2019", change current folder to the project folder, run the following command :It fails. Note, if the folder
obj\x64\Debug
exists (even empty), it works.Expected Behavior
Should build
Actual Behavior
You will get the following output:
Analysis
If I add the following workaround (modify project file), it starts to work:
Versions & Configurations
Microsoft (R) Build Engine version 16.8.1+bd2ea1e3c for .NET Framework Copyright (C) Microsoft Corporation. All rights reserved.
16.8.1.52902