wxWidgets 2.8.3 dll

[Knx]

Code

This application can not be started because the file wxmsw28u_gcc_custom.dll has not been found.

I know where this DLL is stored, if I copy it to the .EXE's folder it works.

But I want to know if there is a way to add this automatically and how to change dll's name.

[stahta01]

Code

This application can not be started because the file wxmsw28u_gcc_custom.dll has not been found.

I know where this DLL is stored, if I copy it to the .EXE's folder it works.

But I want to know if there is a way to add this automatically and how to change dll's name.

Do you know what an static build is?

If you just want to change the word custom in the DLL name look up the VENDOR in the wxWidgets info.

See docs/msw/install.txt

Tim S

[Knx]

Thanks

Code

VENDOR=<your company name>
  Set this to a short string identifying your company if you are planning to
  distribute wxWidgets DLLs with your application. Default value is 'custom'.
  This string is included as part of DLL name. wxWidgets DLLs contain compiler
  name, version information and vendor name in them. For example
  wxmsw283_core_bcc_custom.dll is one of DLLs build using Borland C++ with
  default settings. If you set VENDOR=mycorp, the name will change to
  wxmsw283_core_bcc_mycorp.dll.

Do you know what an static build is?

I know how to link static libraries, but I don't know how to use dynamic libraries...

[stahta01]

Thanks

Code

VENDOR=<your company name>
  Set this to a short string identifying your company if you are planning to
  distribute wxWidgets DLLs with your application. Default value is 'custom'.
  This string is included as part of DLL name. wxWidgets DLLs contain compiler
  name, version information and vendor name in them. For example
  wxmsw283_core_bcc_custom.dll is one of DLLs build using Borland C++ with
  default settings. If you set VENDOR=mycorp, the name will change to
  wxmsw283_core_bcc_mycorp.dll.

Do you know what an static build is?

I know how to link static libraries, but I don't know how to use dynamic libraries...

There is many ways to move the DLL, but there is no way for me to know why you do not want do it manually.
If, you don't want an DLL just do an static build.
If, you are an developer writing an application look at the documentation of the installer program you plan to use.
If, you are just starting out and are willing to risk DLL Hell http://en.wikipedia.org/wiki/DLL_Hell, then copy the DLLs to an directory in your path.
If, you want you can write an batch, or script, file that copies the DLL and make it part of your project.

Note, the above methods most likely are not complete; they are just the ones I thought right now.

I myself just copy it manually or use a static library build.
But, I know enough to do the installer method, I just have not yet done it with wxWidgets DLL.
The only method I have not done, or know how to do, is use a batch file to copy the DLL.

Note, a primary reason I don't copy the wxWidgets DLL to a folder in the path is that I am always making different version of the DLL to test. If DLL was in the path, the testing would not be as easy.

Tim S

[Knx]

Thanks for the information.
I'll move it manually so I can control it better.