The basic question is whether a total newb could successfully carry out a
compile using VS and something called "Boost" without undertaking a new
career.
I mess around with TI's MSP430 controllers, and it has been my idea to modify
TI's BSL flashing software to allow for the use of generic USB-to-Serial
adapters such as the FT232, CP2102 and CH340G as the hardware interface. I
thought that since TI makes the source code available, that should be doable.
I was able to get that done for BSLDEMO2 which is used with the older F2xx,
F4xx and G2xx parts. The code is in C, has no dependencies, and I was able
to compile it with LCC-Win32. But of course you don't really need to know
anything about compilers with LCC - it even creates something called the
"Make" file for you.
But then I looked at BSL-Scripter, which is used with all the newer MSP43x
parts. It's written in C++ for VS, with dependencies I know nothing about,
including Boost, and apparently was compiled by TI with VS 2013. This was
clearly beyond me, but I was bailed out by a guy who saw my posts about this
on the Energia forum, and who did the recompile and posted it on Github. He
fixed my suggested code changes, and made other changes so the compile could
be done with VS Community 2017 in case anyone else wanted to make further
changes. And as it turns out, I do need to make another change. But I don't
have his email, and he hasn't been back to Energia, and I don't think there
is any way to reach someone on Github. Here's his repo:
https://github.com/drcrane/bslscripter-vs2017
When I look at the readme there, I see almost nothing that I understand. I
know what code changes to make, but the roadblock is the compile process. As
a practical matter, is it feasible for someone who knows nothing about this
process, has no experience with VS, or Boost, to successfully recompile this
software without weeks of study? And could I confirm success because my
resulting .exe (before the new changes) would be byte-for-byte identical to
drcrane's release version?
Alternatively, if I found someone who already has VS Community 2017
installed, and already has Boost compiled, would it be a reasonable thing to
ask him to download the source and compile it? I mean, is this a 10-minute
process, or a totally unreasonable request?
I would appreciate thoughts or suggestions about how to proceed. I should
also say that I and others have suggested to TI that they need to make these
changes to their official versions of BSLDEMO2 and BSL-Scripter, which of
course would be signed by TI, but there's no indication they are considering
doing that.