Acaro00

I would like to protect part of the code, as the mxf file of a standalone is accessible to everybody.

I would like to know how the external objects written in C act within a standalone.

As I can't find the external in the application folder after building the standalone, I wonder about where they really are.

Are they bundled within the .exe (win) or the executable file (mac)??

Is there a way to access to them once you've done the standalone??

I would like to protect part of the code, as the mxf file of a standalone is accessible to everybody.
I would like to know how the external objects written in C act within a standalone.

As I can't find the external in the application folder after building the standalone, I wonder about where they really are.
Are they bundled within the .exe (win) or the executable file (mac)??
Is there a way to access to them once you've done the standalone??


questions-about-using-external-object-to-protect-a-software

It seems that the only file which changes its size once you add an external object to the patch is the .mxf file... bad news, it seems like the binary code of the external is there, isn't it?

Questions about using external object to protect a software