TMS320F280049C: How the file subdir_rules.mk is auto-generated in CCS v12?

Hello,

All the contents of the makefiles (including associated *.mk file) are generated from the CCS project being built. Hence there must be something in your project that references those old paths. Please carefully check the project settings. If you are unable to find the paths, please attach the three .*project metadata files and also the subdir_rules.mk file.

Thanks

ki

Thanks Ki. I think so but just couldn't find where it is. And I feel weird that there is anywhere to refer to the old path for just a particular folder in a project.

But anyway, I am trying to upload the .*project files, but it seems not allowing when I click "insert" -> "Image/Video/File" and then click "Upload" to select the .*project file and .mk file. By the way, I tried .txt file just for a try, it worked. Can you advise how to upload those files? 

I would just zip up the three files and then drag and drop the zip file to the reply edit field

Ok great. Zip file works.

Please see the three .*project file and the .mk file with the old path to the project and C2000Ware.

subdir_rules.zip

Thank you. 

What are some of the "old" paths mentioned in the mk file?

All the include paths in the .mk file are the old path. Only exist in the .mk file in this folder. For other folders, these paths are updated with the new ones. This attached is the new one.7875.subdir_rules.zip

One thing I noticed about the project is that it is configured to use C2000Ware 4.0.0.

Which explains the paths in the frst mk file pointing to: 

I am using 4.1.0 and this attached first picture shows what's in the property.

And I checked the build variables as in the second picture, it's already the new ones.

And in the include options in the third picture, the path for the folder with wrong .mk file ControllerAPI is same as the other folders. But its .mk file is different from others. 

The first screenshot indicates that the project is configured for C2000Ware 4.0.0 and SysConfig 1.11.0 but it could not find those versions on your system so it will use the closest match it can find - which is C2000Waee 4.1.0 and SysConfig 1.13.0. So your project should indeed be using those versions and you build. yes your build variables are also pointing to paths that do not match when is in the old mk file.

Can you start again from a clean environment? What I mean is to delete ALL configuration subfolders for the project ("CPU_RAM", etc). Then restart CCS using a clean new workspace folder. Import the project to the new workspace and build it. It will regenerate the configuration subfolders and the makefiles. See if that helps at all. If not, please copy&paste all the build messages in the build console to a text file and attach the file to this thread.

Thanks

ki

Ok thanks! Beside the subfolder of "CPU1_FLASH" and "CPU1_RAM", is there anything else I can or need delete?

I deleted all folders, downloaded the source file again, opened a new workspace in CCS to open the project, set up all the environment variables and include paths, etc, in properties, and built again. Got the same result. Please see the attached build messages coped from the build console. Thanks!build message.txt

It looks like the actual build is using all the correct paths base don the build messages, correct? Just the mk file has the old paths.

Just the .mk file in only one folder "ControllerAPI". For all other folders, the .mk files have the new paths.

Crane Shao said:

Just the .mk file in only one folder "ControllerAPI"

Note that the makefiles are generated in the active build configuration subfolder like "CPU_FLASH1". I assumed that the mk file you sent me was from there. if not, then what is the "ControllerAPI" folder? Is the timestamp for the mk file from there old?

Yes, it is from the subfolder CPU1_FLASH. All .mk files are from the subfolders in that folder CPU1_FLASH.

Crane Shao said:

Yes, it is from the subfolder CPU1_FLASH. All .mk files are from the subfolders in that folder CPU1_FLASH.

Ok, so "ControllerAPI" is a subfolder inside CPU1_FLASH?

Can you should be a screenshot of your project exploer with CPU1_FLASH and ControllerAPI folders expanded?

Here it is.

Ok, I get it now. The source folder in the project would generate their own subfolder in the build configuration subfolder with their own make files.

The 'ControllerAPI' source folder also has its own folder specific build options. And looking back at your build messages, I can see that TController.cpp was build with the old paths as specified in the old mk file. I missed that initially.

Please check the folder specific build options for 'ControllerAPI' and see if the paths for just that folder are the old paths.

Ok great. 

But I found that the same string to set a relative path doesn't work for this folder. I have to set another string to make the relative path work. I will dig into it. 

When looking at your .cproject file, I see the following options for the ControllerAPI folder:

Ok. I am wondering why it is different from other folders.

In addition, if I deleted one of the project folders, the changes will apply all other folders except ControllerAPI. 

And if you look at the project explorer in the attached screenshot, there is small difference on the icon to the left.

Crane Shao said:

And if you look at the project explorer in the attached screenshot, there is small difference on the icon to the left.

Yes as I mentioned in an earlier post:

Ki said:

The 'ControllerAPI' source folder also has its own folder specific build options. And looking back at your build messages, I can see that TController.cpp was build with the old paths as specified in the old mk file. I missed that initially.

Please check the folder specific build options for 'ControllerAPI' and see if the paths for just that folder are the old paths.

https://software-dl.ti.com/ccs/esd/documents/users_guide/ccs_project-management.html#file-specific-options

Yes, already checked and they are old paths and it is already addressed (warning disappeared. Thank you!

Right now I am just wondering why it's different from all other folders.