This provided some useful additional info, which I've attached below.
dNOTE: ENGINE RUN AND INFERIOR RUN OK
dState changed from EngineRunRequested(7) to InferiorRunOk(11)
dNOTE: ENGINE RUN AND INFERIOR RUN OK
dState changed from EngineRunRequested(7) to InferiorRunOk(11) [master]
dNOTE: INFERIOR STILL RUNNING IN STATE InferiorRunOk.
>~" received signal SIGSEGV, Segmentation fault.\n"
>~"0x0000000000000000 in ?? ()\n"
dNOTE: INFERIOR SPONTANEOUS STOP
dState changed from InferiorRunOk(11) to InferiorStopOk(14)
dNOTE: INFERIOR SPONTANEOUS STOP
dState changed from InferiorRunOk(11) to InferiorStopOk(14) [master]
dHANDLING SIGNAL SIGSEGV
sStopped: Segmentation fault (Signal SIGSEGV).
The GDB version that it found is version 7.12.0.
In that case, just create the folders in your project folder and in your .pro file:
SOURCES += \
or alternatively you can add a .pri file per subfolder that you will include in your main .pro file.
@Exotic_Devel said in Qt Creator external tools paths:
What about the problem with qmlviewer, can you give me any suggestions?
I honestly have no idea what that is. Looking in the qmlviewer.xml file, it seems to be related to Qt Quick 1, so likely a Qt 4 remnant.
@AnneRanch said in Missing (#include) "ui_device.h" ?:
Perhaps there is an official way to do "version control" within IDE.
You can use several version control tools with QtCreator, like Git, Subversion, Mercurial and CVS.
After few dead ends I found an older discussion which stated that "qtconnecetivity" examples are somewhat "unusable" in qt5.
I have no intention to "go backwards" to previous versions of qtx and did not keep the compiler errors in case somebody really wants to know why it did not compile in qt5. It was missing some "configure" reference.
So - at this point I shall go back to trying to cobble my own "example" and just use "qtconnectivinty" examples as a template code.
It might be of interest and would likely benefit from a plugin in Qt Creator. However the first step would be to have it build various Qt project types.
Note that cmake won't be transitional. It's going to be the build system of Qt 6 and thus it's going to stay like this for the whole Qt 6 lifetime at least. Just take a look at the lifetime of qmake.
@CoBo said in QtCreator constantly "forgetting" CMake property settings:
I'm no CMake user yet, and I know nothing about the CMake integration in Creator, but nevertheless want to add my two cent before you got other answers - maybe from the developers on the mailing list.
Well, in simple cases it actually does respect existing CMakeCache files, but it looks like in more complex projects it tends to "give up" - and drops everything!
Ok, so best would be you have an example CMakeCache file that exhibits that behavior, so the developers can reproduce it.
And there is for me no reason why this should be some extra because the entire cmake processing is done in the background by the cmake tool anyway: why reinvent the wheel?
Yeah, the build is done by CMake, but Creator needs information about the project: which files are involved, which build targets, which compiler flags etc.
Tradionally, that area was not covered by CMake, it slowly moves in that direction and Qt developers sent patches to CMake to improve the situation.
So as I said above: if you have clear examples of what is not working: tell them. And after all, Creator is an open source project, so adding some GUI to set up CMake parameter can also be done by external contributors (hint, hint, hint!)
so I can also easily imagine that a QtCreator project setup has the potential to be clearly better than cmake-gui. But that is so far just my dreaming!
Let's hope that dream come true. After all, we will have much more CMake users the next years.
@Mariana-Meireles yeah, such things sometimes happen after Creator updates. The sledgehammer solution is to quit Creator, delete the .pro.user and the build directories, and the restart Creator.
But your solution should work too.
Hi @aha_1980 ,
yes the store provides V2.4.1.
The error happened to other people before: "The 'ProviderPackage' package did not load correctly." This leads to a slower startup of VS and the QT VS Tool button to be stuck on "initializing".
https://stackoverflow.com/questions/16176933/the-providerpackage-package-did-not-load-correctly/19428110 (even though QT might not have been the root of the issue in this particular thread)
I actually proceeded to install older versions, f-ing up my VS. I re-installed it, tried 2.4.1 again and the Error above happened again.
I again installed older versions using the command line interface of the VSIXInstaller. V2.3.0 happened to work. As this costed me a couple of hours I stopped there, not further investigating on the error. I can however provide the install-log of V2.4.1 if anyone of the QT-Team is interested.
As it works now, I consider this case closed. I will stay on V2.3.0 for the sake of my mental health. If this really is a compatibility issue, a compatible Version table should be uploaded somewhere.
Cheers and thank you nevertheless @aha_1980 ,
are you using the MSVC or MinGW compiler and which version?
For me with Creator 4.10 and Qt 5.12.4 MinGW 32 bit both Run and Debug print the messages to the Application Output.
Only difference is, that on Debug the output is black while on Run it violet.
Theoretical it could work but ...
QtDesignStudio uses a different settings directory path
we as the QtDesignStudio developers decided not to go the hassle to support every possible platform for preview stuff
QtCreator itself has also the Build->Preview menu entry so you can try to make it work on your own in QtCreator
but we see the need to share stuff with people at there mobile devices or even devices without any installed Qt
For that, we are preparing a QmlProjector which is basically a running Qt in a browser which can understand packed resources.
a first version can be seen here: qmlprojector
work is still in progress, but if we are ready we will show a blog post about it. Try it out and if there are issues use jira so we can reply in structured way.
@kshegunov said in Building of some projects with subdirs template in creator:
@koahnig said in Building of some projects with subdirs template in creator:
Is it because of duplication between object files of complete and leaf projects?
Sort of, it imports the command line configuration for the output directories and such. So in the end it behaves pretty much as what you'd expect by building through the shell. Also it helps to make sure each project references the proper kit, read Qt version, (i.e. the one used when you build from the command line).
OK, that seems to work for me as well.
Is there any relevant documentation available? Searching for some without success.
There is in the left pane this
which I used. But in the right window there is also
They end in the same folder which cannot be chosen in my case. It has to be the shadow build folder resp the relevant branch in that case.
There might be special condition since I try to separate source and shadow build folders as much as possible. The reason is internal, in addition I am using a RAM folder as shadow for a while.
@kshegunov Thanks for the hint it is really helpful.
thanks for your comment - I fully agree that this looks like a missing piece.
I suggest you bring this topic up to the Qt Creator mailing list or create a suggestion at bugreports.qt.io (In that case - please post a link here so others can follow).
@oldthrasher Did you try to fix the string for calling Open ?
newWorkbooks->dynamicCall("Open(const QString&)", newPath);
But anyway I see nothing in your code to write the data in the new file created. You are calling Add without any argument.
You need to loop on data to write them on the new excel file. BTW It could be more efficient to open the new excel file before the loop and then filling it with data at the same time you are reading them from the source file.