S32 Design Studio中的主题 Re: Files encryption

Files encryption

fanziyu — Thu, 22 Feb 2024 03:12:11 GMT

S32DS for Arm 2018.R1

KEAZ128

Some C files and H files in the project cannot be exposed to the client, the client needs to modify some other C files,and then compile to generate the HEX file. Is there any way?

Can confidential C files be replaced by O files for compilation?How to do this?

Thanks

Re: Files encryption

jiri_kral — Fri, 23 Feb 2024 10:22:07 GMT

Hi,

in my opinion is the best method create a library archive from sources which you don't like to share and link it into your project.

Re: Files encryption

fanziyu — Sat, 24 Feb 2024 00:41:33 GMT

It wasn't planned out this way, and the various global variables were too interleaved for this to work. Is there any other way?

Re: Files encryption

jiri_kral — Mon, 26 Feb 2024 06:31:03 GMT

Hi,

I'm afraid that there is no other option. Library archive is just set of object files (.o) like was your first idea. If you already have .o files - you can simply create library archive by ar tool - https://www.delorie.com/djgpp/v2faq/faq8_22.html

Re: Files encryption

stanish — Mon, 26 Feb 2024 08:51:34 GMT

Hi,

Alternatively, you can link separate object file (.o) as an other object file (e.g. place the affected object files into a custom folder e.g. <Project home folder>\obj\) :

I'd also suggest you to disable debug information generation specifically for these source files. This will make them even harder to understand since symbol information is extracted from the compiled object file.

To do so just right click on specific source file and go to properties (main.c in the example):

Once the change is confirmed the file decorator appears (little black pin) indicating that the source file has a different to default build options :

Hope it helps.

Stan