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.

Project build error for imported project from Resource Explorer

Guru 56198 points

Getting the similar Fatal Error 6001 during linking:

<Linking> fatal error #6001: cannot open file "C:/CCSV7/ccsv7/tools/compiler/arm_5.2.8/lib//": Permission denied

>> Compilation failure

Example projects download to (Window7 Desktop) via CCS7 Resource Explorer (REX) cloud share were imported using REX. After deleting CCS7 example projects & files from desktop using Explorer to delete TI-RTOS project folder a message popped saying "Share will be broken do you want to do anyway?" Well I didn't create the folder share and no one had better without asking me in dialog box if it is ok to create a cloud based folder share in the first place.

I then re-download same example projects to the very same (ti) desktop folder via REX, imported project back into CCS7. That's when Fatal Error 6001 occurred and later on any new imports from REX from the cloud share downloaded to desktop. Existing projects that were not down loaded via REX cloud share have no permission issues with any of the installed ARM compilers.

  • The entire CCS Workspace for the project tree & folders inherits Shared file status but they are not network shared!

    CCS7 REX installed project examples install with several ambiguous library path statements:
    Debug/${COM_TI_RTSC_TIRTOSTIVAC_LIBRARIES}
    Debug/${COM_TI_RTSC_TIRTOSTIVAC_LIBRARY_PATH}

    Project GEN library properties dialog warns they are ambiguous paths and may lead to unexpected results!
    Removing debug from the path statement and place a forward slash (/) the warning goes away but.....

    ${COM_TI_RTSC_TIRTOSTIVAC_LIBRARY_PATH}/ (forward slash causes Fatal error 6001 during linking.)
    ${COM_TI_RTSC_TIRTOSTIVAC_LIBRARIES}/