• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Subscribers 54 subscribers
  • Views 6295 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.

Include_path is misssing its parameter 'dir'

Trey German289
Mastermind 22025 points
Other Parts Discussed in Thread: CONTROLSUITE

CCS Guru's,

I know you have seen this before, and I've searched and read the other posts pertaining to this topic, but have not been able to find a solution.  I had some CCSv4 projects that imported into 5 and they stopped working.  I've checked the include paths and macros and everything looks good to me.  I updated my CCS (to 5.1.1) and codegen tools, but that didn't help either.  Any ideas why these macros wouldn't resolve?  All the source files are linked in with these macros and they work.

See below for the pertinent information:

Snippet from the build log (every file has this same error)

'Building file: C:/controlsuite_gitorious_dev/device_support/f2802x/version/f2802x_common/source/spi.c'
'Invoking: C2000 Compiler'
"C:/TI/ccsv5/tools/compiler/c2000/bin/cl2000" -v28 -ml -mt -O0 -g --include_path="C:/TI/ccsv5/tools/compiler/c2000/include" --include_path="" --define=_DEBUG --diag_warning=225 --gen_func_subsections=on --preproc_with_compile --preproc_dependency="spi.pp"  "C:/controlsuite_gitorious_dev/device_support/f2802x/version/f2802x_common/source/spi.c"
error: option --include_path is missing its parameter 'dir'
gmake: *** [spi.obj] Error 1

Include Paths:

Path Variables:

Regards,

Trey

  • 0
    TI__Mastermind 22025 points

    I see 5.2 just went live... I'll try that while I'm waiting for a response :)

    Trey

  • 0
    TI__Guru*** 130875 points

    Hi Trey,

    The problem is that you have defined a path variable using another path variable.  This is not supported.  Try changing the INSTALL_ROOT_... path variable in your screenshot to use an absolute path.

    Keep us informed.

    Best Regards,

    LIsa

  • 0 in reply to Lisa TI
    TI__Mastermind 22025 points

    Hi Lisa,

    Thanks for the quick response.  I feel like this functionality should work for two reasons:

    a) the Path Variables Dialog clearly states that "Path variables specify locations in the file system, including other path variables with the syntax '${VAR}'..."

    Am I misinterpreting this statement?

    b) this was a working CCSv4 project that broke when imported into CCSv5.  CCSv5 created the macro referencing a macro not I.  If this is not an acceptable use of macros, why is CCS doing this?

    Regards,
    Trey

  • 0 in reply to Trey German289
    TI__Guru*** 130875 points

    Hi Trey,

    ok, my humblest appologies.   I have confirmed we actually do now support this with v5 and I just tried it myself.

    Could you still please confirm that things work if you put an absoute path there?

    I amost looks like the import wizard created a broken or partial path there ...

    Best Regards,

    Lisa

  • 0
    TI__Guru* 84285 points

    Trey German said:
    --include_path=""

    I suspect this is your problem.  I don't see where the empty path came from in that dialog.

  • 0
    TI__Guru**** 173310 points

    Trey German said:
    error: option --include_path is missing its parameter 'dir'

    Trey,

    I have seen this error appear when a macro is not resolved properly so you are on the right track here. However, I see in your screenshot that you checked the macro under "Path Variables", but where you also need to check is under Project Properties->C/C++ Build->Build Variables. Do you see the INSTALLROOT_F2802x_VERSION macro properly resolved under "Build Variables"? If not, try setting it/adjusting it there and see if that helps.

    I agree that the import tool should have handled this properly and when reading the macros.ini file should have set this macro correctly in 2 places - under "Path Variables" and under "Build Variables". If it is not doing so, it could be a bug.

    If this exhibits the same behavior with CCS 5.2 as well it would be helpful if you could share the project so we can determine if there is a bug here.

  • 0 in reply to AartiG
    TI__Mastermind 22025 points

    Aarti,

    Alright, I think I've got it figured out now.  When I originally imported these into 5 I was using 5.0.9 and the Path variable was set, but the build variable was not.  Upgrading versions didn't help because the project was already a CCSv5 project so CCS didn't mess with any of the settings.  I rolled back the examples in git to when they were still v4 and re-imported in 5.2 and everything worked fine.  Sorry for the false alarm and thanks for the quick support!


    Regards,

    Trey

  • 0 in reply to AartiG
    Intellectual 805 points

    I am also getting the following error message

    error: option --include_path is missing its parameter 'dir'

    I tried checking path variables against build variables listed under Project Properties->Build->MSP430 Compiler (I can't find Project Properties->C/C++ Build on CCS v5.2), and sure enough, one of the build variables is given as "".  I'd like to change this to the correct path, but I can't do it in the flag summary window.  Any ideas on how to change build variables?

  • 0 in reply to Jimbo
    TI__Guru*** 130875 points

    Hi,

    have you seen this wiki:

    http://processors.wiki.ti.com/index.php/Include_paths_and_options

    Best Regards,
    Lisa