topic Re: 'New Project' function did not generate main.c if PE is used in Processor Expert Software

'New Project' function did not generate main.c if PE is used

mkrug — Mon, 06 Aug 2012 19:14:47 GMT

Hello,

I just discovered a small, but strange, thing.

I am using CW10.2 for a K60 Tower System. If I setup a new project and include PE the 'wizard' did not generate a separate main.c file although I checked the appropriate box while setting up the new project.

The 'wizard' does if I select 'None' or 'Device Initialization' in the 'Rapid Application Development' dialog box.

First I thought I will get the main.c if I click again on 'Generate PE Code' - however it doesn't.

Simply renaming processorexpert.c (where main() is located) into main.c doesn't really work because anytime I call 'Generate PE Code' I got a new processorexpert.c which will than cause trouble during compiling and linking.

Anyone else have the same experience? Any idea how to solve that?

Markus

Re: 'New Project' function did not generate main.c if PE is used

jimtrudeau — Tue, 07 Aug 2012 05:39:25 GMT

The solution is to get accustomed to the idea that the file named processorexpert.c is the equivalent to main.c. It's just a name after all. There is a relatively obscure thing you can do, which is to tell Processor Expert to NOT generate a main(). But that rather defeats at least part of the purpose of using Processor Expert in the first place.

So, my recommendation is to just get used to the idea that main() is in a file with an unusual name.

Re: 'New Project' function did not generate main.c if PE is used

BlackNight — Tue, 07 Aug 2012 12:09:05 GMT

Hello,

The obscure thing is described at the bottom of http://mcuoneclipse.wordpress.com/2012/03/09/shared-files-maintained-by-processor-expert/.

But doing it that way means that you need to care about it yourself 100%.

But I agree: it is just a file name. So I recommend to stick with it. Maybe that name can be configured in the future.

Hope this helps,