Statement: Articles reproduced or quoted on this site involve copyright issues, please contact the webmaster to handle.

In this situation, after a couple of minutes, you probably want to find out if the power outage is just your apartment (which means you have to do something about it) or other people as well (which means someone else has already called it in).

Of course I couldve exited my apartment and checked the lights in the stairway but being lazy I figured there was a quicker way.

Indeed there was.

Take your phone and browse for Wi-Fi connections Unless you have lots of crazy survivalist neighbors that have a UPS, if the power outage is widespread you will notice that all the usual hotspots around you are gone.

Which means you can relax and not worry about fixing your fusesbreakers.

This means copying all the needed files: besides the main executable file there usually are some shared libraries, e.g.

DLLs, and some other files like configuration or certificate files.

And that app structure in Qt depends heavily on shared or dynamically loaded libraries; on your deployment PC the Qt installer sets these up for you, but on other PCs you need to do it yourself.

You can either use an installer, for example Qt has a good one, or copy the files manually.

If youve using Qt together with Visual Studio (and not the MinGW compiler) and you try deploying your app to a Windows XP or Windows Server 2003 computer, chances are youre seeing this error: Too far from the future.

After youve written and debugged a Go program, you issue the go build command.

The result is an.EXE file with minimal dependencies on the DLLs, in Windows for example its just the usual suspects like KERNEL32.DLL etc.

People sometimes complain though, because even a simple Hello World app weighs in to an approx.

MB.exe file. But deployment problems are more or less nonexistent.

From things like.h files that are designed this way (a humongous file like Windows.h is frowned upon) to the delegation of.DLLs that Qt uses for plugins, platform independency etc.

Partially this stems from the early 90s when Qt was initially designed (in those days, deploying a 2MB.exe could constitute a career-limiting move) but probably mostly because it supports so many different architectures and OSes.

For example, the MaintenanceTool app included in your Qts root directory is built that way (as well as Qts onlineoffline installer programs).

In some environments that makes sense or is required (like when deplyoing Qt apps to iOSiPhone) but lets begin with the simple version: distributing Qt using DLLsshared files.

Had some scattered notes, so I thought why not put them on the web, that way Ill find them for sure next time theyre needed.).

Download Qt Platform Plugin Windows