[Qt-interest] VS 2010?

[jjDaNiMoTh]

2011/3/3 Jeffery MacEachern <j.maceachern at gmail.com>:
> While I fully agree with your views in that regard, I think (?) that
> Philippe's point was more specific. For example, if you as a company
> need to make alterations or fixes to Qt that won't be upstreamed
> before your product's release, then under the LGPL, you would have
> obligations with regards to distributing the modified source -
> obligations which, to my understanding (IANAL), would persist for much
> longer than may be practical if your company is not already used to
> doing such things. It might not be an issue, but it certainly could be
> a complication.

Is the question: Need you to release every time your modifications to
the Qt sources?

If yes, see this faq [1], you need to provide your modifications only
when you release your product, that links to modified Qt version. So,
under normal development cycle, you could "keep for you" the
modifications (still I think you need to share them with the
community, but who cares now). When your product is ready for
deployment, you should provide the patches to the Qt. So, you need to
distribuite modified source only when you release your product that is
linked to the modified Qt.

[1]http://www.gnu.org/licenses/gpl-faq.html#GPLRequireSourcePostedPublic

I catched the point?

2011/3/3 Konstantin Tokarev <annulen at yandex.ru>:
> Do you know any ccache fork supporting MSVC?

Why not do a Qt coding and testing on a linux box, and when all is
ready compile with MSVC?
More simple: Why not using minigw for development (there is ccache for
minigw) and only for releasing compile it with MSVC?