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

Product/Repository Version String

Alex
Expert 2430 points

So when I make custom builds of the various components (NDK, SYS/BIOS, IPC, etc.), specifically where (in what .bld or configuration file) do I set the version string that shows up in the selection dialog box:

Case in point, I need (or want very badly anyway) to maintain two separate builds of the NDK, both based on the same original NDK version, but each slightly customized for the project they will be used in.  So, as highlighted above, when I rebuild the 2.20.2.22 NDK, where do I change its version string?  Like, to 2.20.2.22.ProjName2 or 2.20.2.22.ProjName2 or whatever.

To be candid, I have hunted through all the files in the NDK's directories the package files, and I can't even immediately figure out where the "2.20.2.22" itself is getting set.  (Of course, if I had found it, I probably would not have needed to post this query I suppose. :-)  )

  • 0
    TI__Guru**** 171729 points

    Hi,

    Each companion product in Eclipse is called a "feature" and CCS searches for new features at startup if they are located in the ccs install directory or in C:\Program Files\Texas Instruments.

    Also, a new feature is found if the product has a file <feature.xml> inside a subdirectory called eclipse/features/<feature_name_version>. If you look inside the NDK directory you should see this file (as well as BIOS, etc.)

    You can potentially copy the entire NDK structure and hack into the <feature.xml> file and rename the <feature_name_version> directory. If the changes are syntatically correct from an Eclipse standpoint, it should find the "new" product (provided the conditions above are met). You can also add the new product manually from the screen you show above.  

    However I am not aware of additional implications to the repositories, paths, wizards, etc.(I haven't tried that myself).

    Hope this helps,

    Rafael

     

  • 0 in reply to desouza
    Expert 2430 points

    Yes, that helps tremendously.  I'll give it a shot and report back.  And don't worry; I won't hold you responsible for any unforeseen side-effects. :-)

  • 0 in reply to Alex
    Expert 2430 points

    I actually updated a boatload of files, more than just the features.xml file, to ensure that it got fully integrated, both in the IDE and in the Help system, but it worked!  I tested both on a system I already had an NDK installed and on a clean (non NDK) system.

    Thanks for guidance.  It's much appreciated.