This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

A warning suddenly becomes an error !?

Hi,

I'm working on a big project with a lott of sources files.
At compilation time I have a lot of #167-D warning
( warning: #167-D: argument of type "U8 *" is incompatible with parameter of type "const char *" for example ) .

Today I move some functions to another new source file to clean my code.
But when I compile , I get new errors in my new source file :
"error: #167: argument of type "U32 *" is incompatible with parameter of type "U8 *"

The warning in a source file becomes an error in another source file !!!

I didn't setup anything different for this source file , all compilation options are defined by the project.

What is the problem and how to solve it please ?

Parents
  • You have to figure out why the variable was of type U8 if the function - or if it was the function call - was located in one file, and of type U32 when you moved the code to another file.

    Somehow, you may have two header files that specifies different data types, or you have one header file specifying one data type, and a source file defining another data type.

Reply
  • You have to figure out why the variable was of type U8 if the function - or if it was the function call - was located in one file, and of type U32 when you moved the code to another file.

    Somehow, you may have two header files that specifies different data types, or you have one header file specifying one data type, and a source file defining another data type.

Children
No data