Addu,

Your initial problem with failing to load the program could be helped by some of these:
  • Reading the man page for ldd (1) and running it on your executable.
  • Reading the man page for ld.so (8) particularly about the environment variable LD_LIBRARY_PATH and also when it is ignored.
  • Using a script to wrap your executable and adjust with the LD_LIBRARY_PATH before handling off to your executable.
  • Building a statically linked executable (but read and understand your Qt License first).


Without being able to read minds we cannot help you with packaging your product. You need to tell us:
  1. Whether you can distribute source or the product is binary only. If you can distribute source, and the end-user can build it, then you may only need to put dependency info in a Readme file. If binary only you need to package using a tool that the target OS can understand so the user does not have to guess.
  2. What your target Linux audience is: tech savvy, not tech savvy, people who normally use Windows, paying or non-paying users etc.
  3. What distros they are running. Packaging for Ubuntu (Debian), Redhat (CentOS), Gentoo or Slackware is different. Google for dpkg, RPM, ebuild, ...


It almost always helps to tell people what you have already tried, provide exact error messages if that's what you are asking about, provide that actual code of a minimal program that reproduces the fault if possible, explain what you expected to happen etc. Put some effort into asking smart questions and you'll get much more helpful answers.