Updating Qt - where is the Linux install folder ?
-
I have used the above to fresh install Qt, unfortunately the successful install process did not let me select the Linux install folder.
Now no matter what I do I keep starting the old version and do not know WHERE is my new one.
Reboot did not help. -
Hi,
What exactly did you select when installing Qt using the online installer ?
-
@SGaist said in Updating Qt - where is the Linux install folder ?:
Hi,
What exactly did you select when installing Qt using the online installer ?
I used the default 'home/d/Qt" and after it finished selected "launch".
No launch.Just reinstalled in different folder and again selected launch.
No launch.So what is the actual QrCreator executable or am I NOT installing QtCreator at all ? Just Qt ??
-
Everything is under /home/d/Qt.
-
@SGaist Yes, that is the default folder. But none of the files , assuming they are executable , will run when prompted directly. Not even in another folder.
When I select "qtcreator" in terminal it will run the old version.
Apparently the installer did not or cannot finish the job and tell Linux where is the new version. I am not that fond of messing with existing stuff before I get the new one to work.I have only "Qt maintenance tool" - working , must be a add to new version, never seen before this install. Does not do much for me at this time, but runs.
-
@AnneRanch
OK, is it possible that AFTER I install new version I should implement Options -> Build and Run and "add" new qmake ?I did, however , should I also remove the original "auto-detected " qmake ?
It looks as changing to new QtVesion is actually done by changing the "qmake".
But I need confirmation before I screw things up.
BTW the maintenance tool appears to be the way to do the version update from now on. That is nice.
EDIT
I need to follow this -
@AnneRanch said in Updating Qt - where is the Linux install folder ?:
When I select "qtcreator" in terminal it will run the old version.
...
should I also remove the original "auto-detected " qmake ?
The auto-detected Qt 5.5.1 (and the old version of Qt Creator) was installed from your Linux repository.
The Qt online installer knows nothing about these old versions. Use your Linux software manager (
apt-get
or Ubuntu Software Center or GNOME Software) to remove the old versions.P.S. Your screenshot shows that you installed 2 copies of Qt 5.15.2 -- you should keep just 1 of them and remove the other.
-
Making progress....
-
@JKSH said in Updating Qt - where is the Linux install folder ?:
@AnneRanch said in Updating Qt - where is the Linux install folder ?:
When I select "qtcreator" in terminal it will run the old version.
...
should I also remove the original "auto-detected " qmake ?
The auto-detected Qt 5.5.1 (and the old version of Qt Creator) was installed from your Linux repository.
The Qt online installer knows nothing about these old versions. Use your Linux software manager (
apt-get
or Ubuntu Software Center or GNOME Software) to remove the old versions.Exactly what I was afraid of - one app knows zip about the other and
all this "automation" does not make it easy to correct stuff.OK, but why I cannot Remove it while in that form ?
OR
why "autodetect" cannot check WHICH version is newer ?
Don't files have a date stamp ?
I guess it would be too difficult to verify "who is on first" BY DATE.PS
There is no clear way to go from
"kit" to "qmake" .
It is OK , but one is not sure if one mistake doing "kit" wont screw something else.P.S. Your screenshot shows that you installed 2 copies of Qt 5.15.2 -- you should keep just 1 of them and remove the other.
I did .
Please see my next post and give me a hint what "environment" I forgot to change. Maybe "installer" did - changed my g++ ??
This is so much fun
-
@AnneRanch said in Updating Qt - where is the Linux install folder ?:
Please see my next post and give me a hint what "environment" I forgot to change. Maybe "installer" did - changed my g++ ??
The Qt installer does not touch g++. It doesn't install, upgrade, configure, or uninstall g++.
- Open a Terminal instance and run
g++ -v
from the console. What do you see? - Did you remove Qt 5.5.1?
why "autodetect" cannot check WHICH version is newer ?
Don't files have a date stamp ?
I guess it would be too difficult to verify "who is on first" BY DATE.It doesn't matter which files are newer or older. There are legitimate reasons to have multiple copies of Qt installed at the same time. For example, I might install both Qt 5.12.10 LTS and Qt 6.0.0 on the same machine -- the former maintaining a long-term project, and the latter for investigating the latest features.
The autodetector can't tell what you want to do with those versions, so it just detects them. It doesn't manage them.
- Open a Terminal instance and run
-
d@d-SATA:~$ g++ -v
Using built-in specs.
COLLECT_GCC=g++
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/5/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 5.4.0-6ubuntu1~16.04.12' --with-bugurl=file:///usr/share/doc/gcc-5/README.Bugs --enable-languages=c,ada,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-5 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-libmpx --enable-plugin --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-5-amd64/jre --enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-5-amd64 --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-5-amd64 --with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-objc-gc --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.12)
d@d-SATA:~$NO, I did not uninstall the older version.
Since I can have several versions on the machine , so why I cannot simply disable it ? BUT you asked if I uninstalled it, so that is not a real subject of discussion.Besides it now "runs" the new version, AFTER i changed the "options" - as it should . The issue is the g++ .
( I will post comments on the "enabling " options after I get this solved )
If installer did not touch it - why do I have to mess with it?I do not mind fixing the mess, but I am not impressed with a software which saiz " Launch ..." and it does not unless the "options" are modified.
So - the installer does not know beans about the older version, but screws up the g++.I am still not happy uninstalling the old version if THAT IS A REAL SOLUTION.
-
@AnneRanch One more silly question - what does "auto_detected" do if it does not detect the new version anyway ?
There is something missing in Qt logicUPDATE
no "Add subproject " option - grayed out - so the "Add project" cannot be verified!
It builds and runs. Of course cannot find executable, none was added ! -
Your screenshot shows that you are using the old version of Qt Creator, not your updated one.
- Delete
/home/d/CAT_MAIN/build-TEST_APP-Desktop-Debug/
- Delete
/home/d/CAT_MAIN/TEST_APP/TEST_APP.pro.user
- Launch your new version, which is at
/home/d/QT_5.15/Tools/QtCreator/bin/qtcreator
, and use that to build your project.
d@d-SATA:~$ g++ -v
Using built-in specs.
COLLECT_GCC=g++
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/5/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ...That's good. It shows that g++ is still working. It is not screwed up.
NO, I did not uninstall the older version.
Since I can have several versions on the machine , so why I cannot simply disable it ? BUT you asked if I uninstalled it, so that is not a real subject of discussion.I asked if you uninstalled it so that I can better understand your PC's environment. Knowing what you did or didn't do helps us to narrow down the possible causes of the problem.
I wasn't trying to discuss whether you should uninstall it or leave it.
Besides it now "runs" the new version, AFTER i changed the "options" - as it should . The issue is the g++ .
( I will post comments on the "enabling " options after I get this solved )
If installer did not touch it - why do I have to mess with it?I do not mind fixing the mess, but I am not impressed with a software which saiz " Launch ..." and it does not unless the "options" are modified.
So - the installer does not know beans about the older version, but screws up the g++.You can't conclude that the installer screwed up g++ when you haven't ruled out other possibilities.
- Delete
-
@JKSH said in Updating Qt - where is the Linux install folder ?:
Your screenshot shows that you are using the old version of Qt Creator, not your updated one.
Please look at the blue text and tell me how you determined I am running the old version.
The tools -> options allow for section of the version via qmake.
Running "qtcreator" from any folder still runs "qmake" selected in "options".
Please explain the logic behind uninstalling the old version ?
If i uninstall the old version of qt I will lose the ability to build ANY subdirs project - NOT AN OPTION . At least for now I can switch between versions and keep coding until I get the "Import external project" fixed .
And the deletion / uninstall, would defeat the purpose of tools -option - select version anyway.
- Delete
/home/d/CAT_MAIN/build-TEST_APP-Desktop-Debug/
- Delete
/home/d/CAT_MAIN/TEST_APP/TEST_APP.pro.user
- Launch your new version, which is at
/home/d/QT_5.15/Tools/QtCreator/bin/qtcreator
, and use that to build your project.
This launches the old version - as currently selected in tools -options.
d@d-SATA:~$ g++ -v
Using built-in specs.
COLLECT_GCC=g++
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/5/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ...That's good. It shows that g++ is still working. It is not screwed up.
NO, I did not uninstall the older version.
Since I can have several versions on the machine , so why I cannot simply disable it ? BUT you asked if I uninstalled it, so that is not a real subject of discussion.I asked if you uninstalled it so that I can better understand your PC's environment. Knowing what you did or didn't do helps us to narrow down the possible causes of the problem.
I wasn't trying to discuss whether you should uninstall it or leave it.
Besides it now "runs" the new version, AFTER i changed the "options" - as it should . The issue is the g++ .
( I will post comments on the "enabling " options after I get this solved )
If installer did not touch it - why do I have to mess with it?I do not mind fixing the mess, but I am not impressed with a software which saiz " Launch ..." and it does not unless the "options" are modified.
So - the installer does not know beans about the older version, but screws up the g++.You can't conclude that the installer screwed up g++ when you haven't ruled out other possibilities.
For now -since new version does NOT support building "sudirs" project and it does not look as having any new options to "import existing project " TO "SUBDIRS" ANYWAY let me close this thread and continue coding "subdirs" project using the old version.
Appreciate all contribution.
- Delete
-
@AnneRanch said in Updating Qt - where is the Linux install folder ?:
since new version does NOT support building "sudirs" project
Hang on. Building SUBDIRS projects is definitely supported by the latest versions of Qt and Qt Creator.
If you can't get it to work, ask a question about that instead.
Please look at the blue text and tell me how you determined I am running the old version.
Please understand the difference between Qt (the libraries) and Qt Creator (the IDE).
- The blue text shows that you're using the new version of Qt.
- The app logo shows that you're using the old version of Qt Creator.
You said that you were not impressed with having to modify options. Well, if you run the new version of Qt Creator, it would have auto-detected your new version of Qt so you wouldn't have needed to modify any options.
Running "qtcreator" from any folder still runs "qmake" selected in "options".
When you call
qtcreator
, you launch the old version of Qt Creator.When you call
/home/d/QT_5.15/Tools/QtCreator/bin/qtcreator
, you launch the new version of Qt Creator.Please explain the logic behind uninstalling the old version ?
If you don't need it, then uninstall it. If you still need it, then keep it.
Note: The only thing that I asked you to uninstall was the duplicate copy of Qt 5.15.2 -- there's no point in keeping 2 copies of the same thing.
-
I'm pretty sure Qt5.15 does not support this ancient Ubuntu: https://doc.qt.io/qt-5/supported-platforms.html
-
@Christian-Ehrlicher
I asked the OP previously a couple of times which Ubuntu version they are using, but never received a response. I do see what you mean now!