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

command line build CCS V5.4, absoulte paths in generated makefile

Thomas9070
Expert 1575 points


Hi,

We use CCS V5.4 for a DM648 project. All the sources are within one directory tree that can be checkedout on different locations. We need to compile the project from the command line (build server, automated testing). I try to checkin the generated makefiles and call gmake to build the project.

When I create the CCS V5.4 project, I add the sourcefiles 'relative to PROJECT_LOC'. Nevertheless, in the generated makefiles there are absolute paths, e.g. in subdir_rules.mk or subdir_vars.mk.

Is there a way to avoid absolute pathes in the generated makefiles? Is there a way to build a CCS V5.4 project from command line that was created on a different location?

bye,

Thomas

  • 0
    TI__Guru**** 471801 points

    Hi Thomas,

    Thomas9070 said:
    Is there a way to avoid absolute pathes in the generated makefiles?

    No.

    Thomas9070 said:

    Is there a way to build a CCS V5.4 project from command line that was created on a different location?

    Yes, as long as the project was created to be portable.

    command-line builds:

    http://processors.wiki.ti.com/index.php/Projects_-_Command_Line_Build/Create

    portable projects:

    http://processors.wiki.ti.com/index.php/CCS_Modules_Library#Portable_Projects

    Thanks

    ki

  • 0 in reply to Ki
    Expert 1575 points

    Hi Ki,

    It seems that I am a bit confused by the workspace/project concept of CCS V5. What is part of the workspace and what is part of a project? At the command line build commands it is required to specify a workspace. But I thought that it is only required to checkin the project files into the sourcecode management system.

    What I need to do is:
    - create a CCS project somewhere on a main-PC.
    - checkin all sources and all required project files into a sourcecode management system
    - be able to checkout and build the CCS project remotely on a buildserver (virtual machine, without manual GUI interaction)
    - be able to build the CCS project when the sourcecode tree is checkedout to a different location (different "sandboxes" for different builds)

    What is the role of the parameter -data "C:\myWorkspace" in all the command line calls? Does this workspace already have to exist with the projects to be built imported? If yes - this is a problem since this manual interaction is a problem. Or do I first have to remove all already imported projects, import the one to be built and build?

    Do I have to checkin the CCS workspace? What if it is checkedout on a different location?

    bye,

    Thomas

  • 0 in reply to Thomas9070
    Expert 1575 points

    Hello Ki,

    It seems that a CCS workspace is more a storage for temporary files than something bound to a project. And that you can delete it between the builds. I thought that it has to be created first before you can build - this is what the docu indicates. But - a workspace can be created by just importing an existing project into an empty directory - so the <workspace_path> parameter at

    eclipsec –noSplash -data <workspace_path> -application com.ti.ccstudio.apps.projectCreate

    can be an empty directory. Now I use different workspace directories for the build of each project.

    it is important to mention that the generated makefiles contain absolute paths - so it is no option I would suggest to use. If you try to build on a different location the wrong sources will be used.

    It seems that the way is to create a portable project and import it in an empty CCS workspace (use an empty directory). With that the relative path information will be correct.

    bye,

    Thomas