cancel
Showing results for 
Search instead for 
Did you mean: 

Changes to .ioc in one project lead to the replacement of the linker file in another.

CTapp.1
Senior II

I am working on a boot loader and have a workspace that contains two projects - one for the boot loader and another for the application that it loads.

As these two programs are tightly coupled, I have a single .ld linker file in the application project. The application and boot loader projects both use this linker file - the application project uses the default settings that were provided when it was created, with the boot loader being manually configured to use the .ld file from the application project.

The default .ld file that was created for the boot loader project has been deleted because it is not needed.

Everything builds and runs correctly, until I modify the .ioc for the boot loader. When the code is regenerated, a new .ld file is created for the boot loader project and the project settings are modified to point at it. At the same time, the content of the .ld for the application project is overwritten with what looks to be a new, default .ld file.

Unfortunately, I am not able to make any files for the projects available, but I could create a similar structure in another workspace if that would be of help?

I am currently using version 1.18.1 under macOS.

 

1 REPLY 1
TDK
Super User

Rename your LD file to something that won't be overwritten.

If you don't want new LD files to stick around after code generation, you can delete them is a post-code generation step. Don't think there's a way to prevent them from being generated at all.

If you feel a post has answered your question, please click "Accept as Solution".