As I said earlier, very difficult to get the status ethernet using UDP. UDP is fire & forget protocol. You need to build your own mechanism to monitor the status. It could be simple TCP connection to see if the connection alive with remote server. If not you need to get the interfaces status periodically through QNetworkInterface & check if the interface is up. You can use QNetworkInterface::flags() & QNetworkInterface::IsUp to check the status.

@A123 said in New Errors when moving C++ code to QT Creator:

its been used by others for years and it worked perfectly AFAIK with gcc and clang before I started using qtcreator which complained.

Here's my guess: Previously, the assert() macro was disabled. This caused the illegal code to be effectively "commented out", so the compiler didn't detect it. After the migration, the assert() macro was no longer disabled, so the compiler now sees the bad code and (correctly) complains.

See http://www.cplusplus.com/reference/cassert/assert/. You could make your code work again by defining the NDEBUG macro, but be careful: This will disable all assert()s which might cause other errors to go undetected.

P.S. The compiler is the one that complained, not Qt Creator.

@jsmolka said in Trouble compiling files with identical filenames:

Is there any way to fix that and use multiple files with the same name inside my Qt project? Does it perhaps have something to do with the fact, that I am compiling into a bin dir inside my repository?

Not with shadow building, no. When you generate a bunch of object files in the same directory, the object is named after the source file. So the identically named source's object file will overwrite the previous one (in order of building); it may even happen only partially if you're building on multiple cores.
It's a known pitfall and you should name your files better as people have already suggested.

Define your variables via cpp.defines and use from C++.

@skylendar

you shortened the log, so I can't see the GDB version. Please check these.

Also, GDB must be python enabled, and last the python dumper script must be loaded. Have you checked the directories?

Regards

got solution from
https://asmaloney.com/2013/07/howto/packaging-a-mac-os-x-application-using-a-dmg/

example script:

echo "change the permision of .dmg file" hdiutil convert "SquidStat.dmg" -format UDRW -o "SquidStat_Rw.dmg" echo "mount it and save the device" DEVICE=$(hdiutil attach -readwrite -noverify "SquidStat_Rw.dmg" |egrep '^/dev/' |sed 1q |awk '{print $1}') sleep 2 echo "create the sysmbolic link to application folder" PATH_AT_VOLUME=/Volumes/..:..:out:Release:_SquidStat:SquidStat ## check Path inside cd /Volume/ pushd "$PATH_AT_VOLUME" ln -s /Applications popd echo "copy the background image in to package" mkdir "$PATH_AT_VOLUME"/.background cp backgroundImage.png "$PATH_AT_VOLUME"/.background/ echo "done" # tell the Finder to resize the window, set the background, # change the icon size, place the icons in the right position, etc. echo ' tell application "Finder" tell disk "../../out/Release/_SquidStat/SquidStat" ## check Path inside cd /Volume/ open set current view of container window to icon view set toolbar visible of container window to false set statusbar visible of container window to false set the bounds of container window to {400, 100, 1110, 645} set viewOptions to the icon view options of container window set arrangement of viewOptions to not arranged set icon size of viewOptions to 72 set background picture of viewOptions to file ".background:backgroundImage.png" set position of item "SquidStat.app" of container window to {160, 325} set position of item "Applications" of container window to {560, 320} close open update without registering applications delay 2 end tell end tell ' | osascript sync # unmount it hdiutil detach "${DEVICE}" rm -f "SquidStat.dmg" hdiutil convert "SquidStat_Rw.dmg" -format UDZO -o "SquidStat.dmg" rm -f "SquidStat_Rw.dmg" exit

Thank you so much for your helping

@aha_1980 : I just noticed something else: In the log file, there are lines saying "GDB 71101", presumably because it is using v7.11.1 (?!). But I have installed GDB v8.2 in both usr/bin and usr/local/bin. And I've set those locations in QtCreator's options pages for kits and for debuggers. There should be no way for QtCreator to find an older GDB version.

The GDB version in both usr/ folders above is 8.2, confirmed by running via terminal. And I did not find any older stray 7.11.1 versions that QtCreator could be picking up.

Another oddity. Is there any other options page where the GDB location needs to be set?

@Christian-Ehrlicher Thankyou It's Working

Figured out my issue. I just needed to instantiate a QQmlDebuggingEnabler object. Calling QtQml.QQmlDebuggingEnabler() before instantiating my QApplication was enough.

@jsulm we make an installation file for our combined system, including multiple programs sharing some but not other resources. we use an nsi script to manage this. usually works fine. I just missed updating some of the .dll files.

@Ratzz
Thanks for your references.

@J.Hilk
It works ! THANKS :-)

@jsulm
I got this, thanks

My bad, I misread from where the signal came from.

@sergsmi privet !
вы можете использовать QML Shape type : https://doc.qt.io/qt-5.11/qml-qtquick-shapes-shape.html

@Devopia53
It works! , Thanks.

@MikhailG thank u so much sir
i will try.

I know this is an old topic. But I stumbled upon this topic multiple times, but now I got CMake in QtCreator with Visual Studio 15 2017 working. But had to change a few things.

In the Qt kit, I choose:
CMake Generator
Generator: Visual Studio 15 2017 Win 64.
Extra generator: None
Platform: empty
Toolset: empty

CMake Configuration: only CMAKE_PREFIX_PATH:STRING=%{QT:QT_INSTALL_PREFIX}, removed the others

When generating a cmake project, I have to change the resulting Build Settings (for each build configuration).

CMAKE_BUILD_TYPE: Debug
CMAKE_CONFIGURATION_TYPES: Debug

Build steps: choose "ALL_BUILD" instead of "all"

For us this resulted in a working build using msbuild, which allows us to build Wix installers etc. as well, something that cannot be done with NMake Makefiles.

thanks !! . I will look into both of them

It is boost library issue. Looks like you are not using the capture method of boost properly . Look at some examples of boost and fix your issue.

@Paul-Colby Thanks

i myself did something like this :)

QVariantMap json_map; const QJsonDocument doc = QJsonDocument::fromJson(output); qDebug().noquote() << doc; qDebug().noquote() << doc.array(); foreach (auto value, doc.array()) { qDebug().noquote() << value; qDebug().noquote() << value.toObject(); qDebug().noquote() << value.toObject().value("name"); json_map["name"] = value.toObject().value("name").toString(); json_map["installed"] = value.toObject().value("installed").toBool(); json_map["id"] = value.toObject().value("id").toString(); json_map["filename"] = value.toObject().value("filename").toString(); }

@noone Would this be of any help to you? https://forum.qt.io/topic/79730/no-build-step-for-android

It seems this guy had the same problem and solved it with adding gradle.

Usually that error has to do with missing ndk/sdk or the more likely ant/gradle. Try running the build or deploy on the command line and see if it gives you more information.

SOLUTION

with the help of @mrjj i found solution. It's just that instructions were not clear on tutorial

Steps

get the Qt creator source : git clone --recursive https://code.qt.io/qt-creator/qt-creator.git

set qmake version . your qmake version should be close to the qt version you are using . for e.g. if you are building for 5.10 your qmake should also use 5.10.

you can set qmake version by

sudo mv /usr/lib/x86_64-linux-gnu/qt-default/qtchooser/default.conf /usr/lib/x86_64-linux-gnu/qt-default/qtchooser/default.conf_orig sudo vim /usr/share/qtchooser/my_Qt_5.10.0_Desktop_gcc_x64.conf <Qt_dir>/5.10.0/gcc_64/bin <Qt_dir>/5.10.0/gcc_64/lib ln -s /usr/share/qtchooser/my_Qt_5.10.0_Destop_gcc_x64.conf /usr/lib/x86_64-linux-gnu/qt-default/qtchooser/default.conf

check qmake by qmake --version

mkdir qt-creator-build
cd qt-creator-build
qmake ../qt-creator/qtcreator.pro

4. ``` cd qt-creator-build make qmake_all make -j <number-of-cpu-cores+1>

wait for some time . it will take long time to build.

now you have both source and build of Qt creator . Now just follow the wizard and point the qt soruce and build locations

build and run

voila !! \0/

@mranger90 said in sqlite commands not working in qt:

Apparently you can not directly access an SQLite database from a resource. There are some discussions about this, but I cant find the links right now.

Indeed, Qt resources are compiled into the executable (or standalone binary file) which is read-only. Good catch! :-)

@jsulm said in Qt creator cannot successfully start app built with custom built qt bundle on windows:

@farta clone means here cloning from Qt repository (git clone)

Thank you.
I never clone it from Qt repository.

There is no straightforward API for this. I see several possibilities:

custom painting in QQuickPaintedItem custom painting in QQuickItem custom painting via GL shaders custom painting in QML Canvas a set of 4 animated Rectangle components, simulating the line. An ugly solution, but probably the easiest to do

Perhaps BorderImage component can be forced to do an animation like that, but I doubt it.

@nour.m

if you mean here:
http://freetexthost.com/l5wzgtntzb
than no, you did not make the changes @aha_1980 told you to do

SOURCES += main.cpp mainwindow.cpp my_polyhedron.cpp myqglwidget.cpp HEADERS += mainwindow.h My_CGAL_Config.h My_Face_base.h My_Halfedge_base.h my_polyhedron.h My_Vertex_base.h myqglwidget.h

still mising \ at the end of the line

also you are adding the widgets module twice. I'm not sure in what that will result, but you should remove one

QT += core gui QT += widgets //remove me DEFINES += QT_DISABLE_DEPRECATED_BEFORE=0x000000 greaterThan(QT_MAJOR_VERSION, 4): QT += widgets

@SGaist, could You provide an example please - fixed mylibrary.pro? Thanks!

Don't @ the moderators unless you have an issue requiring moderation.

Depending on the content of your line edit, you can use toLatin1() or toUtf8() rather than making these two conversions.

@dokif Do you see the plug-in in QtCreator under "Help/About Plugins..."?

@hassene
Hi and welcome
Is there a reason you simply dont use a layout ?
To make it autofollow the size of window ?
if you place a QLabel on a form ( mainwindow.ui) , right click somewhere on
empty form, and select Layout menu and select layout, the label will follow maniform.
https://doc.qt.io/qt-5.10/examples-layouts.html

@aha_1980
Hi. As I know, qtcreator doesn't handle well with auto keyword. I wish another trick, when I put cursor onto a auto variable's call, such as

auto v = SomeClass(); v.func();

Cursor is at func(). I wish to use shortcut key to show the option list, just as the result that I move cursor to Locator and input

:m func

then it will give me a list where func appears.

Is there such a shortcut ? If it exists, it may improve my code-reading greatly

@GregWilsonLindberg
I think that the g++ version is what is doing it. The old version of rasbian
is using g++ v4.9.2. The new version of rasbian is using g++ v6.3.0-18+.
For the old compiler we had had to add an "INCLUDEPATH =
/usr/include" line into the .pro file to get everything picked up
properly. For the new compiler (and the change from #include to #include_next
in cstdlib) that messes up.
I'm removing the INCLUDEPATH, (which seems to have been included as -isystem
instead of -I) and that is fixing the problem.

@JonB I think i won't be able to understand something more detailled and that answer the whole questions =)

Thanks a lot, you ma real expert ! ;D