Hmm. The MSB6006 errors in your original message are exactly what you get if you try to build ClearScript without first running V8Update. Those errors usually indicate that the V8 binaries cannot be found in that directory.

Is it possible that the directory in which you ran V8Update.cmd and the directory from which you loaded ClearScript.sln are not the same?

The build step that's failing for you simply copies the V8 binaries (DLLs and PDBs, not LIBs) to the target directory - bin\Debug or bin\Release relative to the ClearScript root directory. You should be able to do this manually, but we'd love to understand
why it's failing for you.

Could you please do the following: Retry the build in Visual Studio, and when it fails, find the error messages in the Output window rather than the Error List window. Sometimes you'll see more information there, such as "The system cannot find the path
specified.".

To answer your other question, V8Update.cmd applies a small patch to ClearScript\V8\V8\build\v8\tools\gyp\v8.gyp. This causes the generated DLLs to include the platform in their names; e.g., v8-x64.dll. This way the 32-bit and 64-bit V8 DLLs can be in the same
directory. ClearScript itself is platform-neutral (AnyCPU), and selects the appropriate V8 DLL at runtime.

Thanks Klator. Your issue may be due to a somewhat embarrassing bug in the ClearScript project files.

Could you please try the following: Close Visual Studio, move your entire ClearScript directory to a path that doesn't have any spaces in it, and retry. We believe that the spaces in the subdirectory name "Visual Studio 2012" may be causing the problem.

Please let us know if this fixes the problem for you, and we'll fix the project files ASAP! Thanks for your help!