Closed kscieslinski closed 4 years ago
You're totally correct about the purpose of Buildalyzer being to remove all the boilerplate from triggering a compilation. Unfortunately only C# projects are in-scope for this project (VB and F# projects should mostly work as well, but they're not directly supported and I rely on community contributions for those).
C++ projects go through a different compiler (I.e., not Roslyn) and it's been over a decade since I've done any work in C++ so I don't know anything about that toolchain. Normally I'd consider a community contribution if anyone wanted to look into it, but I don't even feel comfortable supporting something that complex long-term for a new toolchain and language, so C++ projects are likely just plain out-of-scope for the foreseeable future.
Sorry!
:( Anyway really neat idea with this project:) Good luck with further development:)
Thanks, and sorry I couldn’t be more help! I’ll keep my eyes open for something similar for C++ though and drop back in if I see anything.
Hi,
Workspace I cannot compile even the simpliest C++ project using Buildalyzer. I'm working on updated Windows 10 with Visual Studio version 16.04. I've download the newest Buildalyzer package form NuGet.
Project structure
Where
Program.cs
from projectcompiler
looks like:And
main.cpp
fromto_compile
project is:Firstly I received an error about not being able to locate
C:\Microsoft.cpp.default.props
which I've solved manually by adding aVCTargetsPath
environment variable:VCTargetsPath=C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VC\v160\
But now I get new error:
I believe the whole idea of Buildalyzer was to resolve those issues automatically and not having to set all those paths by hand (which is a great idea).