Troubleshooting SCC integration

Important note - The IAR Embedded Workbench shared components version 8 and later (introduced 2017) do not provide SCC integration.

Introduction

IAR Embedded Workbench versions from 2005 to 2016 supplied an integration with the Source Code Control (SCC) API.

This API was also known as Source Code Control Interface (SCCI)..

Discussion

Try these actions to make the SCC API to work:

Step 1

Verify that your version control system supports SCC.

Step 2

Verify that your version control system supports SCC is correctly registed in the Windows registry. (HKLM = HKEY_LOCAL_MACHINE)

• All SCC providers should register themselves under:
  • HKLM\SOFTWARE\SourceCodeControlProvider\InstalledSCCProviders.
  • or under:
  • HKLM\SOFTWARE\Wow6432Node\SourceCodeControlProvider\InstalledSCCProviders
  • More information provided in Microsoft KB 305097.
• You should find something like
  • Name: “Microsoft Visual SourceSafe”, Data: “Software\Microsoft\SourceSafe”

Every provider should also has a link to their DLL as given above under HKLM\.

• From the example above you should find at
  
  • HKLM\Software\Microsoft\SourceSafe
  • Name: “SCCServerPath”, Data: “C:\vss\win32\ssscc.dll”

Step 3

Make sure that all the source files reside in the same directory as the ewp project file, or in subdirectories of this directory.

Step 4

Make sure to first create a project in the SCC client application.

Step 5

When that is done, connect the SCC project to the project in IAR Embedded Workbench.

Step 6

Be patient, give the API time to work. The SCC is slow, simple, and limited. Please let some time pass after you have added the project to source control.

We have seen examples where it takes around a minute before the connection is working as expected.

Conclusion

The IAR Embedded Workbench documentation (from 2005 to 2016) also had information about SCC connection.

All product names are trademarks or registered trademarks of their respective owners