I've reposted this since my previous attempt to get an answer has been locked.
Unfortunately, it took me a while to cycle back around to dealing with this issue, so I did not respond in a timely manner.
Here's the question I posed, which included references to several non-answers that I had already investigated.
This question has been asked a few times, but never given a satisfactory answer.
What steps are required to use the CMSIS DSP library with the CY8CPROTO-062-4343W board, using Eclipse/ModusToolbox v2.x on Windows?
This discussion assumes ModusToolbox 1.x and depends on facilities not available in MT 2.x.
This discussion follows much of the same path as I did, but ends without a resolution.
This discussion never got an answer.
The first response asked if I had tried #2, above, which I had already indicated I had tried. Following those instructions results in an error.
The second response simply repeated the instructions from #2. Not surprisingly, the result was the same.
So back to square one.
The instructions given in #2 above result in exactly the problem reported in #2 above. That is,
CMSIS_5/CMSIS/DSP/DSP_Lib_TestSuite/Common/platform/startup_generic.S:62:6: error: #error "No appropriate startup file found!"
Because the instructions included some vague and undefined terms, I had to make a few assumptions, so I may not have set things up correctly.
In particular, the instruction, "Extract it and place it one level below the application directory," is problematic.
I assumed that "it" referred to the top-level directory of the extracted .ZIP file, CMSIS_5.
I assumed that the "application directory" referred to the workspace directory, since Eclipse has no concept of an "application" directory.
I assumed that "one level below," actually meant to place the folder in the workspace directory, since placing it one level below would require creating an intermediate directory, and no name was mentioned for such a directory.
Also, the suggestion that placing the files "one level below" would somehow shield them from the auto-discovery process conflicts with my experience. I have found that auto-discovery finds everything below the workspace directory, at any level. This is borne out by the auto-discovery report in the console output, which shows a very large number of files found:
Auto-discovery in progress...
-> Found 1486 .c file(s)
-> Found 79 .S file(s)
-> Found 109 .s file(s)
-> Found 132 .cpp file(s)
-> Found 0 .o file(s)
-> Found 0 .a file(s)
-> Found 1361 .h file(s)
-> Found 0 .hpp file(s)
-> Found 0 resource file(s)
At any rate, the question remains unanswered and unchanged: how do I use the CMSIS library with ModusToolbox 2.x?
Auto-discovery in progress...-> Found 1486 .c file(s)-> Found 79 .S file(s)-> Found 109 .s file(s)-> Found 132 .cpp file(s)-> Found 0 .o file(s)-> Found 0 .a file(s)-> Found 1361 .h file(s)-> Found 0 .hpp file(s)-> Found 0 resource file(s)Applying filters...Auto-discovery complete