Problem "cannot display source" with source file in linking

[radekkreczewski]

Hello

When I link a project I got a warning:

"

>Source file

>"D:\workspace\ColdFire\ColdFire_Build_Tools\ewl\EWL_Runtime\Runtime_ColdFire\S

>ource\CF_StaticInitializers.c" not found, cannot display source

>Source file

>"D:\workspace\ColdFire\ColdFire_Build_Tools\ewl\EWL_Runtime\Runtime_ColdFire\S

>ource\CF_StaticInitializers.c" not found, cannot display source

"

I couldn't find any settings where the "D:\workspace" path is.

Does anybody know how to fix it?

Best Regards

Radek

[PedroBecerra]

I had the same problem when I changed the Code Model from Near to Smart.

Then I rebuilded the library it sayed couldn't find and every thing goes fine again.

So if you change anything on your tool setting, problably you should build that new library.

One funny thing is I was working with Codewarrior 10.6 but I should use codewarrior 6.3 to build the library.

[ZhangJennie]

HI,

this is a very old thread which was created almost 4 years ago. Can you please create a new thread with your demo code?

thanks!

Best Regards,

Jennie Zhang

[CrasyCat]

Hello

Just to make sure I understand the problem you are facing.

Are you getting this message when building the application or when to attempt to debug the application?

CrasyCat

[radekkreczewski]

Hi CrasyCat

I'm getting this message when I'm linking project, so there is no matter if I am building or debugging.

Radek

[CrasyCat]

Hello

The path you are seeing is the path to the source file on the Host where the library has been built.

That is strange. Normally the linker does not require to access any source code.

I did some tests with CodeWarrior for MCU V10.2 and I am able to link out of the box without any problem.

There seem to be something related to your project.

Only thing I can think about is perhaps you can try to rebuild the runtime library and make sure they are built with debug information.

This can be done as follows:

• Import project located in {Install}\MCU\ColdFire_Support\ewl in CodeWarrior
• Click right on the project name then select Build Configuration > Set Active and select the appropriate configuration. This depend on the run time library file you are linking with your application.
• Build the project to create a new .a file. All the debug information will then point to your current installation directory and you should be able to link your application

If this does not help, I would recommend you to submit a service Request from our on-line support web page. So a support engineer can look at what is going wrong. Make sure to attach a project reproducing the trouble to the SR.

Click here to submit a Service Request.

CrasyCat