On 2019-11-07 10:40 a.m., Cristian Adam wrote:
You can use https://qtlite.com/ to figure out only the parts you need for your
setup.
Cool!
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
On 2019-11-07 10:31 a.m., Konstantin Tokarev wrote:
07.11.2019, 18:08, "drwho" :
On 2019-11-07 12:42 a.m., Thiago Macieira wrote:
On Wednesday, 6 November 2019 20:41:10 PST martin ribelotta wrote:
4) What about the memory footprint?
A couple of megabytes.
I'd love to see a build how t
You can use https://qtlite.com/ to figure out only the parts you need for your
setup.
Cheers,
Cristian.
> -Original Message-
> From: Development On Behalf Of
> drwho
> Sent: Thursday, 7 November 2019 16:07
> To: development@qt-project.org
> Subject: Re: [Development]
07.11.2019, 18:08, "drwho" :
> On 2019-11-07 12:42 a.m., Thiago Macieira wrote:
>> On Wednesday, 6 November 2019 20:41:10 PST martin ribelotta wrote:
>>
>>> 4) What about the memory footprint?
>> A couple of megabytes.
>
> I'd love to see a build how too that results in a couple of megabytes.
On Thursday, 7 November 2019 16:06:41 CET drwho wrote:
> On 2019-11-07 12:42 a.m., Thiago Macieira wrote:
> > On Wednesday, 6 November 2019 20:41:10 PST martin ribelotta wrote:
> >> 4) What about the memory footprint?
> >
> > A couple of megabytes.
>
> I'd love to see a build how too that results
On 2019-11-07 12:42 a.m., Thiago Macieira wrote:
On Wednesday, 6 November 2019 20:41:10 PST martin ribelotta wrote:
4) What about the memory footprint?
A couple of megabytes.
I'd love to see a build how too that results in a couple of megabytes.
The smallest I've ever got Qt with a "cut ev
>> Yes, POSIX compliant base including pthreads and filesystem API. What the
>> filesystem API accesses is irrelevant, it just has to exist. Threading
>> support
>> is mandatory in Qt, even though there are #ifndef QT_NO_THREAD around.
>> Those
>> aren't tested and aren't guaranteed to even compi
On 7/11/19 3:42 PM, Thiago Macieira wrote:
On Wednesday, 6 November 2019 20:41:10 PST martin ribelotta wrote:
This question is in the air time to time but the information is very
disperse and not so convincent for me.
Actually in my understand, Qt need:
1) POSIX compliant base (pthreads? mma
On Wednesday, 6 November 2019 20:41:10 PST martin ribelotta wrote:
> This question is in the air time to time but the information is very
> disperse and not so convincent for me.
>
> Actually in my understand, Qt need:
>
> 1) POSIX compliant base (pthreads? mmap? fork?)
>
> I can disable parts i
Hi guys, I'm evaluate, for a client, the cost of port Qt to a bare
metal RTOS with minimal (realy minimal) requirements like freeRTOS,
mbedos etc (no mmu, no mmap, no filesystem, etc)
What is the minimal requirement to run Qt in a really minimal
platform? (for now, qt in my words is understand as c
> -Original Message-
> From: Development [mailto:development-
> bounces+kai.koehne=theqtcompany@qt-project.org] On Behalf Of ravi
> kumar verma
> Sent: Friday, February 26, 2016 3:41 PM
> To: development@qt-project.org
> Subject: [Development] porting
>
>
hi,
How do we port a Qt code from one platform to another ?
for eg . from windows to linux .
regards
Ravi Kumar Verma
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
On Oct 18, 2012, at 10:07 AM, Sorvig Morten wrote:
> According to git grep Qt 4 has 47 semi-public exported "qt_platform"
> functions offering platform-spesific functionality. Most platform code is now
> in plugins and can no longer export symbols. We need a plan for dealing with
> these in Qt
/me puts his fingers in his ears in advance of the deafening roar of
volunteers to get dirty with this task.
I personally love seeing the death of this kind of cruft, but you
probably have better things to do with your time and it would be nice
to see Qt 5 out and frolicking in the fields, replete
According to git grep Qt 4 has 47 semi-public exported "qt_platform" functions
offering platform-spesific functionality. Most platform code is now in plugins
and can no longer export symbols. We need a plan for dealing with these in Qt 5.
After a brief investigation these fall into several categ
@qt-project.org] On
Behalf Of Daniel Kreuter
Sent: 13. heinäkuuta 2012 14:57
To: development@qt-project.org
Subject: [Development] Porting my Qt4 application to Qt5 fails because
qtmaind.lib not found (windows)
Hi,
I'm porting my application to Qt5, but when compiling with msvc, he
comp
Hi,
I'm porting my application to Qt5, but when compiling with msvc, he
complains that he cannot open qtmaind.lib.
I used the latest build from Digia for compiling.
--
Mit freundlichen Grüßen
Greetings
Daniel Kreuter
___
Development mailing list
Dev
Hi there,
At Qt CS I hosted a session about the clang based tooling I wrote to automate
the boring parts of porting from Qt4+Qt3Support to Qt5.
http://www.kdab.com/automated-porting-from-qt-4-to-qt-5/
We discussed:
* The scope and limitations of the tool
- Works best for boring stuff, not
Hi,
On 25 June 2012 10:32, wrote:
> Hi Andrea,
>
> My response doesn't relate to EnvJs in particular, although it may be
> relevant.
>
> In general, support for JavaScript in QML is still lacking (examples:
> instanceof doesn't work properly, due to the dichotomy between C++
> inheritance and
opment-
> bounces+christopher.adams=nokia@qt-project.org] On Behalf Of ext
> a.gra...@gmail.com
> Sent: Monday, June 25, 2012 5:14 PM
> To: Stephen Kelly
> Cc: development@qt-project.org
> Subject: Re: [Development] Porting code from QScriptEngine (Qt4) to
> QJSEngine (Qt5)
>
Hi,
On 21 June 2012 17:18, Stephen Kelly wrote:
> On Thursday, June 21, 2012 15:33:19 a.gra...@gmail.com wrote:
>> I've started porting some code from QScriptEngine to QJSEngine, but
>> there are some missing parts I don't know how to implement.
>
> My understanding is that QJS* is not a replacem
On Thursday, June 21, 2012 15:33:19 a.gra...@gmail.com wrote:
> I've started porting some code from QScriptEngine to QJSEngine, but
> there are some missing parts I don't know how to implement.
My understanding is that QJS* is not a replacement for QScriptEngine:
http://thread.gmane.org/gmane.com
I've started porting some code from QScriptEngine to QJSEngine, but
there are some missing parts I don't know how to implement.
1) Here is the comparative "table":
- QScriptEngine --> QJSEngine
- QScriptValue --> QJSValue
- QScriptValueIterator --> QJSValueIterator
- QScriptContext --> ???
QScri
23 matches
Mail list logo
