• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 53 subscribers
  • Views 1852 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.

command line build problem

Kurt Jensen
Genius 5040 points

using ccs5 I have sucessfully imported projects into a workspace.  but two of them will not build.  both build without error in the IDE.

here is part of the log from the build

**** Build of configuration Debug for project Unity ****

C:\ti\ccsv5\utils\bin\gmake -k all
gmake: *** No rule to make target `E:/Builds/NanoScan2/UnitTests/workspace/unity_2_0_135/unity/src/unity.c', needed by `unity.obj'.
gmake: *** No rule to make target `E:/Builds/NanoScan2/UnitTests/workspace/unity_2_0_135/unity/extras/fixture/src/unity_fixture.c', needed by `unity_fixture.obj'.
gmake: Target `all' not remade because of errors.

**** Build Finished ****

Note that unity.c and unity_fixture.c are not in the Unity project directory.  They are referenced as a link in the Unity project.

In fact, the two files that do not compile in the other project are -also- linked from another directory.  Hmmm...is there a pattern?

I can eliminate the linked files in the first project but not in the other project.

Is there some way to enable verbose output on the command line build?

 

  • 0
    Genius 5040 points

    Hi. I have spent much more time trying to find a solution but it still fails the build.

    Would appreciate some help.

  • 0 in reply to Kurt Jensen
    TI__Mastermind 21285 points

    Hello team,

    Is there an update available on this inquiry?

    Regards,

    Michael

  • 0
    TI__Guru**** 451251 points

    Kurt Jensen said:

    Note that unity.c and unity_fixture.c are not in the Unity project directory.  They are referenced as a link in the Unity project.

    In fact, the two files that do not compile in the other project are -also- linked from another directory.  Hmmm...is there a pattern?

    That is a fair assumption. Are you importing an existing v5 project? Or are you importing an older CCS project? In any case, linked files should not cause any problems on import. A small reproducible test case would be really helpful.

    Thanks

    ki

  • 0 in reply to Ki
    Genius 5040 points

    OK, I have -finally- gotten back to my ccs5 development project. seems as soon as I post a question I get yanked over to a different project...

    I found the problem. It is kind of obscure.  But not if you set it up the way I did.

    Here is the directory structure I was using:

    NanoScan2
      UnitTests
        workspace
        Sources
          Firmware
          workspace
            NanoScan2
            UnitTests

    The lowest workspace was intended for use witht the IDE. I created the upper workspace for command line builds. In this case links from Unittest to NanoScan2 source files would fail to compile. But this is all being done as part of a TFS Build process.  All of the files are extracted fresh for each build.  In that case I do not care about the IDE.  When I changed the Import and Build to use the lower workspace folder then the build succeeds.

    But now I have another problem.  In my UnitTests project I setup an include directory to NanoScan2 via the workspace, "${workspace_loc:/NanoScan2}" In the command line build this evaluates to an empty string and I get the error "option --include_path is missing its parameter 'dir'"  I loaded the workspace into the IDE and it builds just fine - the include path is correctly populated. This seems easy to duplicate.

    Seems like every time I try something it does not work.  Am I breaking new ground here?