Compilation errors with OpenAT 3.1


#1

Hi

I’ve installed the OpenAT SDK on the default locations and set the IDE to VC++ 6.0.

When i compile the rte version, everything works fine, but when I compile the target version it fails.

In VC++ 6.0 when I choose Build-Rebuild All I 3 errors and 6 warnings. If I choose Build HelloWorld I get 1 error and 5 warnings.

The error messages for the different build options is shown below.

Please, please help me out here!!!


Rebuild Al


   Make an archive file for TMT application

zip warning: name not matched: …/out/tmt/e2p_csn.cso
zip error: Nothing to do! (…/out/tmt/zip_tmt.zip)
zip warning: name not matched: …/out/tmt/backtraces.axf
zip error: Nothing to do! (…/out/tmt/zip_tmt.zip)
zip warning: name not matched: …/out/tmt/backtraces64k.axf
zip error: Nothing to do! (…/out/tmt/zip_tmt.zip)
zip warning: name not matched: …/out/tmt/symbolfiles/s64k
zip warning: name not matched: …/out/tmt/symbolfiles/e2p.h
adding: s (176 bytes security) (deflated 68%)

************** and

WARNING : misc_status.log is incomplete. Check manually if any errors exist

************* Resulting in

Libraries available in out directory :
gcc_wmadl_3.3.3.1.0.lib,


End process.

adding: backtraces.axf (deflated 76%)

Hello_World - 3 error(s), 6 warning(s)


Build HelloWorld


Make an archive file for TMT application

zip warning: name not matched: …/out/tmt/e2p_csn.cso
zip error: Nothing to do! (…/out/tmt/zip_tmt.zip)
zip warning: name not matched: …/out/tmt/backtraces64k.axf
zip warning: name not matched: …/out/tmt/symbolfiles/s64k
zip warning: name not matched: …/out/tmt/symbolfiles/e2p.h
adding: backtraces.axf (176 bytes security) (deflated 76%)
enter new zip file comment (end with .):

******************* and

WARNING : misc_status.log is incomplete. Check manually if any errors exist

************************** resulting in


Libraries available in out directory :
gcc_wmadl_3.3.3.1.0.lib,


End process.

updating: backtraces.axf (deflated 76%)

Hello_World - 1 error(s), 5 warning(s)


#2

Hi !
I’ve got the same problem. I don’t use RTE but I know that my samples work even I’ve got error messages.
In fact, I think the compilator does a parsing of all compilation messages and each time it finds the “error” word, it displays an error. So if it finds the “No error” message, it would display “1 error”.
So I think it’s really not a problem, you can run your samples.


#3

Hi Again

I think you’re right, I see that the binaries are regenerated, thanks.

/glennik