3

Is there a way to include dlls in a project so that I don'thave to put those dlls in the same folder with my executable after compiling. This way I could just compile my project with them. Is this a possibility and if yes could someone guide me.

My project is an opencv project and there are many dlls that I would have to include in the folder, and I don't know whether they are .NET assemblies or not, since I read an other post which said that it can be done with .NET assembly dlls.

TasostheGreat
  • 432
  • 1
  • 9
  • 24
  • why do you need to put those dll's in the same folder with your executable? In order to debug or for some other reasons? –  Aug 16 '11 at 12:36
  • 1
    no so that it runs, for example when I give the program to someone else he must have those dlls – TasostheGreat Aug 16 '11 at 13:59

3 Answers3

1

I understand that what you wish to do is to deploy your exe file along with its dependencies (dlls), but you also want it to be configured in the project. You can configure your project to use static libraries instead and you don't have to worry about distributing your DLLs because they are already built into the exe.

If you wish to use DLLs because you do not want to bloat your exe then your code will have to implement its loading, i.e. calling LoadLibrary function and the necessary calls to the specific export functions. Once your code has implemented the loading of the DLLs then you can deploy them the way you described.

Ronald
  • 1,532
  • 4
  • 18
  • 34
0

You can't directly do it with DLL's. "DLL" stands for "Dynamically Linked Library", which means they're not statically linked libraries. And it's the latter kind of library which is "included" (linked in) when you're creating your executable. DLL's are included only at the moment when you run the EXE.

You can check the CV documentation so see how you get a static library version of CV.

MSalters
  • 173,980
  • 10
  • 155
  • 350
-1

The dlls are designed to be dynamically linked - that is they are loaded with your program when it runs.

They don't have to be in the same folder as your app, just somewhere on the path, so you only need one copy of the opencv dlls for all the opencv based programs on your machine.

edit: You can build openCV to use static libraries but it's not recommended, you still have external dependancies such as ffmpeg and the image format libs, and Qt if you used that.

On windows you should probably build an installer which can bundle the exe and dlls. Windows otherwise it will warn every time it runs the app innosetup is one of the simplest.

Martin Beckett
  • 94,801
  • 28
  • 188
  • 263
  • yeah, but if for example I would want to give the program to a friend i would like to have just one .exe and no other files – TasostheGreat Aug 16 '11 at 14:13
  • Downvoting this because "somewhere on the path" is specifically noted by MSDN as a security risk. – MSalters Aug 16 '11 at 14:51