Skip to content

Epilogue: Trolltech is listening

Wednesday, 19 September 2007  |  jaroslaw staniek

Not even 2 days after out meeting in Berlin, there is an epilogue of the story: Qt/Windows Open Source Edition will support VS Express.

Big thanks for considering this!

There are always many comments about boundary between free and non-free tools. I can give two notes here:

  • Q: Hey, why to add dependency on these tools?
    A: The word "dependency" here looks like manipulated. Qt technology is about single-source-code projects and clean portable design. For example in my recent test KWord compilation I have not added even one #ifdef. If there are any specifics in such portable development, they usually come from operating system, not compiler. In the worst case most often you fall back to Qt equivalents of the given KDE technology instead of relying on anything built in-house. For example in KDE 3/Windows I have uses QFileDialogs in place of KFileDialogs. In KDE 4 there is improvement in form of abstract file dialog interface. But again, this is not related to compilers.
  • Q: Oh, but I use mingw and it compiles quite fine!
    A: Many of us are concerned about all the development tools (fast compilation, linking, debugging), not just compilation. I wish I can see some large entity like Google or a Linux vendor supporting gcc project heavily to make its internals become a present-day technology (surprise, we have more than 32MB RAM and 500MB HDD today, but still gcc, being unbeatable in cross compilation, unfortunately creates unoptimized temporary files with linear lookup cost). So far, some people do abandon mingw project (see the Christian's link below), and even not satisfied with gcc as a project someone from the outside would like to contribute to.
  • Q: But I don't especially admire vendor of this compiler... Does msvc Express allows for Open Source evelopment at all?
    A: Yes it does. And there are also Intel's and SUN's compilers available for KDE you may want to try... Again, in the worst case if the vendor stops the support, you still have _single-source-code_ project, and abstracted in terms of design (you pay attention to this, do you?), so you can move with your development to other tools or even operating system. It's especiallny not a problem for folks like me, who do the development in parallel on Linux, Windows and sometimes on the Mac.

For some notes about gcc on windows read Christian's blog entry.