--- Quote Start ---
I had the same linker errors and chris.lark's answer didn't solve it for me. What worked for me is: 1) Do NOT manually add the link.exe location to the PATH environment variable 2) call the altera/15.1/hld/init_opencl.bat file which sets up the environment. The init script checks if link.exe is found and if it is, it assumes that the visual studio environment has been set up correctly. Only if link.exe is not found, it will "guess" the visual studio installation (looking for VS10, VS11, VS12 in that order) and then call the visual studio script vcvars64.bat which (supposedly) sets some env variables to point to the right places. (Alternatively, you can of course put the link.exe in PATH and call the vcvars64.bat manually, instead of the init_opencl.bat, to keep the guesswork out of the build step).
--- Quote End ---
I get the following error when I run the init_opencl.bat script:
--- Quote Start ---
VisualStudio's link.exe is not on the path. Guessing its location.
\Microsoft was unexpected at this time.
--- Quote End ---
Honored Contributor
