OAL error continues!

Source: Internet
Author: User
Today I compiled oal again, but I found that there are still many errors, which are too depressing. It was successful some time ago. This is so uncomfortable. Isn't my previous method wrong, as a result, I started from the beginning again. The previous steps are still the same, but some files (as long as the path and name are not involved) are copied directly, which saves a lot of time to find the code.
There are errors from the initial compilation of common to the compilation of oal (which are all compiled separately), but the errors are always the same, which probably means config. h has a problem, so I compiled it as a whole, and there is a problem I like:
Error-cannot open input file D: \ wince600 \ osdesigns \ osdesign7 \ osdesign7 \ reldir \ micro2440_armv4i_debug \ postproc \ nlscfg. inf
Makeimg: Fatal error: Command returned non-zero exit code 1 (DEC ).
Makeimg: Fatal error: Command returned non-zero exit code 1 (DEC ).
D: \ wince600 \ platform \ micro2440 \ dirs-5 error (s), 0 warning (s)
============ Generate: 0 succeeded or the latest, 1 failed, 0 skipped ============= it is best to solve this error, but after this error is solved? Can it be successful? The ghost knows. Try again!
Click Generate and click Copy files to release directory.
Then, click Generate osdesign 7 to view the result.
Finally, there were eight errors that I was familiar with last time. Hey, I felt that my goal was getting closer. I went to dinner first, and I went on in the afternoon!
I came back in the afternoon and continued to work on it. I only knew the copy, but did not make the corresponding changes. In the morning, I was still saying that I would like to change the path, this afternoon, however, I found that some things have not been changed at all. In fact, it is the oal/oallib/source file, and it is dizzy. At the very bottom, there is such a sentence:
Arm_sources = \
Startup. s
Primary des = \
D: \ wince600 \ platform \ micro2440 \ SRC \ Inc \
Everyone must be careful. First, this sentence should be turned over and easily missed. Second, I only know how to change the drive letter, but I forgot to change the subsequent path.
Continue to compile now. Wait and check the effect. Looking forward...
An error occurs again.
Build: [thrd: sequence: type] Message
Build: [01: 0000000045: errore] D: \ wince600 \ platform \ micro2440 \ SRC \ Inc \ bsp_base_reg_cfg.h (57): Error c2059: syntax error :'--'
It turns out that I typed the ------------------ symbol for convenience when I added the annotation, but did not add the // annotation symbol. The result is incorrectly compiled!
Correct the error and continue compiling! Wait and see...
Dizzy!
22 errors:
Build: [thrd: sequence: type] Message
Build: [01: 0000000043: errore] D: \ wince600 \ platform \ micro2440 \ SRC \ common \ intr \. \ Intr. C (57): Error c2065: 'dpcursetting': Undeclared identifier
Build: [01: 0000000044: errore] D: \ wince600 \ platform \ micro2440 \ SRC \ common \ intr \. \ Intr. C (57): Error c2224: Left '. ulzonemask 'must have struct/Union type
Build: [01: 0000000045: errore] D: \ wince600 \ platform \ micro2440 \ SRC \ common \ intr \. \ Intr. C (57): Error c2224: Left '. ulzonemask 'must have struct/Union type
Build: [01: 0000000046: errore] D: \ wince600 \ platform \ micro2440 \ SRC \ common \ intr \. \ Intr. C (93): Error c2224: Left '. ulzonemask 'must have struct/Union type
Build: [01: 0000000047: errore] D: \ wince600 \ platform \ micro2440 \ SRC \ common \ intr \. \ Intr. C (93): Error c2224: Left '. ulzonemask 'must have struct/Union type
Build: [01: 0000000048: errore] D: \ wince600 \ platform \ micro2440 \ SRC \ common \ intr \. \ Intr. C (114): Error c2224: Left '. ulzonemask 'must have struct/Union type
Build: [01: 0000000049: errore] D: \ wince600 \ platform \ micro2440 \ SRC \ common \ intr \. \ Intr. C (114): Error c2224: Left '. ulzonemask 'must have struct/Union type
Build: [01: 0000000050: errore] D: \ wince600 \ platform \ micro2440 \ SRC \ common \ intr \. \ Intr. C (124): Error c2224: Left '. ulzonemask 'must have struct/Union type
Build: [01: 0000000051: errore] D: \ wince600 \ platform \ micro2440 \ SRC \ common \ intr \. \ Intr. C (124): Error c2224: Left '. ulzonemask 'must have struct/Union type
Build: [01: 0000000052: errore] D: \ wince600 \ platform \ micro2440 \ SRC \ common \ intr \. \ Intr. C (140): Error c2224: Left '. ulzonemask 'must have struct/Union type
Build: [01: 0000000053: errore] D: \ wince600 \ platform \ micro2440 \ SRC \ common \ intr \. \ Intr. C (140): Error c2224: Left '. ulzonemask 'must have struct/Union type
Build: [01: 0000000054: errore] D: \ wince600 \ platform \ micro2440 \ SRC \ common \ intr \. \ Intr. C (173): Error c2224: Left '. ulzonemask 'must have struct/Union type
Build: [01: 0000000055: errore] D: \ wince600 \ platform \ micro2440 \ SRC \ common \ intr \. \ Intr. C (173): Error c2224: Left '. ulzonemask 'must have struct/Union type
Build: [01: 0000000056: errore] D: \ wince600 \ platform \ micro2440 \ SRC \ common \ intr \. \ Intr. C (188): Error c2224: Left '. ulzonemask 'must have struct/Union type
Build: [01: 0000000057: errore] D: \ wince600 \ platform \ micro2440 \ SRC \ common \ intr \. \ Intr. C (188): Error c2224: Left '. ulzonemask 'must have struct/Union type
Build: [01: 0000000058: errore] D: \ wince600 \ platform \ micro2440 \ SRC \ common \ intr \. \ Intr. C (210): Error c2224: Left '. ulzonemask 'must have struct/Union type
Build: [01: 0000000059: errore] D: \ wince600 \ platform \ micro2440 \ SRC \ common \ intr \. \ Intr. C (210): Error c2224: Left '. ulzonemask 'must have struct/Union type
Build: [01: 0000000060: errore] D: \ wince600 \ platform \ micro2440 \ SRC \ common \ intr \. \ Intr. C (224): Error c2224: Left '. ulzonemask 'must have struct/Union type
Build: [01: 0000000061: errore] D: \ wince600 \ platform \ micro2440 \ SRC \ common \ intr \. \ Intr. C (224): Error c2224: Left '. ulzonemask 'must have struct/Union type
Build: [01: 0000000062: errore] D: \ wince600 \ platform \ micro2440 \ SRC \ common \ intr \. \ Intr. C (247): Error c2224: Left '. ulzonemask 'must have struct/Union type
Build: [01: 0000000063: errore] D: \ wince600 \ platform \ micro2440 \ SRC \ common \ intr \. \ Intr. C (247): Error c2224: Left '. ulzonemask 'must have struct/Union type
But we can see where the error occurred. You should modify the content of the Intr. C, debug. C and other files. I'm trying to modify it!
Follow 8: Compile the statement first. The g_oallogmask error may occur. Locate and modify the statement.
1): Modify the Debug. c file
Find the following two sentences in the Void oeminitdebugserial () function:
Logmask = g_oallogmask;
G_oallogmask = 0;
Modify it
Logmask = dpcursettings. ulzonemask;
Dpcursettings. ulzonemask = 0;
Find the sentence at the end of the void oeminitdebugserial () function.
G_oallogmask = logmask;
Modify it
Dpcursettings. ulzonemask = logmask;
2): Modify the oal_log.h File
Find the # define oalzone (N) (g_oallogmask & (1 <n) Statement
Modify it to the following two sentences:
Extern dbgparam dpcursettings;
# Define oalzone (N) (dpcursettings. ulzonemask & (1 <n ))
Locate extern uint32 g_oallogmask; comment it out
Modify, re-compile, three errors:
Build: [thrd: sequence: type] Message
Build: [01: 0000000164: errore] D: \ wince600 \ platform \ micro2440 \ SRC \ kitl \ DMA \. \ kitldma. C (620): Error c2039: 'screensignature ': is not a member of 'bsp _ ARGs'
Build: [01: 0000000166: errore] D: \ wince600 \ platform \ micro2440 \ SRC \ kitl \ DMA \. \ kitldma. C (620): Error c2065: 'bsp _ screen_signature ': Undeclared identifier
From the error, we can see that it is related to kitl. The reason is very simple: No kitl-related code is blocked. Now we start to block kitl-related code. Enable kitl (no imgkitl = 1) option in the property, and then re-compile.
I finally succeeded, wasting my half a day!
Ah, it's not easy to love you in ce6.0!

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.