Workbench with SVN problems

[M.Rehberg]

We have a rather large group of programmers this year, and several of them have extensive C++ knowledge. We used WindRiver Workbench last year, and the team agreed to use it again this year. Last year we also used SVN as an archive tool, but with only a few programmers there wasn’t much of a need to use it during development. This year we would like to use SVN (or maybe Git) as a versioning tool on all the programmers’ computers.

The repository is all setup, and the first few “share”, and “checkout” tests worked fine on my Windows7 desktop computer at home. The trouble started when we loaded the development environment on several notebooks, and netbook computers running Win-XP, Vista, and Windows-7. Some of them work some of the time, all of them have problems building projects they checkout some of the time. It is not consistent at all. I checked out the same project 10 times in a row (changing the name each time so they had unique directories in the workspace). Sometimes they will checkout with the following in the name:

“(Host OS (Native Development) Downloadable Kernel Module Project)”
If it does, there is no hope for it building and creating the “.out” file.

It must have the following in the project name to build:
“(Wind River VxWorks6.3 Downloadable Kernel Module Project)”

We do nothing different from one checkout to the next. In 10 checkouts, 3 were OK, and 7 were not.

The netbooks seem to be more prone to this than the systems with more performance. There are no errors during the checkout, it just doesn’t create the proper project.

Very frustrating….

We have installed the Jan 9th updates for LabView, and WindRiver WB
For SVN we have installed the Subclipse plug-in to Eclipse:
http://subclipse.tigris.org/update_1.6.x
We are using:
SilkSVN Vers 1.6.5
TortiseSVN Version 1.6.6.17493

One other note. Sometimes even after a good checkout the first build will not create the .out file. The “PPC603gnu” directory will only have a Makefile in it. We found that if you delete the PPC603gnu directory, and build the project again, it will recreate the directory, and build all of the objects and produce the .out file.