What files to store into Perforce?

Hi Matt,

I'm not too familiar with Perforce but regarding your statement:

MATT GESSNER said:

Since I apparently can't use the Perforce plugin for Eclipse because CCS4 doesn't use a recent enough version

Have you thought about moving to CCSv5? It uses a recent Eclipse version (3.7).

Thanks

ki

The perforce plugin says it supports versions 3.5 and 3.6 of Eclipse.

So I'm out of luck there, too.

Essentially, perforce simply copies files to and from the repository.

But the question here is WHICH files?

When I try it, and then do a Project -> Import Existing...

I get nonsense about the managed makefile process not working.

Thanks.

MATT GESSNER said:

The perforce plugin says it supports versions 3.5 and 3.6 of Eclipse.

Looks like people have gotten it to work with 3.7:

http://forums.perforce.com/index.php?/topic/1073-perforce-plugin-for-eclipse-37-indigo/

I am not sure I want to switch tools just for Eclipse.   I'd rather just figure out what files and what mechanism I need to use to move the files to and from the repository.  I've had so many issues with CCS4's lack of support for AM35x that I think I'd rather stay with what I have, since I've made lots of changes to XML files for support.

We are facing a similar problem:

We are using CCS 5.2.1.00018

We'd like to know which files are important to keep track and versions (apart from the source files, like projects settings, which projects are contained in a workspace), and which files we can skip (like history, logs, lock files).

Bottom lines:

1. Be able to get all the "important files" into a "clean" computer, and be able to open a CCS on this workspace and work.

2. While working on a computer on a certain workspace, and when "getting latest version" from the version control tool into a local workspace, don't mess with irrelevant files (like history, logs, lock files) that don't match local files.

Thanks.