Classic/Legacy CodeWarrior中的主题 Re: Processor Expert tab is empty

Processor Expert tab is empty

Hawkeye — Tue, 13 Feb 2007 03:41:23 GMT

We have 3 developers working on a project and are using a VCS. After I got the latest copy of the project files the Processor expert tab was empty. The other developers do not have this problem.

We are using version 7.3 of CodeWarrior 56800/E with ROHS USBTAP update.

Any suggestions?

Thanks

Re: Processor Expert tab is empty

oskay — Tue, 13 Feb 2007 07:04:06 GMT

The same thing has happened to me several times. I suspect that the only solution is to not use Processor Expert. It's simply not trustworthy since this can happen-- ever. I like to contrast this behavior with that of my code in C, which is easily backed up and doesn't just disappear!

The only thing that I've been able to do is use very few of the PE "features" so that it's faster when I have to rebuild the project from scratch.

Re: Processor Expert tab is empty

CrasyCat — Wed, 14 Feb 2007 19:40:43 GMT

Hello

Just need more info here.

In the original post you say that you are using a VCS.

I assume you mean that you are checking source file in and out in a Version control software before you start building an application.

Which files are you checking in?

Just want to make sure you are checking the appropriate ProcessorExpert files to retrieve all information.

CrasyCat

Re: Processor Expert tab is empty

sricker — Thu, 15 Feb 2007 22:35:39 GMT

I am interested in knowing which files from a project should be in VCS.

Re: Processor Expert tab is empty

CrasyCat — Thu, 15 Feb 2007 23:03:47 GMT

Hello

I would say:

- All C and assembly source files

- All header files included there

- The linker command file (.lcf)

- The exported project .xml file. Instead of placing the .mcp file (which is a binary file) into your

VCS system, I would recommend you to export the project to a .xml file (using menu entry

File -> "Export Project"). This is an ASCII text file and can be easily checked in/out.

- The ProcessorExpert configuration file (.G_C). This is an ASCII text file containing internal information

about the Processor Expert project generation.

- The ProcessorExpert Project file (.pe). This is an ASCII text file containing a description of

the beans included in your project with their properties.

That should be it.

CrasyCat

Re: Processor Expert tab is empty

sricker — Thu, 15 Feb 2007 23:11:52 GMT

CrazyCat,

This means exporting the project as .xml each time you wish to commit, correct? I have been using the .mcp file with CVS without issue (so far) but I understand it would be better as xml.

Thanks,

Shawn

Re: Processor Expert tab is empty

Hawkeye — Fri, 16 Feb 2007 01:04:48 GMT

Jumping back a few posts - I had a working project, got a new version of the .pe file and the problem occurred. Freescale quickly responded to an SR and said to re-install Metrowerks. This solved the problem.

The discussion on which files to archive is helpful. We have archived the mcp file but since SourceSafe does not allow multiple checkouts of a binary file we let it get out of date. We shall now switch to the xml format.

Thanks

Re: Processor Expert tab is empty

CrasyCat — Fri, 16 Feb 2007 15:36:08 GMT

Hello

Well my point with checking in the .xml file is that some VCS software are limited or do not allow checking in/out binary files easily.

Also when you are checking a binary file in, you just have the raw binary and you do not see what has changed there between the two versions.

Meaning retrieving differences in project settings from a .mcp file will be impossible.

It is possible for a .xml file.

Note that if you check the .xml file you have to import it in CodeWarrior to convert it to a .mcp file again.

CodeWarrior can process only .mcp files.

The xml is just here to get a human readable file containing project settings.

At the end of the day it is up to you to decide whether you want to check a binary or a .xml file.

CrasyCat