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

No rule to make target AND option --include_path is missing its parameter 'dir'

robert palma
Prodigy 240 points
Other Parts Discussed in Thread: TM4C123GH6PM

I am getting 3 errors trying to compile TM4C Lab 5 using CCS 6.1:

1.
Description    Resource    Path    Location    Type
gmake: *** No rule to make target `C:/TI/ccsv6/ccsv6/eclipse/TIVAWARE_INSTALL/driverlib/ccs/Debug/driverlib.lib', needed by `lab5.out'.    lab5        Unknown    C/C++ Problem

2.
Description    Resource    Path    Location    Type
option --include_path is missing its parameter 'dir'    main.c    /lab5         C/C++ Problem

3.
Description    Resource    Path    Location    Type
option --include_path is missing its parameter 'dir'    tm4c123gh6pm_startup_ccs.c    /lab5         C/C++ Problem


Previously I could not run LAb 4 and ArtiG suggested that I install CCS 6.1.
I did that and after some more varible defines I finally got it to compile.

Now I am getting different errors using CCS 6.1 to compile Lab5.

I have been working on this for a day and read a number of Wiki and Forum posts, but they all are oriented to a different scenario of compiling or a different processor and I am not making any progress.


I have variables set:
CG_TOOL_ROOT
TIVAWARE_INSTALL

The Project Includes has:
C:\TI\ccsv6\ccsv6\tools\compiler\ti-cgt-arm_5.2.5\include
C:\TI\TivaWare_C_Series-1.1


Any help is much appreciated.

Thank-you,
Rob



  • 0
    TI__Guru**** 173310 points

    Have you been able to resolve these errors? Based on your other post, my understanding is that you have resolved all errors except that one warning discussed in the other post. Let us know if that is not the case and if these errors still remain.

  • 0 in reply to AartiG
    Prodigy 240 points
    Hi AartiG,

    Thank-you for response.

    The previous post was for Lab 4 and that was resolved.

    This is Lab 5 with new errors.

    ===== Further Information on 2 of the 3 errors ( the include_path errors )

    I have located the Build Log file and in both the building of the Main.c and tm4c123gh6pm_startup_ccs.c,
    there are 2, --include_path call outs in the command line.

    In BOTH cases the second call out, I have no entry.
    This is the complaint from the compiler.

    This, I believe is the cause of 2 of the 3 errors I am receiving

    So some how I am telling the compiler to look for 2 includes but somehow I am not specifying what that include is ???

    this is my confusion on 2 of the 3 errors.


    --- begin snip

    **** Build of configuration Debug for project lab5 ****

    "C:\\TI\\ccsv6\\ccsv6\\utils\\bin\\gmake" -k all
    'Building file: ../main.c'
    'Invoking: ARM Compiler'
    "C:/TI/ccsv6/ccsv6/tools/compiler/ti-cgt-arm_5.2.5/bin/armcl" -mv7M4 --code_state=16 --float_support=FPv4SPD16 --abi=eabi -me --include_path="C:/TI/ccsv6/ccsv6/tools/compiler/ti-cgt-arm_5.2.5/include" --include_path= -g --define=PART_TM4C123GH6PM --display_error_number --diag_warning=225 --diag_wrap=off --preproc_with_compile --preproc_dependency="main.pp" "../main.c"
    error: option --include_path is missing its parameter 'dir'
    gmake: *** [main.obj] Error 1
    'Building file: ../tm4c123gh6pm_startup_ccs.c'
    'Invoking: ARM Compiler'
    "C:/TI/ccsv6/ccsv6/tools/compiler/ti-cgt-arm_5.2.5/bin/armcl" -mv7M4 --code_state=16 --float_support=FPv4SPD16 --abi=eabi -me --include_path="C:/TI/ccsv6/ccsv6/tools/compiler/ti-cgt-arm_5.2.5/include" --include_path= -g --define=PART_TM4C123GH6PM --display_error_number --diag_warning=225 --diag_wrap=off --preproc_with_compile --preproc_dependency="tm4c123gh6pm_startup_ccs.pp" "../tm4c123gh6pm_startup_ccs.c"
    error: option --include_path is missing its parameter 'dir'
    gmake: *** [tm4c123gh6pm_startup_ccs.obj] Error 1
    gmake: *** No rule to make target `C:/TI/ccsv6/ccsv6/eclipse/TIVAWARE_INSTALL/driverlib/ccs/Debug/driverlib.lib', needed by `lab5.out'.
    gmake: Target `all' not remade because of errors.

    **** Build Finished ****

    --- end snip



    With regard to the error: gmake: *** No rule to make target

    I have not made any discoveries of what I am doing wrong here .......

    All the best and thank-you for your time and attention,
    Rob
  • 0 in reply to robert palma
    TI__Guru**** 173310 points

    robert palma said:
    error: option --include_path is missing its parameter 'dir'

    Please see http://processors.wiki.ti.com/index.php/Build_Errors_in_CCS#Error:_option_--include_path_is_missing_its_parameter_.27dir.27

    Most likely you have a variable specified in the include path and the variable is either not defined or does not resolve correctly to a proper path.

    robert palma said:
    gmake: *** No rule to make target `C:/TI/ccsv6/ccsv6/eclipse/TIVAWARE_INSTALL/driverlib/ccs/Debug/driverlib.lib', needed by `lab5.out'. 

    As for the gmake error, it appears that lab5 project is dependent on driverlib project and requires the driverlib project to build successfully and generate driverlib.lib before lab5.out can be built. I am not familiar with where these lab projects are coming from or how they have been set up, but if there is a User's Guide or documentation that accompanies those projects I would suggest looking at them for guidelines. It is also possible that these projects are slightly out of date and may require some tweaking to work with latest CCS and TivaWare. I would suggest starting with examples from TivaWare instead to help get started with Tiva devices.

  • 0 in reply to AartiG
    Prodigy 230 points

    Not sure this will apply to this or any other case, but:

    Running CCS 6.2 targetting the MSP432 I ran into the same message.  Digging a bit and comparing to a working chunk of Driverlib dependent code i discovered that the example code "linked resources" [in the project properties] was pointing at a common (for all code)  Driverlib directory that did not exist. I deleted the entry and it then used the Driverlib directory that was part of my source tree.  It now compiles cleanly and I'm in the process of detailed verification of function. It seems to work, but I'm now making sure.

    It's certainly more efficient to use the common Driverlib code and object files, but I'd rather not risk and update that breaks things.  I realize this is also risking missing Driverlib updates.