View Single Post
Posts: 432 | Thanked: 645 times | Joined on Mar 2009
#30
Originally Posted by jaem View Post
Do you mean this as in "it's not officially supported", "it's not our primary/initial concern" or "it won't work"?
I understand the purpose of Qt Mobility and Qt in general, in terms of portability, but Qt+extensions can't cover everything. Specifically, the work I'm doing at my university involves a couple of libraries developed independently by members of our team (this, for one), and I'd be a bit concerned if the new SDK is designed in such a way that using those will be painful.

It means it is possible but not officially supported. What you could do is cross-compile those libraries and then point in the *.pro file with the whole path to that libraries. This should work. Other possibilities are under discussion, mostly in public, and I hope we can give updates on this soon.

Daniel
 

The Following User Says Thank You to danielwilms For This Useful Post: