News:

As usual while waiting for the next release - don't forget to check the nightly builds in the forum.

Main Menu

how do i deploy my program to others?

Started by JerryKc0kk, June 28, 2018, 10:05:59 PM

Previous topic - Next topic

JerryKc0kk

hi

i wrote a program on my windows pc using codeblocks and gcc c++.

what is the easiest way to package and deploy the program to my users so they can install and run the program on their windows pc?

i found no solution in the manual or on the internet

jerry .. wa0h

sodev

Quote from: JerryKc0kk on June 28, 2018, 10:05:59 PM
i found no solution in the manual or on the internet

Not even the internet knows, how shall we know?!? :P

Although this is beyond the scope of this forum, how about https://en.wikipedia.org/wiki/List_of_installation_software? I would go with NSIS or Inno.

raynebc

I just provide the binary and resource files to my users as a zip file.

JerryKc0kk

i apologize, i should have been more specific.

when i asked (how do i deploy to another pc) i should have asked .. in codeblocks, how do i find the libraries and dlls that need to be included in the deploy package?

i built the program in release mode and copied the release .exe to the new pc but nothing happened when i tried to run it.

jerry

oBFusCATed

C::B doesn't provide such tools. You have to use tools like depends.exe or similar to find what is the minimal set of dlls you have to ship.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

gd_on

You can try to use something as "Dependancy Walker".
An other solution is to make your soft static (no dll dependancies).
gd_on
Windows 11 64 bits (25H2), svn C::B (last version or almost!), wxWidgets 3.3.2, Msys2 Compilers 16.1.0, 64 bits (seh, posix : gcc, g++ and gfortran in C:\msys64\mingw64) or 32 bits (dwarf2, posix  in C:\msys64\mingw32).

raynebc

I did it the unsophisticated way:  Bring the program to another computer and note each DLL file it complained was missing when I tried to execute it.  Bring over each relevant file from the development computer (ie. from the compiler's bin folder) until the program does run without error.  After I knew the full set of needed files was assembled, I packaged them together and it's ready to distribute.

oBFusCATed

@raynebc: This is not reliable. You need to do this on a clean operating system, just after installation.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

raynebc

I did that testing with a PC that had no development software on it.  The second step is to monitor user feedback for error dialogs regarding missing library files, which happened on rare occasion when I did something like change compilers.