It turned out that for some project running on Windows, the client asked for statically linking the C runtime (for some reasons I'm not going to disclose) both for Qt and for the application we were developing.
Although this way of build Qt is explicitly regretted by Qt Software (see here), we went that way anyhow. Everything went OK except that we found a memory issue when working in debug mode.
It turned out that some strange is surfacing when using stylesheets (in this case, via a .qss file embedded in the resource file).
So far we found no solution to this. Reverting to dynamically linking Qt means having to distribute and install the Visual C++ 2005 Redistributable Package which is not an option now. And if we statically link Qt (this way no .dlls) that we have proven indeed solved the problem, we cannot do that because of the restrictions of the LGPL license we chose for using Qt within this project.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment