Windows 10: C++ - compile: error MSB4057: The target "Build" does not exist in the project.

Trying to Build a C++ project --> Get this error: error MSB4057: The target "Build" does not exist in the project.Any ideas perhaps ?

:)

 

How to avoid the MPLAB X IDE v5.10 behavior of build errors whenever a user clones the project Github Repository

I am asking how to correct the unexpected behavior of MPLABX IDE v5.10, detailed below. The end goal of this would be to successfully build the code project in MPLABX by understanding what could be causing the unexpected build errors.

MPLABX IDE v5.10 does not produce build errors on the source computer running Windows 10 that pushed the local code to the repository SWIM-team-junior-project. Any other computer that clones the repository using Git Command Line tool in PowerShell on Windows 10, will show build errors.

To see the repository issue with the Makefile output see the link SWIM team project Github Issue

To reproduce the entire (quite lengthy) process, the steps below show how to do so:

• git clone GitHub - PeterStine/SWIM-team-junior-project: Oregon Institute of Technology Junior Project Sequence, Surface Water Information Management System (SWIM)
  

Followed by creating a new MPLABX project, with the following settings:

• Microchip Embedded -> Standalone Project
  
• Select Device -> PIC32MZ2048EFG144
  
• Select Tool (Optional) -> Simulator
  
• Select Compiler -> XC32 (v2.15) [C:\Program Files (x86)\Microchip\xc32\v2.15\bin]
  
• Select Project Name and Folder -> "practice_master_clone_a"
  

And in the GUI for MPLABX IDE the following screenshots and captions describe the steps used to reference the cloned repository code files into the MPLABX IDE project named "practice_master_clone_a". Note that the integrated Git tool in MPLABX IDE is not being used. The Git command line tool is being used in PowerShell.

• Right click on "Header Files" and in the context box select "Add existing items from folder"
  
• In the "Add Files" Dialogue box, click on "Add Folder...".
  
• Browse to location of cloned repository.
  
• Once located, select "Files of Type" -> "Header Files".
  
• Once Selected, enter full path name of GFX folder and click "Select"
  
• Repeat adding the directories "GFX", "RFM69", and "RTC" using the "Files of type" listed below
  
  • Header Files (.H .SUNWCCh .h .hpp .hxx .tcc .inc .INC)
    
  • C++ Source Files (.C .c++ .cc .cpp .cxx .mm)
    
  • C Source Files (.c .i .m)
    

Lastly, enter "Project Properties" in the dialogue window showing from right-clicking on the name of the project in the Navigator window, shown in the image below:

• Project Properties
  
• Followed by changing to "Categories:" -> "Conf: [default] -> XC32 (Global Options) -> xc32-ld
  
• Then change the Heap size (bytes) and Minimum stack size (bytes) both to 2048 as shown highlighted in red in the screenshot below:
  
• Project Properties Categories
  

Following all of the above steps results in a "BUILD FAILED", the output of which is included at the very bottom of this post. However, the build is successful for the source machine that pushes the original MPLABX IDE project to the github repository.

 

How to build a .waproj MSIX project using msbuild (from build tools)

I am trying to work out how to build my .waproj project, and builds a bundle for a WINUI3 project from the command line (for a teamcity auto CLI build system)

I have installed VS 2022 build tools (C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\MSBuild\Current\Bin), and am trying to build the .waproj file using the full path to msbuild (to make sure I get the correct version), eg

```

"C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\MSBuild\Current\Bin\msbuild" "TestAppWinUI (Package).wapproj" /p:UapAppxPackageBuildMode=SideLoadOnly /p:AppxBundle=Never /p:AppxPackageOutput=d:\\0\\MsixDesktopApp.msix /p:AppxPackageSigningEnabled=false

```

But I get the following errors

```

Build started 14-Jun-22 11:05:23 AM.

Project "D:\dev\TestApps\TestApp\TestAppWinUI\TestAppWinUI (Package)\TestAppWinUI (Package).wapproj" on node 1 (default targets).

D:\dev\TestApps\TestApp\TestAppWinUI\TestAppWinUI (Package)\TestAppWinUI (Package).wapproj(36,3): error MSB4019: The imported project "C:\Program Files (x86)\Microsoft

Visual Studio\2022\BuildTools\MSBuild\Microsoft\DesktopBridge\Microsoft.DesktopBridge.props" was not found. Confirm that the expression in the Import declaration "C:\Program Files (x86)\Micr

osoft Visual Studio\2022\BuildTools\MSBuild\Microsoft\DesktopBridge\\Microsoft.DesktopBridge.props" is correct, and that the file exists on disk.

Done Building Project "D:\dev\TestApps\TestApp\TestAppWinUI\TestAppWinUI (Package)\TestAppWinUI (Package).wapproj" (default targets) -- FAILED.





Build FAILED.



"D:\dev\TestApps\TestApp\TestAppWinUI\TestAppWinUI (Package)\TestAppWinUI (Package).wapproj" (default target) (1) ->

D:\dev\TestApps\TestApp\TestAppWinUI\TestAppWinUI (Package)\TestAppWinUI (Package).wapproj(36,3): error MSB4019: The imported project "C:\Program Files (x86)\Microso

ft Visual Studio\2022\BuildTools\MSBuild\Microsoft\DesktopBridge\Microsoft.DesktopBridge.props" was not found. Confirm that the expression in the Import declaration "C:\Program Files (x86)\Mi

crosoft Visual Studio\2022\BuildTools\MSBuild\Microsoft\DesktopBridge\\Microsoft.DesktopBridge.props" is correct, and that the file exists on disk.



0 Warning(s)

1 Error(s)



Time Elapsed 00:00:00.01

```

Would anyone know how I can fix this?

Thanks in advance

 

Compiling C files on Ubuntu and using the executable on Windows

This is called cross-compiling. You need a "toolchain" (compiler, linker, etc.) that will generate the appropriate code and format, involving:

• The target processor architecture. In your case is is probably the same (x86 or amd64), but sometimes you cross-compile for a different processor, for instance when you build an executable for an ARM processor on your PC.
  
• The target ABI (those are the call conventions used).
  
• The right format
  
• The right libraries, including system libraries.
  

Depending on the project, this may be very easy (just a flag or an environment variable to set somewhere) or very difficult.

You'll find a few pointers here, here or here.