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/CCSTUDIO: how to hide source code in CCS

Part Number: CCSTUDIO

Tool/software: Code Composer Studio

Hi, TI experts,

We will supply a CCS project to another team do some development. but we don't want the team see the source code. How to do ?

  • Hello,

    user4238397 said:
    We will supply a CCS project to another team do some development. but we don't want the team see the source code. How to do ?

    You should provide a static library instead of an actual project.

    See the link below on how to create a static library project:

    https://e2e.ti.com/support/tools/ccs/f/81/t/868971

    Use the project to build the library and then just provide the library file to the other team.

    Thanks

    ki

  • If you might want them to actually make a bug change and recompile, you could use an obfuscator:

  • Hello,

    Ki, thanks for your reply.

    I have known the way of static library,.But our team is firmware development team, we should supply the CCS project include some source code and configuration files such as .cfg. and other team is algorithm team, they just supply algorithm library usually, but sometimes, the algorithm team need to debug and test their algorithm code, so they need whole project to generate executable file. they only change their algorithm library, don't change other of project. So how to hide firmware code? maybe we can  make use of .obj files, because I think project don't need code recompile only  just need to link .obj file. I don't konw how to do detailed.

    Thanks

    tao

  • ,

    thanks for you reply.

    It is another way, I will test.

  • user4238397 said:
    maybe we can  make use of .obj files, because I think project don't need code recompile only  just need to link .obj file. I don't konw how to do detailed.

    That could work. Just make sure all the obj files are properly referenced in the linker options. You can manually reference each on with the --library option. If you have a lot of objs, maybe it is easier to add all the references in an additional cmd file that you can add to the project.

    Thanks

    ki

  • It worked, thanks