I went into the command window, and set PATH to point to a different set of libraries.
But when I do the BUILD, it still is trying to use the wrong library set.
And I get the same missing entry point.
So apparently, changing that PATH variable does not affect this issue.
Maybe the Visual studio software overrides that ?
Changing the environment inside a command window session makes changes that apply only to commands executed from that window. By design, it does not change the system environment, and does not affect the environments of any VS sessions that you run simultaneously or subsequently. When you terminate that command window session, the changes are discarded.