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.

Check points of Building The OMAP-L1 SDK

Other Parts Discussed in Thread: OMAP-L137

Hi OMAP Team,

I am currently following the http://processors.wiki.ti.com/index.php/Building_The_OMAP-L137_SDK in order to re-build all the SDK for my OMAP-L137. There are four builds described in this instructions.

1. Build CMEM

2. Build DSPLink

3. Build Codec Engine Examples

4. Build Codec Server

Is there a documentation defines check points of each building process? I mean a documentation defines which re-built files should be existed at which location so that i can then do the manually checking on these re-built files as my verifications.

For example, during the CMEM building process, the make installation copies some files to some locations. I am looking for a documentation that describes all re-built files in each building step.

Regards,

Ping

Regards,

Ping

  • Hi Ping,

    Ping said:
    Is there a documentation defines check points of each building process? I mean a documentation defines which re-built files should be existed at which location so that i can then do the manually checking on these re-built files as my verifications.

    No. I don't think there is a document like that. you may have to check out the building scripts used for building those packages. Usually the building scripts will have the details like what are all the source files to be built and where those binaries will get settled (i.e., location of the file) e.t.c.,

    Ping said:
    For example, during the CMEM building process, the make installation copies some files to some locations. I am looking for a documentation that    describes all re-built files in each building step.

    For this CMEM, you can open up the makefile and check whether those informations can be interpreted. Environmental variables used for building may also contain those informations.

    If your concern is about confirming whether the build is successful, it will throw error when build is not succeeded. If that is not your concern, sometimes the output messages during build or build-logs may have those details.

     

     

    regards,

    shankari.

    --------------------------------------------------------------------------------------------------------
    Please click the Verify Answer button on this post if it answers your question.

    --------------------------------------------------------------------------------------------------------