• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 2448 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS 3.3 to v4 migration: target pattern contains no `% error

Robert Finger
Genius 17587 points
Other Parts Discussed in Thread: OMAP-L138

Team,

I tried to import the audio example from the C6747 PSP installation into CCSv4. No errors occured during import, but when I try to compile I get the following error:

**** Build of configuration Debug for project audioSample ****

C:\Program Files\Texas Instruments\ccsv4\utils\gmake\gmake -k all
subdir.mk:76: *** target pattern contains no `%'.  Stop.
Build complete for project audioSample

What could be the reason? I did a pjt clean and selected the C674x as Device Variant in the Build settings. Anything else missing?

Thanks,
  Robert

EDIT: I've seen that someone on the external forum has the same problem: http://e2e.ti.com/support/development_tools/f/81/t/33200.aspx

  • 0
    TI__Mastermind 18130 points

    Robert,

    I saw the same problem with the OMAP-L138 BSL examples. The problem is essentially that the conversion wizard creates bad search paths.

    I attempted to rebuild the test_audio example that comes with the Logic PD OMAP-L138 BSL in CCSv4.1, but when I rebuild I get the following error:

    **** Build of configuration Debug for project test_audio ****

    C:\Program Files (x86)\Texas Instruments\ccsv4\utils\gmake\gmake -k all subdir.mk:35: *** target pattern contains no '%'. Stop. Build complete for project test_audio

    How do I fix this?

    Environment: CCSv4.1, CGTools v6.1.12, OMAP-L138 BSL 1014013A (dated Aug. 21, 2009)


    Steps to fix: The conversion wizard is creating bad paths for the .obj, .out and .map files as well as two bad header include paths. To fix this follow the following steps:

    • Open the Project Properties (right click the project, select Properties)
    • Navigate to Basic Settings->C6000 Compiler->Directory Specifier and make sure the mode is automatic (or specify a valid object file directory)
    • Under Include Options update the last two directories to point to the actual location of the project's include folder and the BSL include folder
    • Navigate to Basic Settings->C6000 Linker->Basic Options and specify a valid output file name (probably project_name.out) and map file name (project_name.map)

    At this point you should not get the strange gmake errors, but you will still get a linker error. To correct the linker error open the linker_dsp.cmd file and update the relative path to the BSL file to an absolute path. You should now be able to completely build the project successfully.

    With that said, I have filed a bug SDSCM00034965 against the conversion wizard.