I thought I would get started with TDE programming, so I'm following the steps in the Wiki Development section, "Qt Designer and KDevelop 3.0 for Beginners". I followed the steps for creating the HelloWorld program substituting TDevelop for KDevelop, and all went well until the Project Build step, which failed, producing this output:
| cd '/home/development/TDEupdAlt/debug' && WANT_AUTOCONF_2_5="1" WANT_AUTOMAKE_1_6="1" LC_MESSAGES="C" LC_CTYPE="C" gmake -k | gmake all-recursive | gmake[1]: Entering directory '/home/development/TDEupdAlt/debug' | Making all in doc | gmake[2]: Entering directory '/home/development/TDEupdAlt/debug/doc' | Making all in . | gmake[3]: Entering directory '/home/development/TDEupdAlt/debug/doc' | gmake[3]: Nothing to be done for 'all-am'. | gmake[3]: Leaving directory '/home/development/TDEupdAlt/debug/doc' | Making all in en | gmake[3]: Entering directory '/home/development/TDEupdAlt/debug/doc/en' | /opt/trinity/bin/meinproc --check --cache index.cache.bz2 /home/development/TDEupdAlt/doc/en/index.docbook | gmake[3]: Leaving directory '/home/development/TDEupdAlt/debug/doc/en' | gmake[2]: Leaving directory '/home/development/TDEupdAlt/debug/doc' | Making all in po | gmake[2]: Entering directory '/home/development/TDEupdAlt/debug/po' | gmake[2]: Nothing to be done for 'all'. | gmake[2]: Leaving directory '/home/development/TDEupdAlt/debug/po' | Making all in src | gmake[2]: Entering directory '/home/development/TDEupdAlt/debug/src' | g++ -DHAVE_CONFIG_H -I. -I/home/development/TDEupdAlt/src -I.. -I/opt/trinity/include/tde -I/usr/include/tqt3 -I. -include tqt.h -DTQT_THREAD_SUPPORT -D_REENTRANT -Wno-long-long -Wundef -D_DEFAULT_SOURCE -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -fno-builtin -g3 -fno-inline -O0 -g3 -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -I/usr/include/tqt -MT main.o -MD -MP -MF .deps/main.Tpo -c -o main.o /home/development/TDEupdAlt/src/main.cpp | mv -f .deps/main.Tpo .deps/main.Po | /usr/bin/tmoc /home/development/TDEupdAlt/src/tdeupdalt.h -o tdeupdalt.moc | g++ -DHAVE_CONFIG_H -I. -I/home/development/TDEupdAlt/src -I.. -I/opt/trinity/include/tde -I/usr/include/tqt3 -I. -include tqt.h -DTQT_THREAD_SUPPORT -D_REENTRANT -Wno-long-long -Wundef -D_DEFAULT_SOURCE -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -fno-builtin -g3 -fno-inline -O0 -g3 -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -I/usr/include/tqt -MT tdeupdalt.o -MD -MP -MF .deps/tdeupdalt.Tpo -c -o tdeupdalt.o /home/development/TDEupdAlt/src/tdeupdalt.cpp | mv -f .deps/tdeupdalt.Tpo .deps/tdeupdalt.Po | /bin/sh ../libtool --tag=CXX --mode=link g++ -Wno-long-long -Wundef -D_DEFAULT_SOURCE -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -fno-builtin -g3 -fno-inline -O0 -g3 -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -I/usr/include/tqt -R /opt/trinity/lib64 -R /opt/trinity/lib64 -R /usr/lib64 -R /usr/lib64 -L/opt/trinity/lib64 -L/usr/lib64 -ltqt-mt -lz -lpng -lz -lm -lXext -lX11 -lSM -lICE -ltqt -lpthread -ltdecore -ltdeui -ltdeparts -o tdeupdalt main.o tdeupdalt.o -ltdeui | ../libtool: line 1300: func_opt_split: command not found | libtool: Version mismatch error. This is libtool 2.2.6b Debian-2.2.6b-2ubuntu1, but the | libtool: definition of this LT_INIT comes from libtool 2.4.6. | libtool: You should recreate aclocal.m4 with macros from libtool 2.2.6b Debian-2.2.6b-2ubuntu1 | libtool: and run autoconf again. | gmake[2]: Leaving directory '/home/development/TDEupdAlt/debug/src' | gmake[2]: *** [Makefile:629: tdeupdalt] Error 63 | gmake[2]: Target 'all' not remade because of errors. | gmake[2]: Entering directory '/home/development/TDEupdAlt/debug' | gmake[2]: Leaving directory '/home/development/TDEupdAlt/debug' | gmake[1]: Leaving directory '/home/development/TDEupdAlt/debug' | gmake[1]: *** [Makefile:582: all-recursive] Error 1 | gmake: *** [Makefile:500: all] Error 2 | *** Exited with status: 2 ***
All went well until libtool was invoked, and I have to suppose that TDevelop is (or thinks it is) using embedded libraries? because 1) I'm running on openSUSE, not Debian ubuntu, and 2) my current installed libtool is
|@17:51:37 root@pinto | wd=~ | ● rpm -q libtool | libtool-2.4.6-150000.3.6.2.x86_64 | rc=0
Am I going to have to download TDevelop and compile it on my system?
Leslie
J Leslie Turriff via tde-devels wrote:
I thought I would get started with TDE programming, so I'm following the steps in the Wiki Development section, "Qt Designer and KDevelop 3.0 for Beginners". I followed the steps for creating the HelloWorld program substituting TDevelop for KDevelop, and all went well until the Project Build step, which failed, producing this output:
Hi, unfortunately this is a lot of work to update to the latest TDE build workflow and I am not sure if someone did something about it. TDE is moving to cmake and ninja is used to speed up the builds. There are also the build scripts in the repository. With those scripts you can build the whole TDE or parts of it. When I started working with TDE (I must thank here Michele and Slavek for supporting me) I setup Eclipse (with the C++ view). In Eclipse I setup the paths of the target (I build in chroot), so that Eclipse can handle the includes. This way one can get information about functions and classes from the include files. As I build in chroot, I can not take advantage of the Eclipse build modules and run the commands manually in the chroot. I would still use TDevelop and especially the UI creator to inspect or create ui files.
I hope it helps
Anno domini 2024 Tue, 28 May 23:45:22 -0500 J Leslie Turriff via tde-devels scripsit:
I thought I would get started with TDE programming, so I'm following the steps in the Wiki Development section, "Qt Designer and KDevelop 3.0 for Beginners". I followed the steps for creating the HelloWorld program substituting TDevelop for KDevelop, and all went well until the Project Build step, which failed, producing this output:
| cd '/home/development/TDEupdAlt/debug' && WANT_AUTOCONF_2_5="1" WANT_AUTOMAKE_1_6="1" LC_MESSAGES="C" LC_CTYPE="C" gmake -k | gmake all-recursive | gmake[1]: Entering directory '/home/development/TDEupdAlt/debug' | Making all in doc | gmake[2]: Entering directory '/home/development/TDEupdAlt/debug/doc' | Making all in . | gmake[3]: Entering directory '/home/development/TDEupdAlt/debug/doc' | gmake[3]: Nothing to be done for 'all-am'. | gmake[3]: Leaving directory '/home/development/TDEupdAlt/debug/doc' | Making all in en | gmake[3]: Entering directory '/home/development/TDEupdAlt/debug/doc/en' | /opt/trinity/bin/meinproc --check --cache index.cache.bz2 /home/development/TDEupdAlt/doc/en/index.docbook | gmake[3]: Leaving directory '/home/development/TDEupdAlt/debug/doc/en' | gmake[2]: Leaving directory '/home/development/TDEupdAlt/debug/doc' | Making all in po | gmake[2]: Entering directory '/home/development/TDEupdAlt/debug/po' | gmake[2]: Nothing to be done for 'all'. | gmake[2]: Leaving directory '/home/development/TDEupdAlt/debug/po' | Making all in src | gmake[2]: Entering directory '/home/development/TDEupdAlt/debug/src' | g++ -DHAVE_CONFIG_H -I. -I/home/development/TDEupdAlt/src -I.. -I/opt/trinity/include/tde -I/usr/include/tqt3 -I. -include tqt.h -DTQT_THREAD_SUPPORT -D_REENTRANT -Wno-long-long -Wundef -D_DEFAULT_SOURCE -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -fno-builtin -g3 -fno-inline -O0 -g3 -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -I/usr/include/tqt -MT main.o -MD -MP -MF .deps/main.Tpo -c -o main.o /home/development/TDEupdAlt/src/main.cpp | mv -f .deps/main.Tpo .deps/main.Po | /usr/bin/tmoc /home/development/TDEupdAlt/src/tdeupdalt.h -o tdeupdalt.moc | g++ -DHAVE_CONFIG_H -I. -I/home/development/TDEupdAlt/src -I.. -I/opt/trinity/include/tde -I/usr/include/tqt3 -I. -include tqt.h -DTQT_THREAD_SUPPORT -D_REENTRANT -Wno-long-long -Wundef -D_DEFAULT_SOURCE -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -fno-builtin -g3 -fno-inline -O0 -g3 -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -I/usr/include/tqt -MT tdeupdalt.o -MD -MP -MF .deps/tdeupdalt.Tpo -c -o tdeupdalt.o /home/development/TDEupdAlt/src/tdeupdalt.cpp | mv -f .deps/tdeupdalt.Tpo .deps/tdeupdalt.Po | /bin/sh ../libtool --tag=CXX --mode=link g++ -Wno-long-long -Wundef -D_DEFAULT_SOURCE -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -fno-builtin -g3 -fno-inline -O0 -g3 -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -I/usr/include/tqt -R /opt/trinity/lib64 -R /opt/trinity/lib64 -R /usr/lib64 -R /usr/lib64 -L/opt/trinity/lib64 -L/usr/lib64 -ltqt-mt -lz -lpng -lz -lm -lXext -lX11 -lSM -lICE -ltqt -lpthread -ltdecore -ltdeui -ltdeparts -o tdeupdalt main.o tdeupdalt.o -ltdeui | ../libtool: line 1300: func_opt_split: command not found | libtool: Version mismatch error. This is libtool 2.2.6b Debian-2.2.6b-2ubuntu1, but the | libtool: definition of this LT_INIT comes from libtool 2.4.6. | libtool: You should recreate aclocal.m4 with macros from libtool 2.2.6b Debian-2.2.6b-2ubuntu1 | libtool: and run autoconf again. | gmake[2]: Leaving directory '/home/development/TDEupdAlt/debug/src' | gmake[2]: *** [Makefile:629: tdeupdalt] Error 63 | gmake[2]: Target 'all' not remade because of errors. | gmake[2]: Entering directory '/home/development/TDEupdAlt/debug' | gmake[2]: Leaving directory '/home/development/TDEupdAlt/debug' | gmake[1]: Leaving directory '/home/development/TDEupdAlt/debug' | gmake[1]: *** [Makefile:582: all-recursive] Error 1 | gmake: *** [Makefile:500: all] Error 2 | *** Exited with status: 2 ***
All went well until libtool was invoked, and I have to suppose that TDevelop is (or thinks it is) using embedded libraries? because 1) I'm running on openSUSE, not Debian ubuntu, and 2) my current installed libtool is
|@17:51:37 root@pinto | wd=~ | ● rpm -q libtool | libtool-2.4.6-150000.3.6.2.x86_64 | rc=0
Am I going to have to download TDevelop and compile it on my system?
Leslie
Welcome to the club. I dropped tdevelop and use kate + Makefile, which works quite nice. I think you could reuse the template applications to get started. But I don't make GUI applications any more, all stuff is moved to webinterface or tui+http/telnet-server --> my stuff is more barebones than it used to be :)
Nik
J Leslie Turriff via tde-devels wrote:
tdeupdalt main.o tdeupdalt.o -ltdeui | ../libtool: line 1300: func_opt_split: command not found | libtool: Version mismatch error. This is libtool 2.2.6b Debian-2.2.6b-2ubuntu1, but the | libtool: definition of this LT_INIT comes from libtool 2.4.6. | libtool: You should recreate aclocal.m4 with macros from libtool 2.2.6b Debian-2.2.6b-2ubuntu1 | libtool: and run autoconf again. | gmake[2]: Leaving directory '/home/development/TDEupdAlt/debug/src'
regarding the error it is obvious that it comes from automake process trying libtool and it seems there is version mismatch. I don't know if you know automake tools. If not you should read about them first.
On Wednesday 29 May 2024 02:05:22 deloptes via tde-devels wrote:
J Leslie Turriff via tde-devels wrote:
tdeupdalt main.o tdeupdalt.o -ltdeui
| ../libtool: line 1300: func_opt_split: command not found | libtool: Version mismatch error. This is libtool 2.2.6b
Debian-2.2.6b-2ubuntu1, but the
| libtool: definition of this LT_INIT comes from libtool 2.4.6. | libtool: You should recreate aclocal.m4 with macros from libtool 2.2.6b
Debian-2.2.6b-2ubuntu1
| libtool: and run autoconf again. | gmake[2]: Leaving directory '/home/development/TDEupdAlt/debug/src'
regarding the error it is obvious that it comes from automake process trying libtool and it seems there is version mismatch. I don't know if you know automake tools. If not you should read about them first.
Heh. All of my skills are in the IBM mainframe arena. I know a teeny bit about C++ and make, but beyond that I'm clueless; but I'd like to learn, if only I could find a mentor.
Leslie -- Platform: Linux Distribution: openSUSE Leap 15.5 - x86_64 Desktop Environment: Trinity Qt: 3.5.0 TDE: R14.1.2 tde-config: 1.0
Anno domini 2024 Wed, 29 May 03:22:20 -0500 J Leslie Turriff via tde-devels scripsit:
On Wednesday 29 May 2024 02:05:22 deloptes via tde-devels wrote:
J Leslie Turriff via tde-devels wrote:
tdeupdalt main.o tdeupdalt.o -ltdeui
| ../libtool: line 1300: func_opt_split: command not found | libtool: Version mismatch error. This is libtool 2.2.6b
Debian-2.2.6b-2ubuntu1, but the
| libtool: definition of this LT_INIT comes from libtool 2.4.6. | libtool: You should recreate aclocal.m4 with macros from libtool 2.2.6b
Debian-2.2.6b-2ubuntu1
| libtool: and run autoconf again. | gmake[2]: Leaving directory '/home/development/TDEupdAlt/debug/src'
regarding the error it is obvious that it comes from automake process trying libtool and it seems there is version mismatch. I don't know if you know automake tools. If not you should read about them first.
Heh. All of my skills are in the IBM mainframe arena. I know a teeny bit about C++ and make, but beyond that I'm clueless; but I'd like to learn, if only I could find a mentor.
I brought this up some months (or maybe years) ago on the list, so you should find it in the archive when you search for libtool and tdevelop or so. tdevelop does not use the autotool templates from your system, but has a rather old version boundled. You can replace the files in question with your correct version from your distribution, but these changes will be gone with the next update.
Nik
Leslie
Platform: Linux Distribution: openSUSE Leap 15.5 - x86_64 Desktop Environment: Trinity Qt: 3.5.0 TDE: R14.1.2 tde-config: 1.0
tde-devels mailing list -- devels@trinitydesktop.org To unsubscribe send an email to devels-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/devels@trinitydeskt...
-- Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ...
J Leslie Turriff via tde-devels wrote:
Heh. All of my skills are in the IBM mainframe arena. I know a teeny bit about C++ and make, but beyond that I'm clueless; but I'd like to learn, if only I could find a mentor.
May be asking here is the best and fingers crossed to get someone to help. I can share my experience, but I had already a background in C/C++. Unfortunately as mentioned TDevelop tools are not fully working - I mean the build functionality. May be someone can share the experience.
What you need to know for the starter is 1. C/C++ (introduction - there are good books also online) 2. make and cmake, but some projects still use automake and outside of TDE automake is widely used 3. you need a build environment based on your preferences. 4. go through some examples to get an idea how it works. For example I wrote few years ago some examples how to use DBus (dbus-1tqt) https://mirror.git.trinitydesktop.org/gitea/deloptes/dbus-1-tqt-example This is pretty simple and does not need any automake or cmake. The build is in the shell script - so you will find out how to compile simple binary There are also other examples on the WIKI 5. in the repo there are the Debian build scripts by Michele, however he is using another build system and I wrote my own build system based on make files, but you are using OpenSUSE (RPMs), so might be not of any advantage for you
On Wednesday 29 May 2024 05:44:54 deloptes via tde-devels wrote:
J Leslie Turriff via tde-devels wrote:
Heh. All of my skills are in the IBM mainframe arena. I know a teeny bit about C++ and make, but beyond that I'm clueless; but I'd like to learn, if only I could find a mentor.
May be asking here is the best and fingers crossed to get someone to help. I can share my experience, but I had already a background in C/C++. Unfortunately as mentioned TDevelop tools are not fully working - I mean the build functionality. May be someone can share the experience.
What you need to know for the starter is
- C/C++ (introduction - there are good books also online)
- make and cmake, but some projects still use automake and outside of TDE
automake is widely used 3. you need a build environment based on your preferences. 4. go through some examples to get an idea how it works. For example I wrote few years ago some examples how to use DBus (dbus-1tqt) https://mirror.git.trinitydesktop.org/gitea/deloptes/dbus-1-tqt-example This is pretty simple and does not need any automake or cmake. The build is in the shell script - so you will find out how to compile simple binary There are also other examples on the WIKI 5. in the repo there are the Debian build scripts by Michele, however he is using another build system and I wrote my own build system based on make files, but you are using OpenSUSE (RPMs), so might be not of any advantage for you
That's right; and learning stuff like make, let alone automake and cmake, is incredibly frustrating for me because tutorials all seem to go from the trivial Hello World level straight to levels that I find incomprehensible. I guess I will go back and read again the old QT3 Development book, which IIRC covers designing GUIs manually; but right now, TDevelop seems useless, failing with this library incompatibility error; and the Designer crashing outright.
Leslie
J Leslie Turriff via tde-devels wrote:
That's right; and learning stuff like make, let alone automake and cmake, is incredibly frustrating for me because tutorials all seem to go from the trivial Hello World level straight to levels that I find incomprehensible. I guess I will go back and read again the old QT3 Development book, which IIRC covers designing GUIs manually; but right now, TDevelop seems useless, failing with this library incompatibility error; and the Designer crashing outright.
The examples on the WIKI are also good. I remember I went through them. Designer was causing me troubles as well and I recall there are bug reports in TGW, but no one has the time to repair. I am pretty happy with Eclipse. I have it installed and setup in 2018. I am afraid to touch it (upgrade etc), because it is working very well. I can only recommend. It has plugins for cmake as well and can autobuild.
You need to know besides the language itself C/C++ also some basics - how include works, how build works (g++). To make life easier, people created first automake and then cmake. Then you have the packaging system for the distro. So when you write code you have the short way - to run g++ from the command line with all the options, or to use one of the build systems. If you want to create a package, you must use the packaging system on top of the former. It just takes time to sync in, so do a little step every day
J Leslie Turriff via tde-devels wrote:
That's right; and learning stuff like make, let alone automake and cmake, is incredibly frustrating for me because tutorials all seem to go from the trivial Hello World level straight to levels that I find incomprehensible.
Did you read this?
https://wiki.trinitydesktop.org/Category:Developers
On Thursday 30 May 2024 10:43:01 deloptes via tde-devels wrote:
J Leslie Turriff via tde-devels wrote:
That's right; and learning stuff like make, let alone automake and cmake, is incredibly frustrating for me because tutorials all seem to go from the trivial Hello World level straight to levels that I find incomprehensible.
Did you read this?
Yes. Lots of stuff there; hard to determine where to start. I read https://wiki.trinitydesktop.org/Qt_Designer_and_KDevelop_3.0_for_Beginners and tried to follow its instructions, which is what prompted me to start this thread. From other comments on this thread, it seems that this Beginners page is at best misleading. Maybe instead there should be a page about useful IDEs?
Leslie -- Platform: Linux Distribution: openSUSE Leap 15.5 - x86_64 Desktop Environment: Trinity Qt: 3.5.0 TDE: R14.1.2 tde-config: 1.0
J Leslie Turriff via tde-devels wrote:
Yes. Lots of stuff there; hard to determine where to start. I read https://wiki.trinitydesktop.org/Qt_Designer_and_KDevelop_3.0_for_Beginners and tried to follow its instructions, which is what prompted me to start this thread. From other comments on this thread, it seems that this Beginners page is at best misleading. Maybe instead there should be a page about useful IDEs?
This would work for KDE3 presumably, because it says KDevelop 3.0 and not TDevelop. I wouldn't say it is misleading. However I agree that it is hard to learn as a beginner.
On Friday 31 May 2024 03:31:10 deloptes via tde-devels wrote:
J Leslie Turriff via tde-devels wrote:
Yes. Lots of stuff there; hard to determine where to start. I read https://wiki.trinitydesktop.org/Qt_Designer_and_KDevelop_3.0_for_Beginner s and tried to follow its instructions, which is what prompted me to start this thread. From other comments on this thread, it seems that this Beginners page is at best misleading. Maybe instead there should be a page about useful IDEs?
This would work for KDE3 presumably, because it says KDevelop 3.0 and not TDevelop. I wouldn't say it is misleading. However I agree that it is hard to learn as a beginner.
I'm currently exploring use of classic Qt tools (tqtdeveloper, tqmake, etc.) and will continue this discussion in future as necessary. I will also look into how this is done using cmake instead.
Interestingly, though the Kdevelop tools seem to be broken in various ways, so far the tqt tools are working. (I was a bit surprised to find them in /usr/bin instead of /opt/trinity/bin...)
Leslie
On Wednesday 29 May 2024 05:44:54 deloptes via tde-devels wrote:
J Leslie Turriff via tde-devels wrote:
Heh. All of my skills are in the IBM mainframe arena. I know a teeny bit about C++ and make, but beyond that I'm clueless; but I'd like to learn, if only I could find a mentor.
May be asking here is the best and fingers crossed to get someone to help. I can share my experience, but I had already a background in C/C++. Unfortunately as mentioned TDevelop tools are not fully working - I mean the build functionality. May be someone can share the experience.
What you need to know for the starter is
- C/C++ (introduction - there are good books also online)
- make and cmake, but some projects still use automake and outside of TDE
automake is widely used 3. you need a build environment based on your preferences. 4. go through some examples to get an idea how it works. For example I wrote few years ago some examples how to use DBus (dbus-1tqt) https://mirror.git.trinitydesktop.org/gitea/deloptes/dbus-1-tqt-example This is pretty simple and does not need any automake or cmake. The build is in the shell script - so you will find out how to compile simple binary There are also other examples on the WIKI 5. in the repo there are the Debian build scripts by Michele, however he is using another build system and I wrote my own build system based on make files, but you are using OpenSUSE (RPMs), so might be not of any advantage for you
I have never used a "build environment," so I have no preferences. :-) Right now I use the jEdit text editor, which has some quasi-build-environment plugins, which I have not fooled with.
Leslie
On Wednesday 29 May 2024 02:05:22 deloptes via tde-devels wrote:
J Leslie Turriff via tde-devels wrote:
tdeupdalt main.o tdeupdalt.o -ltdeui
| ../libtool: line 1300: func_opt_split: command not found | libtool: Version mismatch error. This is libtool 2.2.6b
Debian-2.2.6b-2ubuntu1, but the
| libtool: definition of this LT_INIT comes from libtool 2.4.6. | libtool: You should recreate aclocal.m4 with macros from libtool 2.2.6b
Debian-2.2.6b-2ubuntu1
| libtool: and run autoconf again. | gmake[2]: Leaving directory '/home/development/TDEupdAlt/debug/src'
regarding the error it is obvious that it comes from automake process trying libtool and it seems there is version mismatch. I don't know if you know automake tools. If not you should read about them first.
Not obvious to me. :-)
Leslie -- Platform: Linux Distribution: openSUSE Leap 15.5 - x86_64 Desktop Environment: Trinity Qt: 3.5.0 TDE: R14.1.2 tde-config: 1.0
-
deloptes -
Dr. Nikolaus Klepp -
J Leslie Turriff