Kinook Software Forums

Kinook Software Forums (
-   [VBP] Third Party Tools (
-   -   Support for MS eMbedded C++ compiler (

DHearn 09-03-2003 12:28 PM

Support for MS eMbedded C++ compiler
Using the standard VS6 C++ build step and passing the name of the VCW workspace file appears to work correctly. The only problem was that I had to override the default location of the command-line compiler because it could not find the ECV compiler. Am I missing an environment variable?

kinook 09-03-2003 01:58 PM

The Make VC6 action looks for the following registry values when attempting to auto locate the EVC compiler:

1) HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr entVersion\App Paths\evc.exe\
2) HKEY_CLASSES_ROOT\vcpfile\shell\open\command\
3) HKEY_CLASSES_ROOT\vcwfile\shell\open\command\

These are created by EVC 3 when installed, but apparently none of these are created/updated by EVC 4, so if you're using that version, you will have to tell it where the compiler is (usually at \Common\EVC\Bin\EVC.EXE) or create/update one of the registry entries above.

DHearn 09-03-2003 02:14 PM

Thanks, we are using EVC 4. It updates the following new registry keys instead of the ones used by EVC 3:

1) HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr entVersion\App Paths\eVC4.exe\
2) HKEY_CLASSES_ROOT\vcpfile\shell\open EVC4\command\
3) HKEY_CLASSES_ROOT\vcwfile\shell\open EVC4\command\

All times are GMT -5. The time now is 12:32 PM.

Copyright 1999-2019 Kinook Software, Inc.