> > What is the best/designated way to supply relacement macros for those
> > symbols so the clang analysis succeeds? Is there some configuration/setting
> > in Qt Creator? Should I patch the code? Should I pass this to clang as
> > command line arguments?
>
> You should contribute the
I wouldn't call them OpenSource per-se. They were done for one reason or
another and released freely.
A Java thing I did for the family trucking company that I'm told quite a
few small trucking companies used back when fuel surcharges were
changing spastic like and difficult to calculate.
Sent from ProtonMail mobile
Original Message
On Dec 22, 2018, 1:05 PM, Roland Hughes wrote:
[snip]
Try porting it to a non-Linux platform where the C compiler only goes up
to the first half of C99.
[/snip]
Only Curious.. example of platform that is not Linux and only has
I would like to thank everyone who has been mentioning "alone" as a
criteria in here. We all go through that stage and some of us never
leave it. Definitely going to make a nice essay in my new book.
At some point we all buy into the fantasy of one developer alone
creating something fantastic
Should have done this a long time ago...
https://i.imgur.com/HmnchHN.png
So long and thanks for all the fish __
On 12/22/18, 9:53 AM, "Interest on behalf of Roland Hughes"
wrote:
On 12/21/2018 4:37 PM, Konstantin Tokarev wrote:
> 21.12.2018, 19:42, "Vlad Stelmahovsky":
>>
On 12/21/2018 4:37 PM, Konstantin Tokarev wrote:
21.12.2018, 19:42, "Vlad Stelmahovsky":
Nope, its only my guess based on short Dart code checking and some articles,
how it works
Google definitely aware about Qt, but its huge, so..
Note that declarative UI description languages were known
Sorry for asking again... I have not found a solution yet.
I tried to define the macros using #ifdef __clang__ / #endif but it seems
__clang__ is not
defined during code model parser run. Also all GCC smybols are defined so I can
not
disinguish clang from GCC.
I also tried to add a -D argument
