• State Resolved
  • Locked Locked
  • Replies 10 replies
  • Subscribers 52 subscribers
  • Views 498 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Original question:

CCS/TM4C129CNCPDT: CCSv8.2 and "Exclude from Build" no longer works

CCS/TM4C129CNCPDT: CCSv8.2 and "Exclude from Build" no longer works, CCSv9 has not fixed it

Kaveh Vaghefi
Expert 1704 points
Part Number: TM4C129CNCPDT

Tool/software: Code Composer Studio

I tried to respond to the topic where this was originally posted, but it's been inexplicably locked.  I just downloaded CCSv9 to try the fix and sadly it doesn't work as it seems another bug has been introduced.

If I select the "strict_manual" option, I run into the same issue as before. If I select the "assisted_manual" option, then I run into an issue where I have a cc file called `${PROJ_LOC}/base/status.cc` that gets compiled properly but placed in the root of the output directory instead of `${OUTPUT_DIR}/base/status.obj`.  The linker subsequently says "cannot file file `${OUTPUT_DIR}/base/status.obj`" because MAKE/compiler put it in `${OUTPUT_DIR}`.

Can you guys just revert the change that broke this in 8.2?

  • 0
    Expert 1704 points
    A little more info...this source file `base/status.cc` is a linked resource defined in the .project file. I wonder if this is why we run into this issue.
  • 0 in reply to Kaveh Vaghefi
    TI__Guru**** 173310 points
    Kaveh,

    I will take a look at this and get back to you, hopefully tomorrow.
  • 0 in reply to Kaveh Vaghefi
    TI__Guru**** 173310 points
    Kaveh,

    If you could attach a test case that would be very helpful. Otherwise, could you attach the build logs for both the "strict_manual" and "assisted_manual" options for us to review please? Thanks.
  • 0 in reply to AartiG
    Expert 1704 points

    For the `strict_manual` case the failure mode is exactly the same as before (you can use the .project and .cproject file I had previously sent).  I managed to get it working under `assisted_manual`, but only after removing the surrounding quotes I had for the paths I had specified and removing the unnecessarily linked resource for `base/status.cc` we had in our .project file.  It seems like in your implementation of a new `assisted_manual` mode, you might've not tested the cases where:

    • The path specified in that dialog is surrounded by quotes OR
    • There is a linked resource that happens to be able to be referenced in the project.

    Do you still need me to try and supply you with a failure log or do you think you can use this info to recreate these one or two issues?

  • 0 in reply to Kaveh Vaghefi
    TI__Guru**** 173310 points

    Kaveh Vaghefi said:
    For the `strict_manual` case the failure mode is exactly the same as before (you can use the .project and .cproject file I had previously sent). 

    The strict manual mode in CCS 9.0 works the same way as the manual mode in previous versions, so the failure in this case is expected. The solution for your use-case is the addition of the assisted manual option.

    Kaveh Vaghefi said:
    The path specified in that dialog is surrounded by quotes

    It is the --obj_directory option that has the path surrounded by quotes, correct? If so, yes I can recreate the error for that case.

    Kaveh Vaghefi said:
    There is a linked resource that happens to be able to be referenced in the project

    Could you provide an example or more details to recreate this? What is the error generated due to this?

  • 0 in reply to AartiG
    Expert 1704 points

    AartiG said:
    It is the --obj_directory option that has the path surrounded by quotes, correct? If so, yes I can recreate the error for that case.

    Yes

    AartiG said:

    Could you provide an example or more details to recreate this? What is the error generated due to this?

    Add a linked resource that is also under the project's path.  This is a weird use case, but that's how I originally ran into this issue.
  • 0 in reply to Kaveh Vaghefi
    TI__Guru**** 173310 points

    Do you mean like this? 

    main.cc is "added" to the project's root directory. And there is another main.cc that is "linked" inside a sub-directory of the root project directory. 

    I don't get an error with this set up. Could you clarify how yours is different?

  • 0 in reply to AartiG
    Expert 1704 points
    It would be more like this:
    - Make a project
    - Make a directory within that project called foo
    - Make a file in that project called bar.cc
    - Add a linked resource to the root of the project `bar.cc` that links from `foo/bar.cc`
  • 0 in reply to Kaveh Vaghefi
    TI__Guru**** 173310 points

    I have filed these for tracking.

    Kaveh Vaghefi said:
    The path specified in that dialog is surrounded by quotes

    CCSIDE-3528

    Kaveh Vaghefi said:
    There is a linked resource that happens to be able to be referenced in the project.

    CCSIDE-3529


    Thank you for bringing these to our attention.

  • 0 in reply to AartiG
    Expert 1704 points

    Thanks, to be clear this is no longer a showstopper as I'm able to get things working in CCSv9, but I'm glad to see bugs file to make it more robust.