Why the ldf is always regenerated every time I open CCES

Hi,

When importing a previous version of CCES project to new version of CCES, Changing Tools Settings and/or Startup Code/LDF configuration UI options will have the effect of re-generating the Startup Code/LDF source files in your project which may lead to create the file wrongly.

so please try importing a project without modifying LDF by selecting "No" when the dialog appears asking to regenerated the LDF.

Also if you open or import a project and the Startup Code/LDF schema number(s) found in the project's system.svc configuration differ from the schema number(s) specified in the underlying XML templates (e.g. System\SourceGenerators\LDFGen\SHARC), then the Startup Code/LDF Add-in will re-generate its source file(s).

This ensures that you're using the latest Startup Code and LDF updates - new memory segments or output sections may have been added or removed, or a hardware anomaly workaround applied to the generated source file(s).

When the source file(s) are re-generated, you will see an Informational message in the Problems View.

The updated schema number is stored in the system.svc and the next time you open or import your project, the Startup Code/LDF Add-in knows that it does not need to re-generate its source file(s)

Another time when the Startup Code/LDF Add-in will re-generate its source file(s) is after you change a project Tools Setting that requires an update to an LDF (e.g. -eh -rtti).
The Startup Code/LDF Add-in will detect the Tools Setting change and re-generate its source file(s).

And lastly, if you modify the Startup Code/LDF configuration and click Save, just as you would do for the other Add-ins

Is it that you're trying to use a custom LDF at Link time? If so There is an entry box in Tools Settings: Linker: General called "Custom LDF (-T)". You can use it to specify a customized LDF.

Regards,
Kader

Hi,

When importing a previous version of CCES project to new version of CCES, Changing Tools Settings and/or Startup Code/LDF configuration UI options will have the effect of re-generating the Startup Code/LDF source files in your project which may lead to create the file wrongly.

so please try importing a project without modifying LDF by selecting "No" when the dialog appears asking to regenerated the LDF.

Also if you open or import a project and the Startup Code/LDF schema number(s) found in the project's system.svc configuration differ from the schema number(s) specified in the underlying XML templates (e.g. System\SourceGenerators\LDFGen\SHARC), then the Startup Code/LDF Add-in will re-generate its source file(s).

This ensures that you're using the latest Startup Code and LDF updates - new memory segments or output sections may have been added or removed, or a hardware anomaly workaround applied to the generated source file(s).

When the source file(s) are re-generated, you will see an Informational message in the Problems View.

The updated schema number is stored in the system.svc and the next time you open or import your project, the Startup Code/LDF Add-in knows that it does not need to re-generate its source file(s)

Another time when the Startup Code/LDF Add-in will re-generate its source file(s) is after you change a project Tools Setting that requires an update to an LDF (e.g. -eh -rtti).
The Startup Code/LDF Add-in will detect the Tools Setting change and re-generate its source file(s).

And lastly, if you modify the Startup Code/LDF configuration and click Save, just as you would do for the other Add-ins

Is it that you're trying to use a custom LDF at Link time? If so There is an entry box in Tools Settings: Linker: General called "Custom LDF (-T)". You can use it to specify a customized LDF.

Regards,
Kader