- Ask a related questionWhat is a related question?A related question is a question created from another question. When the related question is created, it will be automatically linked to the original question.
I found out that when a linker command file (.cmd) is located inside a linked folder of the project, with the actual folder located outside the project root, then this linker command file is not passed to the linker as a command line argument. The linker command file is NOT excluded from build but still it does not appear in the linker command line shown in the build console. Copying the file somewhere inside the actual project root folder solves the issue.
I have not found this being mentioned anywhere and I beleive it is quite confusing, since source files (.c) are automatically included in the build, so ont would expect that .cmd are taken into account too.
I observed this using CCS v6, compiling a project for MSP430F5528 using compiler V4.3.7
Giannis
Giannis Roussos said:I found out that when a linker command file (.cmd) is located inside a linked folder of the project, with the actual folder located outside the project root, then this linker command file is not passed to the linker as a command line argument.
I have not been able to reproduce this with CCS 6.0.1 or 6.1.0. Attached below is a screenshot of an example project with a linked folder named cmd, that is outside the project folder. You can tell from the special icon that it is a linked folder. The build log shows the linker command file being passed as an argument to the linker.
How did you create your linked folder? Are there other files within that same linked folder that are picked up in the build, while the .cmd is not?
