11-13-2012 03:35 PM
Thats what i tried to do, but it needs informations from the bsp-project, so i have to make the driver dependend on the bsp...Then i will have to compile a lib of my drivers for every bsp. Is there a better way to get a lib which works with all bsps?
11-14-2012 08:16 AM
No in that case the code needs to be compiled each time so you need to provide it.It you really have some parts of your driver you don't want to share, you can always try and split it in two. The first part is the low-level driver that directly talks to the hardware, using the constants defined in the bsp, distributed as source code. The second part is the higher level "intelligent" part, that you can distribute as a binary library. Of course it depends on the kind of hardware you have and which part of the driver you need to protect.
11-14-2012 09:48 AM
HI,thanks for your answers! I think the suggestion Daixiwen made is a good solution for me. I will trie out to split my driver sources. I googled the obfuscator, but i am afraid of unexpected behavior of my functions if i obfuscate them. Thanks, Paddy