• State Not Answered
  • Locked Locked
  • Replies 16 replies
  • Subscribers 22 subscribers
  • Views 7825 views
  • Users 0 members are here
Options
Related
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

Lx51 "Data Type Different" Warnings ?

Andrew E. Kalman

Hello.

I have a project that links to a library I created using the C51 toolset.

If I build it using BL51, everything's cool. If I build it with Lx51, I get warnings like this:

*** WARNING L25: DATA TYPES DIFFERENT
    SYMBOL:  _FnName
    MODULE:  .\main.obj (MAIN)
though the application appears to work just fine in the simulator.

If I build the project with source files only (i.e. I compile the modules that are normally in the library, and I don't link to the library) then everything works under BL51 and Lx51.

So, what can I do to enable me to build projects using Lx51 and my libraries, and avoid these "Data Type Different" Warnings?

Parents
  • 0 in reply to Jon Ward

    "The problem with that is that there may be a lot of places that the variable is used and listing"

    But the message only refers to one particular instance (one module?) - so the Linker should be able to give the details for the particular instance on which it's reporting?

    "each occurance would create a huge list."
    As I've noted many times, a single mistake often leads to a whole raft of messages, so that shouldn't be an undue worry.

    "Maybe engineering can figure out a good way to display it"
    As I've noted before, "big" compilers (eg, Borland, Microsoft) often give better diagnostics than the "small" cross-compilers.
    I'm sure that Borland does give you all the info in its equivalent message.

    "You may use the source browser"

    But if the Link fails, you can't use the Source Browser - because the browse info is only available from a successful build!

Reply
  • 0 in reply to Jon Ward

    "The problem with that is that there may be a lot of places that the variable is used and listing"

    But the message only refers to one particular instance (one module?) - so the Linker should be able to give the details for the particular instance on which it's reporting?

    "each occurance would create a huge list."
    As I've noted many times, a single mistake often leads to a whole raft of messages, so that shouldn't be an undue worry.

    "Maybe engineering can figure out a good way to display it"
    As I've noted before, "big" compilers (eg, Borland, Microsoft) often give better diagnostics than the "small" cross-compilers.
    I'm sure that Borland does give you all the info in its equivalent message.

    "You may use the source browser"

    But if the Link fails, you can't use the Source Browser - because the browse info is only available from a successful build!

Children
No data