Quantcast
Viewing all articles
Browse latest Browse all 36216

Re: Run just an .dxe file when in CCES

Needed to follow up at the start of a new term  and a new set of students

1) Students are unfamiliar with CCES 1.0.3 and I want to run a simple .dxe

2) Tell students to build an "empty" project

3) Add the .dxe into the Debug directory -- see below

4) Click "Debug as"

5) CCES builts the project (all the app.c" default files always added to the project)

6) It then complains "can't find _main" (since there is none there)

7) Finds the "old executable" in the Debug directory and runs the .dxe I wanted to have run by accident

 

Questions

A) Is there a cleaner way (without all the error message) to run an existing .dxe somebody has given you? I know how to click through the error messages -- but I would rather not have the students fdo it

 

These may need to go into another stream to be answered

B) I have always considered that CCES / Eclipse running the old .dxe after a failed build as a potential problem when developing code (and you don't notice).  So is there a CCES option (other than doing a clean) where I can automatically delete the .dxe after a failed build?     Some sort of 'prebuild command' that I can incorporate into the project  

 

C) This is an Eclipse issue -- Used Linker add library option to add a library in another project -- and that library is updated. I have yet to find a method whereby Eclipse notices the dependancy and rebuilds the project.

Is there a "prebuild" command I can incorporate into a project to "touch" a certain file forcing the project to rebuild (and thus include the new library from the other project)

 

Thanks

Mike

 

Image may be NSFW.
Clik here to view.


Viewing all articles
Browse latest Browse all 36216

Trending Articles