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.

What is gitAUTOINC in the TI SDK Linux

I recently downloaded the latest TI SDK for the AM335x (02.00.02.11) and I would like to better understand the naming convention used for the linux kernel and u-boot. In this version, the directory in which the linux kernel resides is named:

linux-4.1.18+gitAUTOINC+bbe8cfc1da-gbbe8cfc

Is gitAUTOINC a special variable or something used by the build system? The commit sha following matches the second to last git commit in the kernel, but the last part I am not sure. How should I expect this directory name to change over time? Basically I am trying to understand how (and if I should) version control the whole SDK or not. We are not using git, but I would potentially keep git for the kernel nested so it is easier to patch later.

Thanks,

- Chris

  • I think, auto increment git version is used for kernel and uboot source.

  • Here in the bitbake user manula www.yoctoproject.org/.../bitbake-user-manual.html
    SRCREV_FORMAT¶

    Helps construct valid SRCREV values when multiple source controlled URLs are used in SRC_URI.

    The system needs help constructing these values under these circumstances. Each component in the SRC_URI is assigned a name and these are referenced in the SRCREV_FORMAT variable. Consider an example with URLs named "machine" and "meta". In this case, SRCREV_FORMAT could look like "machine_meta" and those names would have the SCM versions substituted into each position. Only one AUTOINC placeholder is added and if needed. And, this placeholder is placed at the start of the returned string.

    and in the comment in <OE tisdk>/sources/bitbake/lib/bb/fetch2/__init__.py
    """
    Return the revsion string, usually for use in the version string (PV) of the current package
    Most packages usually only have one SCM so we just pass on the call.
    In the multi SCM case, we build a value based on SRCREV_FORMAT which must
    have been set.

    The idea here is that we put the string "AUTOINC+" into return value if the revisions are not
    incremental, other code is then responsible for turning that into an increasing value (if needed)
    """
    you can find information how the git auto increment is accomplished by the OE.

  • Thank you Kemal. I understand now - I won't be needing that since I am not using bitbake. That answers my question.