• State Resolved
  • Locked Locked
  • Replies 11 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 585 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.

Original question:

TDA2EVM5777: Vision SDK sample_app build configuration

TDA3XEVM: VISION SDK based project with version control

Claes Ivarsson
Prodigy 80 points
Part Number: TDA3XEVM


Hi,

I am starting a project based on the vision sdk and would like to get recommendations on how to do that from a version control perspective.

My Plan is to install VISION SDK in a docker image which can be used by all developers in the project and I would like this part to be read only.

All files which we will work on shall reside in outside of the VISION SDK file path.

I would also like all generated files from both my source files and ti_components/vision sdk (binaries, archive files from drivers etc)  in my folder for generated file.

Do you have a guideline for this kind of setup ?

  • 0
    TI__Genius 15985 points

    Hi,

    You can use git for this.

    Regards,

    Anuj

  • 0 in reply to Anuj Gupta
    Prodigy 80 points

    Yes, I assume I can use any version control system tool I like. But I plan to use git!

    I am more interested in your suggestion on folder structure and setup in the buildsystem to do this the most efficient way. Without including the files of vision sdk into my repository.

    Regards

    Claes

  • 0 in reply to Claes Ivarsson
    TI__Genius 15985 points

    Hi,

    So you want to move apps folder only out of vision_sdk folder.

    You can move the apps folder to a location and provide that in build/Rules.make, change $(MAKEAPPNAME)_PATH to path where you keep apps folder.

    After this please do a greo of "$(vision_sdk_PATH)/apps" and replace those accordingly as well.

    We have not tried this so can not tell you the exact way of doing this.

    You can start with above points and if you face any issue then please let us know.

    Regards,

    Anuj

  • 0 in reply to Anuj Gupta
    Prodigy 80 points

    Hi Anuj,

    I copied apps, build, links_fw and modifed the following symbol definitions (over multiple files)

    <myfolder>/build/rtos/makerules/env.mk:
    DEST_ROOT=$(abspath $($(MAKEAPPNAME)_PATH)/../binaries/$(MAKEAPPNAME)/$(MAKECONFIG))
    <myfolder>/build/tools_path.mk
    TI_SW_ROOT = <installed root of ti_components>
    <myfolder>/build/Rules.make:
    vision_sdk_PATH = <my new root folder>
    $(MAKEAPPNAME)_PATH := $(abspath ..)/$(MAKEAPPNAME)
    PROJECT_ROOT := $(abspath ..)

    This only partly solves the problem as files are created inside the installed vision sdk path (which I do not like). It seems to me that the vision_sdk_PATH symbol is used in more places then it is supposed. For instance as base for generated binaries and also as base for the build folder and apps. This makes it hard to create our custom application and still reuse the buildsystem, without actually make changes in the vision sdk. 

    Regards
    Claes

  • 0 in reply to Claes Ivarsson
    TI__Genius 15985 points

    HI,

    Can you tell me your sample folder structure which you want to achieve.

    Its difficult to answer without that information.

    Regards,

    Anuj

  • 0 in reply to Anuj Gupta
    Prodigy 80 points

    I have done in the same way as described in https://e2e.ti.com/support/processors/f/791/t/798042 when it comes to folder structure.

    Regards
    Claes

  • 0 in reply to Claes Ivarsson
    TI__Genius 15985 points

    Hi,

    Are you trying to achieve below folder structure

    C:\PROCESSOR_SDK_VISION_03_06_00_00

         |___ti_components
         |___vision_sdk
                |___apps
                |___build
                |___docs
                |___links_fw
                |___sample_app

    D:\TEST

               |___binaries
               |___build
               |___links_fw
               |___sample_app

    So your apps will be in vision sdk folder and everything else will be somewhere else?

    Regards,

    Anuj

  • 0 in reply to Anuj Gupta
    Prodigy 80 points

    Hi,

    Yes, this is correct, apart from the fact that we also copied the apps folder to the local workspace parallel to binaries, build, links_fw and sample_app.

    Regards
    Claes

  • 0 in reply to Claes Ivarsson
    Prodigy 80 points

    Meeting held to clarify this topic. It is clear that the buildsystem in Vision SDK is not designed to be used in a production project with version control. 

  • 0 in reply to Claes Ivarsson
    TI__Genius 15985 points

    Hi,

    We keep all folders under single vision SDK folder and our build system only support that.

    Every engineer has their own local copy and a single copy on remote where all changes will get merged and keep on developing.

    Currently we do not have any prepare document to support your requirement but TI has explained the initial changes to meet requirement.

    We have taken your request to prepare a doc for the same and management will decide when this can be included.

    Regards,

    Anuj

  • 0 in reply to Anuj Gupta
    Prodigy 80 points

    Further discussions regarding this topic will be handled in meetings with the sales contact.