@AliReza-Beytari

Ps. are you sure this works with 5.7 ?
Only Qt 5.6 is mentioned.

Check in the ndk whether you have gcc 4.8 available IIRC there was a change with r11.

HI, i'm interested in your code can you share it with me please?

@SGaist Yes I'll have another look at it. But when I was using 5.6 some of the OpenGL shader demos would not run under windows without a hand build Qt with the -opengl desktop option.

I have built 5.7 from the same git branch under linux with no drama. I'll try and do another build on a clean windows machine (my build environment may not be in the best shape).

Thanks.

My bad.

I was running config from qtcore and nor the project root!

Because QT_INSTALL_PLUGINS is defined at build time and is known to qmake.

As for the double $ problem, that's rather a question for the NodeBB folks

Finally, I found the reason. I had to add -Wl,-rpath,$(ROOTSYS)/lib to the end of the LIBS definition. So the solution is the following:

Add ROOTSYS to the Projects/Build Environment Add -Wl,-rpath,$(ROOTSYS)/lib to the libs.

The .pro file looks like this:

TEMPLATE = app win32 { QMAKE_CXXFLAGS += -FIw32pragma.h } CONFIG += qt warn_on thread INCLUDEPATH += $(ROOTSYS)/include win32:LIBS += -L$(ROOTSYS)/lib -llibCore -llibCint -llibRIO -llibNet \ -llibHist -llibGraf -llibGraf3d -llibGpad -llibTree \ -llibRint -llibPostscript -llibMatrix -llibPhysics \ -llibGui -llibRGL else:LIBS += -L$(ROOTSYS)/lib -lCore -lCint -lRIO -lNet \ -lHist -lGraf -lGraf3d -lGpad -lTree \ -lRint -lPostscript -lMatrix -lPhysics \ -lGui -lRGL -Wl,-rpath,$(ROOTSYS)/lib HEADERS += canvas.h SOURCES += canvas.cxx main.cxx

@SGaist Thx I will give it a try.

I am closing it as solved since the issue has been reported for bug-fixing and there are other options to make it work.

@jsulm I meant to change some configurations, if there are some, and fasten the compilation.

So if I choose the external resources step, is it feasible to do the following steps:

Can I integrate the rcc command that I have to execute manually in terminal, somehow to the make step of the application, so that it is executed automatically?

If I achieve the upper step, can I detect, whether the qrc was changed a new rcc compilation is necessary?

If you publish your app then you should use standard directories for documents/configuration (and NOT the directory where your app or Qt is installed!).
Should the user be able to edit that text file?
Does this file contain some predefined content?
If it does your app could generate this file if it is not there and write this predefined content into the file.
If user should be able to edit the file directly then you should store the file somewhere in its home directory ("My Documents" on Windows /home/USENAME on Linux). Else you can treat the file like a configuration file.
See here how to get paths to standard directories: http://doc.qt.io/qt-5/qstandardpaths.html

Glad you found out and thanks for sharing your findings !

Thanks for the link, I've forgotten that page.

What I usually do is an out of source build, so when there's something to change, you can just nuke the build folder and start fresh without to worry about what would need to be cleaned from the source tree.

Since you have it working now, please mark the thread as solved using the "Topic Tool" button so that other forum users may know a solution has been found :)

@Bart_Vandewoestyne said:

we're storing our Qt build in our version management system

This is a strange thing to do, since Qt guarantees binary compatibility between minor versions, but well, you're free to choose. Unfortunately, I don't see how you could decrease the size further, beside deleting the docs, as the libraries are in the /lib directory and they're the next biggest size. Maybe store only the libs that you're using, i.e. these that you're going to deploy. No point in keeping QtXml if you're not using it, right?

Hi,

Here you have the starting point to make your device usable for application development.

Hope it helps

Were you able to solve this issue? I ran into the same problem on a Virtual Machine with Ubuntu Server 14.04

Hi,

Glad you found out and thanks for sharing !

You can mark the thread as solved using the "Topic Tool" button :)

Hi,

Do you mean that if you build with MinGW-32 it's all working fine but not with MinGW-64 ?

Hi and welcome to devnet,

While it might be doable, I'd recommend using a build manager either CMake like suggested by @debian, QBS or qmake. You'll have an easier way to handle your project and its submodules (not to mention that it will also make your life easier if changing OS to build your project).

Note that you can use qmake for non-Qt project without a problem.