@Kinesis There are only two options: Install a compatible Qt version on the second computer Deploy all needed libraries along with your program. You may want to have a look at linuxdeployqt Regards

Oh ok, thanks to both of you! I think I am just going to make videos on it and show that without actually sending it. Thanks though!

You could certainly make use of UPX, it should get the filesize down to maybe 4MB (by using compression).

If I may, don't call the destructors like that. When you want to "destroy" a heap allocated object call delete on it.

Hi, You can cross-compile Qt and your application using MinGW provided that you don't use any Linux specific API.

Writing a small compiler ?

You have to place the respective libraries and plugins in corresponding place where the executable is placed. And the libraries and plugins must be refering to executables.

yes that was the problem thanks ^^

@koahnig Thank you very much for your help. Your link explained some concepts to me. I had the "The procedure entry point _ZN10QArrayData10deallocateEPS_jj could not be located in the dynamic link library Qt5Core.dll." error message and wasn't sure how to deal with it. I realized I was using only .dll files from the C:\Qt\Tools\QtCreator\bin directory. When I used the .dll files from the C:\Qt\5.4\mingw491_32\bin directory -- including libstdc++6.dll which i should have just tossed into my build folder, my issues disappeared. This makes sense since I was using that MinGW instance to do my compiling. This forum question helped my problem more specifically. Dependency Walker is still stating that I'm missing these files: API-MS-WIN-CORE-COM-L1-1-0.DLL API-MS-WIN-CORE-WINRT-ERROR-L1-1-0.DLL API-MS-WIN-CORE-WINRT-L1-1-0.DLL API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0.DLL API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL API-MS-WIN-SHCORE-SCALING-L1-1-0.DLL DCOMP.DLL GPSVC.DLL IESHIMS.DLL These are .dll files which some forums tell me are only side problems of something unrelated.

HI, I suggest to open a new post because you marked this as SOLVED. BTW if you moved to windows and want to see the debug output you should add CONFIG += console to your .pro file