Is it known issue that QT5.0 does not create VC2010 Projects?
Thanks
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
>A cross platform compatible API for the serial port is a useful thing,
>but is there a good reason for limiting it to Qt applications ?
Why do you think that this is a limitation?
This is just a separate, cross-platform implementation of the serial port,
taking into account the Qt-specific,
an
Am Freitag, 11. Januar 2013, 23:07:25 schrieb Shaw Andy:
> > [...]
> >
> > > Microsoft in the past has also said that you should keep the
> > > -MD(d)/-MT(d)
> > > setting consistent so it is the same across all libraries and
> > > applications,
> >
> > [...]
> >
> > Which is cool, if you can ma
On Friday 11 January 2013 15:01:57 Alan Alpert wrote:
> On Fri, Jan 11, 2013 at 1:43 PM, Bache-Wiig Jens
>
> wrote:
> >> Hi,
> >>
> >> As part of the Android-port of Qt 5 being contributed to the Qt Project
> >> by BogDan, he also contributed the code for a general-purpose Android
> >> app which
> [...]
>
> > Microsoft in the past has also said that you should keep the -MD(d)/-MT(d)
> > setting consistent so it is the same across all libraries and applications,
>
> [...]
>
> Which is cool, if you can manage it. But it's far from what happens in the
> real world.
>
> In the real world y
On Fri, Jan 11, 2013 at 1:43 PM, Bache-Wiig Jens
wrote:
>
>> Hi,
>>
>> As part of the Android-port of Qt 5 being contributed to the Qt Project
>> by BogDan, he also contributed the code for a general-purpose Android
>> app which is used for getting libraries and plugins on demand when a Qt
>> app
On 01/12/2013 07:43 AM, Bache-Wiig Jens wrote:
>> Hi,
>>
>> As part of the Android-port of Qt 5 being contributed to the Qt Project
>> by BogDan, he also contributed the code for a general-purpose Android
>> app which is used for getting libraries and plugins on demand when a Qt
>> app is deployed
[...]
> Microsoft in the past has also said that you should keep the -MD(d)/-MT(d)
> setting consistent so it is the same across all libraries and applications,
[...]
Which is cool, if you can manage it. But it's far from what happens in the
real world.
In the real world you have foreign libra
> Hi,
>
> As part of the Android-port of Qt 5 being contributed to the Qt Project
> by BogDan, he also contributed the code for a general-purpose Android
> app which is used for getting libraries and plugins on demand when a Qt
> app is deployed to an Android device. This tool is called "Minis
> I'm no expert on the various build and link issues, but in trying to write the
> new ICU backend for QLocale which would make ICU a hard requirement in
> the
> future I've started running into problems which may affect your choice of
> solution.
>
> For those interested, I have working code for
> On sexta-feira, 11 de janeiro de 2013 13.32.35, Shaw Andy wrote:
> > Unfortunately this is what is happening now if ICU is linked in, ICU will
> > always use the release version so if Qt is built in debug mode then it will
> > end up mixing the C runtime libraries.
>
>
> > Either way I feel tha
On sexta-feira, 11 de janeiro de 2013 20.18.52, Oswald Buddenhagen wrote:
> On Fri, Jan 11, 2013 at 03:51:02PM +, shane.kea...@accenture.com wrote:
> > > NOTE: No cherry-picks this time !!
> >
> > What about changes that are integrated to stable already but missed
> > the branch due to unrelat
On Fri, Jan 11, 2013 at 4:47 PM, Simon Hausmann
wrote:
> Hi all,
>
> Now that Qt 5.0.0 is out I feel that it is a good time to also emphasize show
> cases
> of Qt and QML as a technology. In Qt 4 we've had a couple of pretty nice demos
> in the source code, including a pretty neat demo browser. I
On Fri, Jan 11, 2013 at 03:51:02PM +, shane.kea...@accenture.com wrote:
> > NOTE: No cherry-picks this time !!
> >
> What about changes that are integrated to stable already but missed
> the branch due to unrelated test failures delaying the integration?
>
your premise is already wrong.
if it
On Fri, Jan 11, 2013 at 6:52 PM, BogDan wrote:
> I'll do a summary of them:
> - the most important is that qt libs are very big (Qt4 libs are +40Mb for
> one
> platform and most probably Qt5 will be more than that), if you want to
> target
> two platforms (armv5 and armv7) you need to bundle +80
BogDan: Thank you for all your work and this explanation!
I was afraid that, at least part of, the reasoning for Ministro was the
create/control a "shared location" :(
Do you have any ideas of how we could continue with "shared libraries" (not
per app) but avoid having to install ministro "manual
On Fri, Jan 11, 2013 at 04:53:25PM +0100, Giuseppe D'Angelo wrote:
> On 11 January 2013 15:21, Olivier Goffart wrote:
> > c. Critical fixes (P1/P0): security, crashes or data corruption.
>
> Aren't important fixes (such as security fixes) good candidates for
> the release branch instead of stab
Hi,
I have write a few mails on this matter at android-qt mailing list.
Here https://groups.google.com/group/android-qt/msg/854062a719092224
you can find my reasons why I believe that Ministro is the best solution for
Android deployment.
I'll do a summary of them:
- the most important is tha
On Friday 11 Jan 2013 20:45:43 Konstantin Tokarev wrote:
> It's icky to cross-compile, otherwise bearable. Size comes only from bundled
> data, if you can use external dat file, your ICU may be quite small.
Unfortunately, the format of the the dat file is very tightly coupled with the
ICU major
This is my experience as well, as of now I am doing native or Cordova app
dev on the android platform since for my particular audience the Ministro
workflow is too much.
WHat about the statically linking libs in or talking to Google to include
it there anyways ?
On Fri, Jan 11, 2013 at 4:36 PM,
11.01.2013, 20:29, "John Layt" :
> On Friday 11 Jan 2013 13:32:35 Shaw Andy wrote:
>
>> Since ICU doesn't provide the debug version of the libraries in their binary
>> packages then this means that either the user has to build them themselves
>> (which means modifying the target as well since
On Friday 11 Jan 2013 13:32:35 Shaw Andy wrote:
> Since ICU doesn't provide the debug version of the libraries in their binary
> packages then this means that either the user has to build them themselves
> (which means modifying the target as well since the output for debug and
> release defaults t
On Fri, Jan 11, 2013 at 12:59 PM, Alberto Mardegan
wrote:
> On 01/11/2013 04:47 PM, Simon Hausmann wrote:
>> So I got in touch with them and they're willing to contribute the code to
>> the Qt
>> project. I'm therefore seeking approval from the Qt project to importing
>> Snowshoe
>> into Gerrit,
On 01/11/2013 04:47 PM, Simon Hausmann wrote:
> So I got in touch with them and they're willing to contribute the code to the
> Qt
> project. I'm therefore seeking approval from the Qt project to importing
> Snowshoe
> into Gerrit, with
[...]
I like the idea, but I'm a bit concerned about the fu
On 01/11/2013 04:51 PM, shane.kea...@accenture.com wrote:
>> Hi,
>>
>> All the repos part of the Qt 5.0.1 release were merged yesterday from
>> stable->release as announced.
>>
>> So changes for 5.0.1 need to be pushed to 'refs/for/release' with a
>> Task-number tag in the commit message pointing t
On 11 January 2013 15:21, Olivier Goffart wrote:
> c. Critical fixes (P1/P0): security, crashes or data corruption.
Aren't important fixes (such as security fixes) good candidates for
the release branch instead of stable?
--
Giuseppe D'Angelo
___
De
> Hi,
>
> All the repos part of the Qt 5.0.1 release were merged yesterday from
> stable->release as announced.
>
> So changes for 5.0.1 need to be pushed to 'refs/for/release' with a
> Task-number tag in the commit message pointing to a P0/P1 task [1].
>
> The process should be that you get the ch
On sexta-feira, 11 de janeiro de 2013 13.32.35, Shaw Andy wrote:
> Unfortunately this is what is happening now if ICU is linked in, ICU will
> always use the release version so if Qt is built in debug mode then it will
> end up mixing the C runtime libraries.
> Either way I feel that this needs t
Hi all,
Now that Qt 5.0.0 is out I feel that it is a good time to also emphasize show
cases
of Qt and QML as a technology. In Qt 4 we've had a couple of pretty nice demos
in the source code, including a pretty neat demo browser. It serves as a
show-case
for QtWebKit's C++ API and the Qt widgets
On sexta-feira, 11 de janeiro de 2013 15.21.43, Olivier Goffart wrote:
> Go to stable:
> a. Fixes to regressions against a previous "recent" version of Qt. (less
> than 2 or 3 years old)
> b. Fixes in new feature introduced in the most recent minor version.
> c. Critical fixes (P1/P0):
On Fri, Jan 11, 2013 at 4:31 PM, Eskil Abrahamsen Blomfeldt <
eskil.abrahamsen-blomfe...@digia.com> wrote:
> This suggestion is definitely something we'll investigate. I haven't
> looked into the Ministro code yet, so I don't know if it's technically
> possible, but as far as I've understood from
On 01/11/2013 04:23 PM, Felipe Crochik wrote:
With my very limited experience on the subject I have to say that "the
current flow" is probably good enough for "controlled distribution"
but pretty bad for mass market apps.
Having the application download the libraries after "being downloaded"
With my very limited experience on the subject I have to say that "the
current flow" is probably good enough for "controlled distribution" but
pretty bad for mass market apps.
Having the application download the libraries after "being downloaded" is
bad enough for the average user but figuring out
On 01/11/2013 03:36 PM, Felipe Crochik wrote:
Are there plans to change this flow? I have to assume there were good
reasons to do like this but without actually looking into the code it
seems that would make more sense to combine the ministro code with the
java wrapper generated for each applic
Mainly my suggestion is to avoid the step of having to have ministro
installed. I appreciate that including the qt libraries with every app is
not the best approach (especially if we need different sets for the
different android versions/devices).
I would like for each application to include some
On Fri, Jan 11, 2013 at 2:36 PM, Felipe Crochik wrote:
> I have to assume this subject has been discussed before in other lists but
> since the android port it is a "hot topic" on this list right now I thought
> it was worth starting again.
I think it is a good idea to reiterate again because ma
I have to assume this subject has been discussed before in other lists but
since the android port it is a "hot topic" on this list right now I thought
it was worth starting again.
I deployed a test application using the necessitas project and while I was
impressed on how nice the development exper
Hi,
We should finish this discussion and document the conclusion in
http://qt-project.org/wiki/Branch-Guidelines
...
Marc Mutz wrote:
> > > Ok, trying to summarise, I understand it this way:
> > >
> > > 1. release-critical fixes are submitted and merged to 'stable' now,
> > >'release' later,
On 01/11/2013 02:41 PM, Glen Mabey wrote:
>
> On Jan 11, 2013, at 2:03 AM, Samuel Rødal wrote:
>
>> On 12/28/2012 03:36 PM, Glen Mabey wrote:
>>> Hello,
>>>
>>> For some time, I have been working on a QtCore-based class that would be a
>>> container class of arbitrary dimensionality. I did give a
On Fri, 11 Jan 2013 07:19:19 -0600, Glen Mabey wrote:
>> Something I was missing several times is a 2D container. Qt has objects
>> organized in rows and columns ( QTable, QImage ... ) - so IMHO it is
>> related to Qt.
>>
>> But I would expect to find a class with an API comparable to QVector.
>
Hi,
As part of the Android-port of Qt 5 being contributed to the Qt Project
by BogDan, he also contributed the code for a general-purpose Android
app which is used for getting libraries and plugins on demand when a Qt
app is deployed to an Android device. This tool is called "Ministro".
We nee
On Jan 11, 2013, at 2:03 AM, Samuel Rødal wrote:
> On 12/28/2012 03:36 PM, Glen Mabey wrote:
>> Hello,
>>
>> For some time, I have been working on a QtCore-based class that would be a
>> container class of arbitrary dimensionality. I did give a presentation on
>> this topic at DevDays-CA:
>>
As I was investigating a different problem I came across a bigger issue
regarding ICU on Windows. The problem is that when ICU is linked against on
Windows it links against the same copy of the library even if it is building
for release which causes a problem with C runtime libraries on Windows
On Jan 11, 2013, at 1:56 AM, Uwe Rathmann wrote:
> On Wed, 09 Jan 2013 16:02:17 -0600, Thiago Macieira wrote:
>
I think this is out of the scope of Qt. I do not see that many uses
case for normal Qt applications.
>>>
>>> I am not surprised that some developers would feel this way, an
QMessageAuthenticationCode is ready: https://codereview.qt-project.org/44512
11.01.2013, 02:51, "Richard Moore" :
> On 10 January 2013 22:32, Ruslan Nigmatullin wrote:
>
>> 11.01.2013, 00:55, "Richard Moore" :
>>> On 10 January 2013 20:48, Ruslan Nigmatullin wrote:
2. HMAC is unsupporte
On 10-Jan-13 17:26, Alan Alpert wrote:
>> The Qt
>> heritage so far was, to maximize portability level, to "test for
>> features" - something sadly currenly NOT possible in an easy way in QML.
> The Qt heritage so far was desktop, where cross-device compatibility
> meant "make sure it'll still work
On Jan 10, 2013, at 5:46 PM, Alberto Mardegan
wrote:
> Hi all!
> I'd like to make C++ models more usable from QML; in the net there
> are several blog posts illustrating how to achieve that, but IMHO it
> would be better if at least some of these handy features were in
> QAbstractListModel
11.01.2013, 11:57, "Uwe Rathmann" :
> On Wed, 09 Jan 2013 16:02:17 -0600, Thiago Macieira wrote:
>
I think this is out of the scope of Qt. I do not see that many uses
case for normal Qt applications.
>>> I am not surprised that some developers would feel this way, and I
>>> think I
On 12/28/2012 03:36 PM, Glen Mabey wrote:
> Hello,
>
> For some time, I have been working on a QtCore-based class that would be a
> container class of arbitrary dimensionality. I did give a presentation on
> this topic at DevDays-CA:
>
> http://www.qtdeveloperdays.com/northamerica/sites/default/
49 matches
Mail list logo
