Application builder and DLL

[Harold Hebert at NRC]

(excuse my english)

I build industrial system that contain hight speed digitizers and many others instruments.

We developp also high levels digital processing functions in C and compile them in LLB . Our actual clients are chinese laboratories and industries.

My function is to develop the hardware and the main user software. After acquisition is done I use the treatment functions developped by our researchers thrue LLB.

After buildind an application, the LLB appears in a Data folder.

I would like to find a way to embed the LLB in the compiled code in order to protect it and also to reduce the upgrade to send to our client as a simple

executable file. We would like to continue to work with LLBs rather than CINs.

Need help.

[tst]

You keep writing LLB, but your header says DLL, which also makes sense in the context, so I'll assume you're refering to a DLL.

Other than a CIN, I don't think there is any way to embed C code into your VI. There is the formula node, but that is not pure C.

If you want to simplify the deployment, you can create an installer or just a small executable which will deploy the application's executable as well as the DLL. You can do this either by writing code in C or LV or by using something like a self extracting archive. I think Winzip can create those.

[Harold Hebert at NRC]

In fact, in my text, LLB should be read as DLL.

[Harold Hebert at NRC]

Thank you for your answer. In my text, "LLB" should be replace by "DLL".

I think that digital analysys and treatment guys will have to sit with the development guy.

They uses their development tools (Pascal, C, Matlab ...) and I have to embed thoses functions in our systems.

We are in a big rush now. I must find a way to remove those DLL in our already installed systems in China.

However, it could be interesting to find a way to protect DLLs.

Once again, thank you for the info.

[tst]

What do you mean by "protect"?

If you want people not to be able to use the functions inside the DLL, simply don't include the parameter definitions with the program. This will not make it impossible, but unless your functions are extremely simple (i.e. clear name, one input, one output) people will not know how to call them.

If you just want to protect the actual files themselves, have the program installed in a folder where only the admin has write priviliges and use the admin account only for installing the program.

[Harold Hebert at NRC]

Thank for the information.

Our functions do have many inputs and are quite complex.

Now I will try to find the way to exclude the parameter definitions with the program.

[tst]

---

@Harold Hebert at NRC wrote:

Now I will try to find the way to exclude the parameter definitions with the program.

---

That should be simple. These definitions are usually distibuted in header files (.h), so you can simply tell the C guys not to include those (which they're probably not doing anyway).