**** Build of configuration Debug for project CSL_GPIO_OutputPinExample ****
C:\TI\ccsv4\utils\gmake\gmake -k all
'Building target: CSL_GPIO_OutputPinExample.out'
'Invoking: Linker'
"C:/TI/ccsv4/tools/compiler/C5500 Code Generation Tools 4.3.9/bin/cl55" -v5505 -g --define="_DEBUG" --diag_warning=225 --large_memory_model --algebraic --asm_source=algebraic -z -m"CSL_GPIO_OutputPinExample.map" --verbose_diagnostics --warn_sections -i"C:/TI/ccsv4/tools/compiler/C5500 Code Generation Tools 4.3.9/lib" -i"C:/TI/ccsv4/tools/compiler/C5500 Code Generation Tools 4.3.9/include" -i"C:/TI/bios_5_41_10_36/packages/ti/rtdx/lib/c5500" -i"C:/TI/bios_5_41_10_36/packages/ti/bios/lib" -i"C:/ee410/C5505_CSL_Rel_1.1_CCS40/VC5505_CSL/cslVC5505" -i"C:/Program Files (x86)/C55 Low Power Chip Support Library v2.50.00/c55xx_csl/ccs_v4.0_examples/gpio/CSL_GPIO_OutputPinExample" -i"/lib" --priority --reread_libs --rom_model -o "CSL_GPIO_OutputPinExample.out" "./gpio_Output_Pin_Example.obj" -l"" -l"Debug/cslVC5505.lib" -l"rts55x.lib" -l"rts55h.lib" "../VC5505.cmd" "../cslVC5505_Lib.lib"
<Linking>
error: cannot find file "-lDebug/cslVC5505.lib"
fatal error: file "../cslVC5505_Lib.lib<csl_gpio.obj>" specifies "C55x CPU Rev
2.x", which is not compatible with "C55x CPU Rev 3.x" specified in a
previous file or on the command line
This right here, and every error remotely like it are the bane of my existence. EVERY time I try to build an example project, I run into this. I understand that it must be that the linker is grabbing libraries from different places in the build space, and that I have to find the projects which build the libraries, rebuild the libraries, export them to the target project, and try again. Problem is that about 70% of the time, that does not work at all. This is further complicated by the fact that the output from the linker does not give me the full path to the libraries it is trying to link, and in an environment where there are at least 2 versions of every library running around, this is very frustrating. I am hoping someone out there has also run into this problem and can give me a strategy for eliminating these errors in less than an hour every time I run into one.
