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.

CCS: how to add a configurable parameter to the generated eclipse plug in name

Tool/software: Code Composer Studio

Hi,

I need to generate a RTSC product which can be recognized by the CCS. How do I add a configurable parameter to the generated eclipse plug in name? For example, in the generated eclipse/plugins folder, there are com.ti.rtsc.libarch.product_1.0.1.0 and com.ti.rtsc.libarch.product.ui_1.0.1.0. How do I replace "product" with a configurable target name, e.g. k2g, c6678, etc, such that the names are:

  • com.ti.rtsc.libarch.k2g.ui_1.0.1.0
  • com.ti.rtsc.libarch.k2g_1.0.1.0

or 

  • com.ti.rtsc.libarch.c6678.ui_1.0.1.0
  • com.ti.rtsc.libarch.c6678_1.0.1.0

Thanks,

Jianzhong

  • Hi Jianzhong, 

    Which scripts are you using to generate plugins?

    martin

  • Hi Martin,

    Below is what's in the makefile:

    $(XDC) -P $(LIBARCH_BASE_DIR)/build/eclipse
    $(XS) --xdcpath "$(XDCPATH);$(LIBARCH_BASE_DIR)/build" xdc.tools.product.plugingen -p exports/$(PACKAGE_NAME) -m eclipse.Product

    Thanks,

    Jianzhong

  • Hi Jianzhong,
    I'll re-assign your forum post to a different team as XDCTools is not my area of expertise.

    Martin
  • Jianzhong,

    It's not possible to alter the product* suffix in plugin names, but you can control the plugin prefix. For example, the plugin names can be defined to be

    com.ti.libarch.c6678.product_1.0.1.0 and com.ti.libarch.c6678.product.ui_1.0.1.0

    by overriding the id configuration parameter to be "com.ti.libarch.c6678" in your Product.xdc file:
    override config String id = "com.ti.libarch.c6678";

    That said, starting with CCS 7.1 it's now possible to create target content products for CCS _without_ having to create any Eclipse plugins. In lieu of creating an eclipse directory with plugins, you will need to add some fairly simple .json files that enble your content to be shown via TI Resource Explorer.

    The Toronto team responsible for TI Resource Explorer can help you convert to this new recommended approach for creating target content products.
  • Hi Dave,

    Thanks for the answer. I was aware of the id in Product.xdc, but that would require me to have a different Product.xdc for every supported target, right? 

    I was hoping the target name could be configured through the command line. Is that possible? 

    Thanks,

    Jianzhong

  • Unfortunately there is no command line parameter to define the product id. So, you'll have to use separate "product" .xdc files. However, it is possible to eliminate all duplication within the files.

    Place all the common settings in an interface, say, ILibProduct.xdc _and_ create separate architecture specific product modules that inherit from this interface which override just the product id. For example:

    ILibProduct.xdc:
    metaonly interface ILibProduct inherits xdc.tools.product.IProduct {
    : /* common definitions */
    }

    Product6678.xdc:
    metaonly module Product inherits ILibProduct { /* inherit common definitions */
    override config String id = "com.ti.libarch.c6678"; /* override just the id */
    }

    Now run plugingen on each of the Product* modules.
  • Hi Dave,

    Thanks for the suggestion. I tried and it worked well. 

    Regards,

    Jianzhong