Hello internet!
Today I'd like to share my experience with you I made today while trying to
decode an Base64 encoded (via Qt) string in a application that does not use Qt (and so does not use Qt for Base64 decoding).
After trying 3 Base64 libraries I though that I have to write the Base64 decoding on my own. Fortunately I found this library a few minutes ago.
Turns out that this library is capable of decoding Base64 string which were created with the Qt Base64 encoding function.
Showing posts with label QT. Show all posts
Showing posts with label QT. Show all posts
Wednesday, March 16, 2011
Monday, January 31, 2011
Qt is just awesome
I just have to say it over and over again.
Qt is just awesome.
Everytime I think of, for example, toolbars...How I could realize them in Qt, I just
open google and search for the tool I'd like to use and add an "Q" at the begining.
"QToolbar"
"QThread"
"QWizard"
It's always a hit.
Qt is just awesome.
Everytime I think of, for example, toolbars...How I could realize them in Qt, I just
open google and search for the tool I'd like to use and add an "Q" at the begining.
"QToolbar"
"QThread"
"QWizard"
It's always a hit.
Thursday, January 27, 2011
Finally got QT static linkage working! (How-to inside)
Yesterday I gave the current build of the leveleditor to a friend to test if the application runs correctly. He got an "Side-by-side configuration is incorrect" error when he wanted to start the editor.
After some investigation I found out that since VS2005 and Windows Vista you have to ship the Visual C++ Runtime library (Downloadlink see below) with your application to make them run properly.
(You'll notice the installation of the runtime files after you start nearly every game the first time in Valves Steam).
So you now have two choices...Either you ship your application with the runtime install files or you link the runtime library staticly to your application.Easy choice yeah...?
Well no. I was FORCED to find out that's it not that easy.
The tricky part is that every library you use in your application also has to be staticly linked with the runtime files.
So if you use foo.dll (DLL = Dynamic link library) and want to use it with your bar.exe but don't want the user to install the visual c++ runtime you'll have to compile foo.dll as foo.lib. To do that you have to open your DLL-project in Visual Studio and go to Project->Settings->Configurationsettings->Common. Set "Configurationtype" from "*.dll" to "*.lib" and choose "use MFC in a static library" at "Usage of MFC" after that go to "C\C++ -> Code generation" and change "Multithreaded Debug DLL" to "Multithreaded Debug" (Or "Multirthreaded DLL" to "Multithreaded" if you want to build a release).
If you've done that you do the same in your application project and then you are ready to go.
For QT-Developer:
If you want to staticly link Qt library you have to do the following:
If you don't want to link staticly, here you'll get the runtime installfiles:
After some investigation I found out that since VS2005 and Windows Vista you have to ship the Visual C++ Runtime library (Downloadlink see below) with your application to make them run properly.
(You'll notice the installation of the runtime files after you start nearly every game the first time in Valves Steam).
So you now have two choices...Either you ship your application with the runtime install files or you link the runtime library staticly to your application.Easy choice yeah...?
Well no. I was FORCED to find out that's it not that easy.
The tricky part is that every library you use in your application also has to be staticly linked with the runtime files.
So if you use foo.dll (DLL = Dynamic link library) and want to use it with your bar.exe but don't want the user to install the visual c++ runtime you'll have to compile foo.dll as foo.lib. To do that you have to open your DLL-project in Visual Studio and go to Project->Settings->Configurationsettings->Common. Set "Configurationtype" from "*.dll" to "*.lib" and choose "use MFC in a static library" at "Usage of MFC" after that go to "C\C++ -> Code generation" and change "Multithreaded Debug DLL" to "Multithreaded Debug" (Or "Multirthreaded DLL" to "Multithreaded" if you want to build a release).
If you've done that you do the same in your application project and then you are ready to go.
For QT-Developer:
If you want to staticly link Qt library you have to do the following:
- Download the OpenSource from the QT libraries.
- After you unpacked everything start the command prompt from Visual Studio.
- Go to the root directory of the unpacked sourcecode (the same directory where bin\ is in)
- Enter "configure -static" (during this process an project.sln will get created)
- Open Visual Studio and open the just created "project.sln"
- Choose the parts of QT you want to build and xo everything mentioned above to staticly link the runtime files.
If you don't want to link staticly, here you'll get the runtime installfiles:
Saturday, January 22, 2011
Subscribe to:
Posts (Atom)