CodeLite 9.1.8 and Portable Visual C++ 14.0 (2015) (Bug?)
Posted: Tue Jun 14, 2016 1:02 am
Hello everybody,
I'm new here and stumbled upon a problem with a self made portable version of the Visual C++ 14.0 Compiler.
I zipped the compiler (Directories "common7", "VC", "XML") & the platform SDK (directories "bin", "include", "lib" ..) to be transported to another PC without Internet connection (and to be prepared for microsoft's change of mind by unreleasing the standalone build tools - what they did in the past).
After I unzipped the compiler and the platform SDK in another directory on a seperate hard disk, Code-Lite was unable to identify the compiler location, not even by manually selecting the directory.
I had to manually copy the "VC++" compiler parameters from the text-file "[CodeLite-Base-Directory]/config/build_settings.xml.default" to the build-settings dialog to work around this problem.
On a system where the build tools were installed with the online installer, CodeLite is been able to find Visual C++ 16.0 automatically.
So my understanding is, that CodeLite recognizes the compiler not by files (cl.exe, link.exe, rc.exe) but some other indicator(s) that I haven't figured out yet.
Maybe some of you know a more elegant workaround or even a solution to the problem.
Thanks in advance.
I'm new here and stumbled upon a problem with a self made portable version of the Visual C++ 14.0 Compiler.
I zipped the compiler (Directories "common7", "VC", "XML") & the platform SDK (directories "bin", "include", "lib" ..) to be transported to another PC without Internet connection (and to be prepared for microsoft's change of mind by unreleasing the standalone build tools - what they did in the past).
After I unzipped the compiler and the platform SDK in another directory on a seperate hard disk, Code-Lite was unable to identify the compiler location, not even by manually selecting the directory.
I had to manually copy the "VC++" compiler parameters from the text-file "[CodeLite-Base-Directory]/config/build_settings.xml.default" to the build-settings dialog to work around this problem.
On a system where the build tools were installed with the online installer, CodeLite is been able to find Visual C++ 16.0 automatically.
So my understanding is, that CodeLite recognizes the compiler not by files (cl.exe, link.exe, rc.exe) but some other indicator(s) that I haven't figured out yet.
Maybe some of you know a more elegant workaround or even a solution to the problem.
Thanks in advance.
