The Lounge

Cool, I'm glad that it worked.
Just to be clear,<string.h> is the C strings library (has strcpy(), memcmp() and the likes). The C++ equivalent for this is <cstring>.
None of these have the C++ type std::string, which requires <string>, so the fact that it worked when compiling was not due to the <string.h> include. It just pulled <string> from somewhere.

I can only recommend you to comment and vote for QTCREATORBUG-21407. It also contains a workaround to start one Creator without Clang.

Maybe we should also create a poll here in the forum to see how many users are affected by Clang problems and how they work around those.

Regards

Hi and welcome to devnet,

Licenses and platforms are not related. What is GPL on Linux will also be on macOS, Windows and all other supported platforms. Qt provides the same set of tools on all supported platforms.

In Qt Creator 4.8 we introduce an experimental client for the "Language Server Protocol".
http://blog.qt.io/blog/2018/10/11/qt-creator-4-8-beta-released/

Looks like there is at least some language server for Ada (https://github.com/reznikmm/ada-lsp, state unknown to me). That might work in our language client in Qt Creator 4.8.
For highlighting you'll also need to install the highlighting spec file for Ada, Tools > Options > Text Editor > Generic Highlighter > Download definitions, find Ada and download.

Regarding QtAda and integration with Qt in other ways, no idea.

@Mr_Ada you may be interested in Qt5Ada, see this announcement

Let's put it this way: if there is a limit, I haven't hit it, so you're good for quite a while.

Main Screen

Sorry, I just want to try the formatting

Bold Italic
List:

list item 1 list item 2

No..no..no

www.example.com

int main( int argc, char * argv[] ) { cout << "Hello world" << endl; }

Normal text
picture test

@Afsha

If you have a real Qt question, you can post it e.g. "General and Desktop".

If you want to spam do it somewhere else or better get a decent hobby.

AFAIK the automotive offering comes with Boot2Qt which will automatically bake a Linux distro with Qt and deploy it to target board. When doing embedded development, people tend to compile everything themselves anyway. Actually having to follow a guide on how to cross-compile Qt for Raspberry Pi is a good exercise to train for more "hardcore" embedded development.

I'm not saying I'm against something prebuilt for Raspbian, but I don't think it's a high priority target,. And, as Sam already pointed out - Qt team already has to go through considerable effort to prepare current package roster.

@mzimmers said in Showdown! Qt vs. LabVIEW:

difficult to quantify, but nonetheless important:

Qt gets it.

+1

Back when I was trying out GTK and Qt, I felt the difference immediately.

With Qt Creator, we can definitely tell that Qt engineers eat their own dogfood!

Thanks for the reply and suggestion.

@J.Hilk
That is very pretty! But, no, it was not just a question of writing QED. I refer you to the quote I pasted above, where you can see that another person has the same recollection as I have about some very specific wording we were made to use, which we have now forgotten. It was something about what we had to write for the move to generalise from 1/k/k + 1 to n. And something similar in the way of "special wording" when we talked about the confidence-relationship between x-bar & mu in statistics....

I've been using the Qt IDE for several years, and have watched the goings on in Qt-land.

I'd agree that US adoption of the Qt framework seems to lag that in other tech-savvy nations. This could be due to Microsoft's stranglehold on the US Fortune 500, or the relative lack of interest in the write-once, build-anywhere paradigm that is Qt's main selling point. In any event, I imagine it's going to be awhile before Qt becomes a household word in the US.

Sure hope I'm wrong...

HI and welcome to devnet,

Do you have any presentation about your project ?

www.qtcentre.org/threads/69407-Forum-captcha-broken