Different Linker Command files per build

I've set up a project with the intention of being able to build it on the TM4C123G or the TM4C129X (probably the TM4C1294 in the future as well)

Most of it was pretty trivial to set up, just excluding device specific files from the other builds.

The part where I'm not so sure is the .ccsproject file.

<?xml version="1.0" encoding="UTF-8" ?>
<?ccsproject version="1.0"?>
<projectOptions>
	<deviceVariant value="Cortex M.TM4C1231H6PM"/>
	<deviceFamily value="TMS470"/>
	<deviceEndianness value="little"/>
	<codegenToolVersion value="5.1.9"/>
	<isElfFormat value="true"/>
	<linkerCommandFile value="project_base_css.cmd"/>
	<rts value="libc.a"/>
	<createSlaveProjects value=""/>
	<templateProperties value="id=com.ti.common.project.core.emptyProjectTemplate,"/>
	<isTargetManual value="false"/>
</projectOptions>

As you can see the device variant says "Cortex M.TM4C1231H6PM" and the linker command file is "project_base_css.cmd".

I actually don't have a "project_base_css.cmd" file, I believe that is leftover from an earlier version of this project. I have two files tm4c123gh6pm.cmd and tm4c129xnczad.cdm, but they need to be used based on the build target.

How much do I have to worry about these .ccsproject file definitions? Are they going to destroy my whole plan? I am able to build and debug the project without the project_base_css.cmd file existing.