Slashdot Mirror


Qt Released For OS X

AxsDeny writes: "It looks like Macslash is also reporting this, but Trolltech is now offering Qt for OS X. Long live cross platform development." Doesn't look like there's a Free version, but there is a non-commerical license called the "Qt Academic License," which "Allows schools and universities to acquire and use Qt for free in relevant courses."

52 of 244 comments (clear)

  1. Another good link by wiredog · · Score: 5, Informative

    To a good article at Kuro5hin.

  2. Qt non-free versions by No-op · · Score: 3, Interesting

    I've been using the Win32 Qt 3.0 for a while, and I have to say that I've vastly enjoyed it. Trolltech earns my vote for one of the best companies I've worked with so far.

    Don't flame them too much for charging money for stuff- everyone has to earn a living somehow :P

    --
    EOM
    1. Re:Qt non-free versions by infiniti99 · · Score: 5, Interesting

      Actually, they say it's because a GPL application cannot be linked to a closed source library. They say if you want to link your GPL app to Qt/Noncommercial, then you need to include an exception-clause in your license (this is similar to what Linus does to allow commercial dev on Linux. read the Linux license sometime, it's not pure GPL).

      And no, you can't get around this by using the commercial Qt. You aren't allowed to redistribute the source with that either.

      However, IMO this is a strange necessity. I've seen some MFC windows apps claiming to be GPL. After reading this thing about Qt though, I wonder if that is even possible. MFC is closed source. Hell, so is Windows. Does that mean that pure GPL applications on Windows are impossible? That any GPL Windows app is actually GPL-with-exception by default?

      Technicalities aside, if someone releases a GPL MFC app, you are _not_ allowed to make modifications unless you have a valid MSVC++ license. Granted, you can get MSVC loads cheaper than Qt, but it's the same principle.

      Anyway, all I'm saying is Qt on Windows is no less evil than MFC when it comes to GPL. It's just more expensive (but then, it's also way better).

    2. Re:Qt non-free versions by infiniti99 · · Score: 2

      The source is only available if you have a MSVC++ license though, right? Qt works just like that too. I got full source code with my Qt/Windows license. However, since both sources are only available to license holders, they are effectively closed-source.

      I did not realize you get MFC source with MSVC++ though, so thank you for pointing it out (I just now verified). I had thought it was always closed, even for developers.

    3. Re:Qt non-free versions by RPoet · · Score: 2
      "However, IMO this is a strange necessity. I've seen some MFC windows apps claiming to be GPL. After reading this thing about Qt though, I wonder if that is even possible. MFC is closed source. Hell, so is Windows. Does that mean that pure GPL applications on Windows are impossible? That any GPL Windows app is actually GPL-with-exception by default?"

      You didn't read the GPL, it already has an explicit built-in exception that basically says that software components normally regarded as integral parts of a runtime environment, does not have to be GPL compatible by themselves. This is what makes GPL applications under Windows/MFC possible, as well as GPL apps under Java/Swing/etc.

      From 3:

      However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary
      form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component
      itself accompanies the executable.
      --
      "Oppression and harassment is a small price to pay to live in the land of the free." -- Montgomery Burns.
  3. This is good news. by Anton+Anatopopov · · Score: 3, Insightful
    Only purist 'license zealots' will worry about the terms of the license. This is great because it means a whole load of great apps can now be ported to run native on Macs.

    MacOS X really is the best of all worlds. You have the stability reliability and scalability of Unix/Mach with the familiar ease-of-use of the mac. Too bad the clunky old PC still seems to rule the roost with the general public :-(

    1. Re:This is good news. by BlowCat · · Score: 2, Flamebait
      Only purist 'license zealots' will worry about the terms of the license.
      Wrong. If you violate the license you are potentially in trouble. If you are a company in Europe or in the United States and you use Qt in violation of the license, your chances to be sued by Trolltech are very high (I would say above 50%).

      Of course, if you are in Russia (seems to be the case for you) or in North Korea or in Iraq, you may want to risk. However, please don't generalize. I'm not a license zealot, but I'm not going to violate their license (e.g. pretend to be a university professor).

    2. Re:This is good news. by dvdeug · · Score: 2

      Russia has the same copyright laws as anywhere else, so TrollTech can sue you there for violating the license just as easy as the US or EU.

  4. Cross platform is definately good... by Ace905 · · Score: 2, Informative

    I've always been impressed with cross-platform initiatives. Especially the ECAs big project to get Eggplant code on every system available. Including embedded devices!

    Eggplants!

    --

    Ace
    1. Re:Cross platform is definately good... by daviddennis · · Score: 2

      It's a joke, and a pretty good one at that.

      Although I'm surprised anyone would have difficulty understanding that - the descriptive material and code exampes made it quite clear what an eggplant is and that the site is satire.

      I'd eat an eggplant to celebrate their achievement if I could stand to do so.

      D

  5. Lets not forget the other big news... by toupsie · · Score: 3, Funny

    ...No not about the mystery press conference tomorrow where Steve Jobs will turn on the Reality Distortion Field and shock us with his "pssst, It's not a Mac" new product. No, I am talking about the native port of Tcl/Tk applications on Mac OS X!!!

    You know I am going to end up with whatever Steve Jobs shows off tomorrow. I already have a closet full of Netwons, QuickTake Digital Cameras, Power CDs and exploding PowerBook 5300 batteries for home defense.

    --
    Strange women lying in ponds distributing swords is no basis for a system of government.
    1. Re:Lets not forget the other big news... by Snocone · · Score: 2

      I already have a closet full of ...

      Yeah, well *I* have a PIPPIN, pose-boy. Top THAT.

    2. Re:Lets not forget the other big news... by mr100percent · · Score: 2

      How many megapixels or CCDs is the quicktake? does it work in OS 9?

    3. Re:Lets not forget the other big news... by toupsie · · Score: 2

      Okay, okay! You got me beat. I hadn't lost that much of my common sense!!! :)

      --
      Strange women lying in ponds distributing swords is no basis for a system of government.
  6. Qt by Dr.+Sp0ng · · Score: 4, Interesting

    I just have to point out that Qt really is the most excellent toolkit I've ever used, for any platform (and the fact that it runs on all major platforms is a huge bonus). It's sanely designed and it really is a pleasure to use. I'm not a big fan of C++, generally preferring C for most stuff, but Qt makes using C++ more than worth it.

    I just can't comprehend why anybody uses GTK these days :)

    1. Re:Qt by Dr.+Sp0ng · · Score: 3, Interesting

      Could it be that some people actually prefer C?

      Dude, did you read my comment? *I* prefer C. But Qt's API is so far above and beyond GTK's that, in my opinion, using GTK is just silly. The API makes my head hurt.

      Anyway, I wasn't trying to start a flamewar, just pointing out my opinion.

    2. Re:Qt by captaineo · · Score: 2, Informative

      I agree that Qt is quite well put-together, but after working with it for a little while (I'm mostly a GTK/PyGTK fan) I've found it has an annoying flaw that really prevents me from using it effectively: its memory-management system is restrictive, and it only works in C++.

      The "restrictive" part is due to the fact that Qt takes a simplistic hierarchical view of resource ownership - parent objects own their children, and delete them when they are deleted. This forces you to implement most of your own code as subclasses of Qt toolkit classes. Aside from being aesthetically icky, this can get you into trouble when the rest of your own code has different ideas about object ownership and lifetimes. At the very least you need to write extra adaptor code or invent weak references for Qt objects.

      The other problem of course is that Qt "only works from" C++. I've long since left static languages behind for GUI development; Python and friends are the way of the future. Sure there are bindings like PyQt, but PyQt has some serious memory management problems (since Python objects are reference counted, and can't easily mesh with Qt's object hierarchy). The result is segfaults and/or memory leaks even for simple PyQt programs.

      Using Qt was an interesting and worthwhile experiment, but I much prefer Gtk's more reasonable resource management scheme (which has been designed from the ground up to cooperate with scripting language bindings).

    3. Re:Qt by Dr.+Sp0ng · · Score: 2

      I agree that Qt is quite well put-together, but after working with it for a little while (I'm mostly a GTK/PyGTK fan) I've found it has an annoying flaw that really prevents me from using it effectively: its memory-management system is restrictive, and it only works in C++.

      True, it only works in C++, but then again that's what the language was designed for, and using it in another language isn't how it was intended to be used. That said, its memory management is very nice... you don't have to delete stuff yourself! How is that bad? If you create a dialog box with lots of widgets, do you really want to have to delete each and every widget, or would you rather just be able to delete the dialog itself and have it automatically take care of deleting its children?

      Granted, in some limited situations it would be nice to be able to turn this off, but for the most part it's very nice.

    4. Re:Qt by Dr.+Sp0ng · · Score: 2

      didn't you write powershell?

      Yep. Haven't updated it in a year and a half, though... I just can't deal with GTK+ anymore :)

    5. Re:Qt by paulbd · · Score: 2

      gtkmm, the C++ wrapper for GTK+, allows you to choose how your widgets are managed. you can opt for "deleted by parent", "parent does nothing" and others. sometimes i want a dialog to leave one or more of its children alone. you can't do that in Qt. furthermore, gtkmm offers full STL compatibility, which Qt does not, and it also draws the line between a GUI toolkit (like GTK+) and a desktop/programming environment kit (like GNOME or KDE).

  7. COOL! by Zo0ok · · Score: 2, Interesting

    Fully carbonized! That means (?) you can develop a program in a mixed Linux/OS X environment, and get Aqua look and feel in OS X. I think it is time to learn Qt ;)

  8. Aqua l'n'f or native Aqua implementation? by pi_rules · · Score: 3, Interesting

    The article kind of glazed over the technical details here... but is this a port of Qt that just wraps around the native MacOSX widgets or does it re-implement everything with an aqua-ish look and feel? Didn't Apple object to the Mozilla port which had an aqua-like but not true Aqua interface?

    1. Re:Aqua l'n'f or native Aqua implementation? by AxsDeny · · Score: 3, Informative

      yeah, if you read through it says that it uses the native Aqua interfaces as well as sets apps up to use the Aqua interface.

      --

      zork% mv *.asp /bin/darkroom
      283 files eaten by a grue
    2. Re:Aqua l'n'f or native Aqua implementation? by Webmonger · · Score: 2

      I read it through and didn't see that. I see that it's a native app, and that it has the Aqua look and feel. And that it's carbon-based.
      I don't see anything saying that it uses native widgets. I don't think this press release is meant for the Slashdot crowd.

    3. Re:Aqua l'n'f or native Aqua implementation? by spitzak · · Score: 2
      They are not using native widgets. They are emulating the Aqua look-n-feel as a Qt theme.

      Anybody who thinks you can make a portable toolit using native widgets has not tried to write one.

      As I understand it, the Aqua look-n-feel could easily be ported to other platforms, but Apple is not allowing that. It is also possible it uses OSX calls to draw some parts of the look-n-feel, this sounds like a reasonable idea since it is not supposed to run on other platforms. However I expect these calls are on the level of "draw a rounded translucent shape this big here", ie much lower than any toolkit interface.

  9. Unix Toolkits for MacOS X by BoarderPhreak · · Score: 2
    I think this is great - it's always good to have the toolkits that we all know and love on MacOS X.


    While this is good for porting, unless it's ported as a true "localized toolkit" then it's not of much use. Take for example, GTK+ which works under MacOS X. Without an X server running to display everything on, it won't do much good.


    What would really be icing on the cake is a translator of sorts, or porting the toolkit directly to MacOS X so that the same functions, etc. would transparently call MacOS X/Quartz functions.


    Remember, Quartz/Aqua isn't X.

  10. Carbonized? by BoarderPhreak · · Score: 2
    If QT is C++ in origin, then why isn't it COCOAized?


    Remember, Carbon is for porting old OS 9 apps easily to OS X. It is based on C. Cocoa is the "real deal" for OS X, and is based on C++. It just seems more logical that they would port QT to Cocoa, not Carbon.

    1. Re:Carbonized? by mcfiddish · · Score: 3, Informative
      Cocoa is the "real deal" for OS X, and is based on C++.

      Actually Cocoa is based on Objective C, which is an object oriented language based on C, but is significantly different than C++. There's also Objective C++, but I don't know anything about it.

    2. Re:Carbonized? by BoarderPhreak · · Score: 2
      What?


      Cocoa and Carbon will run at the same speed, regardless. They both run under MacOS X. However Cocoa does not run under MacOS 9...

    3. Re:Carbonized? by statusbar · · Score: 2

      Unfortunately there IS no Objective C++ available anymore. Something about a patent violation, seriously. This severely limits my usage of Cocoa. This is why libQT for MacOSX is so good. Without it, everybody wanting to use C++ on MacOSX would have to thunk to C to call Objective C Cocoa libs, or use C++ with the crappy Carbon libs.

      --jeff

      --
      ipv6 is my vpn
    4. Re:Carbonized? by alannon · · Score: 3, Informative

      This is completely untrue. Objective C++ was included in MacOS 10.1. I'm using it as we speak. It allows you to mix Objective-C and C++ code freely in a single source code file. It works just as it should. It takes much longer to compile, though. Something about pre-processed headers, I think.

    5. Re:Carbonized? by statusbar · · Score: 2

      heh! Well I guess I should upgrade to 10.1 then! I know it wasn't available for the entire last year. I think HP or someone like that had a patent on the 'thunking' technology used in Objective C++.

      I'm glad it is at least available now! Thanks!

      --jeff

      --
      ipv6 is my vpn
  11. I don't mind them charging ... by Daniel+Dvorkin · · Score: 5, Interesting

    ... I just wish they didn't charge so _much_. Never having been a free software zealot, I don't mind paying for software that's truly useful, as this certainly is. But as a starving student, I just can't pay the kind of prices they're charging. I didn't see anything in their academic license section about prices available to individual students. The excellent student prices available on Metrowerks products are one of the main reasons I've stuck with CodeWarrior as my primary dev environment for so long, even though I haven't been wild about their more recent releases in a number of other ways.

    It would be great if TrollTech learned this lesson. Remember, today's poor CS students are tomorrow's pro developers ...

    --
    The correlation between ignorance of statistics and using "correlation is not causation" as an argument is close to 1.
    1. Re:I don't mind them charging ... by TheAwfulTruth · · Score: 2, Flamebait

      Further, TrollTech is activly hostile to the idea of shareware. A method that students and graduates often use to earn a little extra money. Having had a shareware program of my own keep me in computer parts for 8 years and wanting to port to mac/linux I looked into Troll and was agast at the prices they charge for "commercial" software and even more agast at the fact that they specifically call out "Shareware" as a totally unworkable software model, which they will never support.

      wxWindows is not quite as professional as QT and last time I tried the mac port it was severely trailing the windows/linux port (About a year ago). But at least there's hope for people that both don't want to be starving for the rest of their life or have to be MS itself to afford their commercial lisence fees.

      --
      Contrary to popular belief, coding is not all free blow-jobs and beer. Those things cost MONEY!
  12. Yes, but you're breaking the law by yerricde · · Score: 2, Insightful

    This is great because it means a whole load of great apps can now be ported to run native on Macs.

    Technically yes, but legally no. Many common apps that use Qt are under the GNU GPL and may not be linked with non-free libraries nor compiled with non-free headers.

    --
    Will I retire or break 10K?
    1. Re:Yes, but you're breaking the law by pi_rules · · Score: 4, Informative
      That is absolutely not the case.


      You can write a GPL app and link it to non-free applications. What you cannot do is link to a GLPed library and release it with a non-free (well, non GPL) license. If the library is written under the LGPL you -can- link a non-GPL application to the LGPL library though.


      If your above stated take on the license was true it would be impossible to write a GPLed application for any OS which isn't GPLed from the ground up. You can write a GPL app for Win32 or Solaris, right? Last I checked their standard C library wasn't GPL.

    2. Re:Yes, but you're breaking the law by dvdeug · · Score: 2

      Read the fine license!!! The GPL says

      "However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary
      form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable."

      There's a big difference between QT/OSX and the standard C library of a system in terms of GPL compatibility.

  13. Hmmm... by BoarderPhreak · · Score: 2

    Yeah, my bad... It is Objective C, not C++

  14. wxWindows also works on OSX by ClarkEvans · · Score: 2, Informative

    The wxWindows folks also have a Macintosh port that I believe also uses CARBON. From what I understand they are doing a great job. For python people, wxPython is just fantastic.

  15. Just be careful by mughi · · Score: 2, Interesting

    When I looked into their licensing in general (for possible work use) I noticed that if any project was ever touched by any free version of Qt, it could never be later realeased commercially by purchasing a Qt license at a later date.

    This one limitation might be a severe one for those who care about complying with licenses. Read the whole thing carefully before proceding. And get your lawyer to check things for you.

  16. Pricing - ouch by TomatoMan · · Score: 3, Informative

    You know when you have to dig this deep into the site to find the pricing information, it's going to hurt when you get there.

    http://www.trolltech.com/purchase/qtpricing.html

    US$1550 for one professional license, US$1950 for one enterprise license?

    I believe all the people that say QT3 is the bees' knees, but yikes. Guess I won't be experiencing that coolness for myself.

    (Wistfully remembering the days when Think C was $99, and the early CodeWarriors were around $199)

    --
    -- http://frobnosticate.com
    1. Re:Pricing - ouch by furiousgeorge · · Score: 3, Interesting

      Have you checked out the prices of cars lately? Some of them can go up to even $30,000!!!! Ouch!!

      Not everything is for everybody. The thing is - Qt has developers that actually eat and pay the rent and need a paycheck. And guess what - they deserve it. Qt is KILLER. I work for a small company and we pay for 5 Qt licenses (thats pushing $10,000 a year) - and you know what........ worth every freaking penny. Working with MFC was painful at best, and gtk made me want to go out and kick cars in the parking lot. The increased quality that Qt brings, plus the development time savings is worth the price ten times over. It's a beautiful toolkit.

      It's always so sad whenever something is brought up on slashdot, all people do is bitch and whine because it's not free. Well, welcome to the real world. If you want everything to be free, then you lose the right to complain about the quality of what you get.

      JWZ got it right - and it proves itself every day:
      "linux is free if your time is worthless".

      For those of us who's time isn't worthless, finding the tradeoff point is important. And anybody who can improve that deserves their money.

      Now excuse me, i need to go start a linux system build of our project - it takes SIX @#$(*#&$ hours using GCC - gee, it's the 21st century, you think they'd discover precompiled headers. Once that build is running i'll go back to my MSDEV machine and get some real work done.

      (and debugging with DDD ---------- eeeeshhhhhhh..... god help us all........ yet another way MSDEV kicks serious ass).

      j

    2. Re:Pricing - ouch by Dr.+Sp0ng · · Score: 2

      Seriously it is ONLY a GUI toolkit.

      No it's certainly not - it is a complete application toolkit. The GUI portion is just a part of it (granted, it's a rather large part). It also provides beautiful asynchronous socket support, database connectivity, better-than-STL STL-like functionality (linked lists, hashes, and so on), settings management (uses the registry on windows, dotfiles on Unix), internationalization, threading functionality, process control, an XML parser, really good file I/O routines, printer support, and more. And all of it works perfectly, on any platform that Qt supports. Name me ONE other toolkit that even comes close to this.

      I'm a professional developer and I use Qt, and like the previous poster said, it's worth every penny.

  17. Re:Time to move? by Dr.+Sp0ng · · Score: 4, Informative

    I've got a biggish Win32 program and wonder about moving it to Qt. How big an effort?

    Qt is quite a bit different from MFC, and I think porting would be more effort than simply rewriting it in Qt.

    Any performance hits / gotchas?

    Not really... don't pay any attention to the AC trolls who bitch and moan about moc (Qt's preprocessor)... it lets you do some really neat stuff that you simply can't do with normal callbacks. As for performance, I haven't noticed any speed hits using Qt as opposed to MFC.

    Any features that we'll lose?

    Nope. Anything that Qt doesn't support is EXTREMELY easy to add yourself... Qt is designed in such a way that subclassing a widget to add new features is a breeze, so you can make any widget do anything you want.

    Qt also provides tons of utility classes, which make it simple to do stuff like asynchronous socket/file i/o and so on. It rocks.

    Want to stop being dependent on MS before they collapse!

    Heheh. Good plan :)

  18. Qt rocks by infiniti99 · · Score: 3, Interesting

    This is a complete shameless plug for my application, but it is also a great example of how good of a crossplatform library Qt is.

    Check out JabberCentral and you will see my client, "Psi", has both a Windows and Linux version. The programs are identical (all features are the same). By use of QSettings, application settings are stored in the registry on Windows and in a "dot" file on *nix. And the look&feel matches the OS.

    The best part? All it took was a simple recompile. One source tree sure makes life easy.

    -Justin

  19. Hello? by BoarderPhreak · · Score: 2
    I'm talking about things like GTK+ which on MacOS X right now, requires an X server.


    Dumbass. How about YOU get a clue?

  20. academic licenses by mj6798 · · Score: 4, Insightful
    but there is a non-commerical license called the "Qt Academic License,"

    Reminds me of "Hey, the first one is on me, buddy." Seriously, working in the commercial world, these academic licenses are really tiring: companies get students hooked on some piece of software in the hope that they will then enter the workforce and demand that their employers buy their overpriced commercial software, even when good open source alternatives are available. I hope more and more employers will refuse to fall into this trap: someone who has experience with a costly commercial package where a free alternative is available simply lacks the relevant experience for the job and needs to be retrained.

    Matlab is a huge offender in the engineering world (almost free for students, thousands of dollars in the real world). Qt doesn't seem much different.

    My message to universities (as well as open source developers): if you want a cross-platform C++ toolkit, use wxWindows or FLTK; they are good enough. And if you think it needs improvements, make those improvements student projects and contribute them.

  21. Re:Trolltech should be called on to make QT liscen by Keith+Russell · · Score: 2
    Um, no. Selling commercial licenses to commercial developers for commercial products is a pretty good way to keep a revenue stream flowing. How much money do you think the GTK team would make if they incorporated?

    I think it's fine for Trolltech to straddle the fence:
    • Free edition for Free software
    • Commercial edition for commercial software

    Simple, right? Wrong. Add operating systems to the equation. Now it's:
    • Commercial edition for commercial software on any OS
    • Free edition for Free software on Open Source OSs (and a few architecturally similar closed OSs)
    • Non-Commercial edition for "non-commercial" software, or Free software, if you get permission from the people who manage it, or Open Source software, if that particular flavor of license allows it, for two particular closed OSs that cover all but a sliver of the desktop OS market.


    Trolltech could make everyone's lives easier if they'd just forget about the operating system. Would I like to see Windows go Open Source? Sure. Would I like to see Apple open more of OS X than Darwin? Certainly. Is it going to happen? Not bloody likely. Are Trolltech's licensing terms going to change anything? Not bloody likely.

    I just feel like Trolltech is robbing Peter to pay Paul. They're trying very hard to encourage adoption of Open Source operating systems. Unfortunately, their choice of licensing terms actively discourages cross-platform Open Source applications.
    --
    This sig intentionally left blank.
  22. Re:What about Java? by Pengo · · Score: 2

    I ran the volano benchmark on my G4 466 and it ran 20% faster than the IBM JDK running on my Dual CPU PIII 800.

    I have found java on OSX to be outstanding. I am a java programmer and use it for dev all day, though we deploy to linux boxes.

  23. Qt/Mac may indirectly bring us Linux apps by infiniti99 · · Score: 2

    We might see that happening in the near future now that Qt is available for Mac.

    Qt has always worked between Windows/Unix, but big application companies (like say, Adobe) care more about Windows/Mac. AFAIK, Photoshop has two codebases, one for Windows and one for Mac. With Qt 3.0 they could reduce it to just one. Even though their original intention might be to just have Windows/Mac versions, this would place them "one compile away" from having a Linux version. They may or may not go the Linux route at first, but the option would be obviously there.

    Who knows, maybe this will actually happen.

  24. More on the OS Loophole by yerricde · · Score: 2

    However, as a special exception, the source code distributed need not include ... the operating system"

    I have written more about this operating system loophole in the GNU GPL. Some software publishers might claim, and some courts would believe, that Qt qualifies as an "operating system" under which other applications can run. It certainly is a "platform."

    --
    Will I retire or break 10K?
    1. Re:More on the OS Loophole by dvdeug · · Score: 2

      Publishers might claim anything, and you can always find a court that will agree with pretty much any piece of junk you want to put out. But QT is not an operating system, any more than it's a CPU (an OS always includes a kernel, in every definition and example I've ever seen.) And GNU/Linux plus foo does not make foo a part of the operating system, any more than GNU/Linux plus a i386 makes the i386 part of the operating system.

      It's possible you could argue that QT was part of SuSE and some other Linux operating systems, but that still doesn't give you the right to distribute binaries linked against QT for Solaris, as that's clearly not part of the OS.