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 without CCS V5?

Hi,

Currently I use CCS V3.3, I am thinking about the implications of switching to CCS V5.

I build my project from command line now also on a buildserver and on PCs that run automated tests. I dont use the editor on the build server, this is just a virtual machine that calls the compiler in order to produce a software release.

Is a command line build possible without having CCS V5 installed on that PC?

The info on this page: http://processors.wiki.ti.com/index.php/Projects_-_Command_Line_Build/Create indicates that CCS install is required, so a license for CCS would be required also for the buildservers... is this true? Is there a license model for a 'build-only' environment?

bye,

Thomas

  • Thomas,

    Depending on the device family, CCSv5 can be installed and used free of charge (check details here) - although it still requires an install to be performed, the custom installation can be reduced to a very minimal setup.

    The page you mentioned perform command-line builds using CCSv5's built-in project management features - thus it requires a complete CCS project (.pjt in CCSv3.3 or a set of files in CCSv5).

    However, since you mentioned your buildserver only calls the compiler (we call it code generation tools, as they also have assembler, linker and other utilities), then the modifications to your existing buildserver will be minimal, as a typical CCSv5 installation contains the commmand-line versions of the code generation tools (installed under ccsv5/tools/compiler).

    Hope this helps,

    Rafael

  • Hi Rafael,

    as far as I understand it, the free CCS is no option for me. I have a large project running on DM647 - both not supported on free CCS.

    But... first: is it legal to use the ccsv5/tools/compiler seperately? Are you thinking about copying the ccsv5/tools/compiler to the buildserver?

    second: Is there a way to generate something like a makefile from a CCS project? Or to build a CCS project without having to specify the build settings on different locations? What about the parts that are not just plain C code? The DSP BIOS configuration etc.? How do I build these parts without having a full CCS installation?

    bye,

    Thomas

  • Thomas,

    The only limitation of the free limited version for your processor is the use of advanced emulators (XDS510, XDS560). There is no limit in code size or device family.

    As I mentioned, you can install CCSv5 to your buildserver using a minimal set of features - you can't install CCS in one PC and copy parts of its installation to the buildserver.

    In the case of C6000, you can also download a copy of its command-line compiler at the page below:

    http://processors.wiki.ti.com/index.php/Compiler_Releases

    All Eclipse-based projects (CCSv4 and v5) generate a set of makefiles in the project output directory. These files allow building the project from the command line using a simple gmake utility - and yes, they also build the non-compiler source code.

    In this case you can also download the Target Content updates from the main wiki page (check the link at the bottom of the main screen), but you will have to make sure you install the matching components.

    In my opinion, I would install a version of CCSv5 and play with its project build capabilities and see how well it adapts to the buildserver. It is also a good start for a well-known good configuration, as the combination of tool versions can be very confusing.

    Hope this helps,

    Rafael

  • Hi Rafael,

    thanks! I played a little more with CCS 5.1 - and now I think I understand what you meant by 'install with minimal set of features'.

    I installed CCS 5.1 on a second test-PC and selected 'free license'. On my main PC, I created a project with all sourcefiles being 'linked', include pathes etc. with path relative to environment variables or the project location. I checked-in the project files in my subversion repository and checked it out on the second PC on a different location. There I imported the project into CCS and built it - which worked in the same way than on the main PC. The resulting .out files were working - so as you said there are no restrictions from the free CCS license from that side. This is what I needed to know for the buildserver.

    I will now try to see how command line build works when CCS is installed. But I think the best will be to install CCS 5.1 on the buildserver and build the project 'the CCS way' and not with manually installed components...

    bye,

    Thomas