Hi!
some packages of TDE I could install successfully and now the next one would be tdelibs. But there is no configure-file. Am I supposed to use autoconf to create one and which configure.* file should I use for autoconf? I know that you're switching to CMake but I would like to do it with make this time.
Kind regards, Christoph
On 2022/04/28 09:35 PM, Christoph Klassen wrote:
Hi!
some packages of TDE I could install successfully and now the next one would be tdelibs. But there is no configure-file. Am I supposed to use autoconf to create one and which configure.* file should I use for autoconf? I know that you're switching to CMake but I would like to do it with make this time.
Hi Chris, tdelibs is built with cmake these days. Have you checked out the packaging files for debian by the way? They contains all you need to build packages in debian, they will simplify your task a lot. Cheers Michele
Hello Michele,
On 4/28/22 15:57, Michele Calgaro via tde-devels wrote:
some packages of TDE I could install successfully and now the next one would be tdelibs. But there is no configure-file. Am I supposed to use autoconf to create one and which configure.* file should I use for autoconf? I know that you're switching to CMake but I would like to do it with make this time.
Hi Chris, tdelibs is built with cmake these days. Have you checked out the packaging files for debian by the way? They contains all you need to build packages in debian, they will simplify your task a lot. Cheers Michele
Would it still be possible to build the package with make? I'm asking because our fork is using make and there are also more files like Makefile.am First I would like to do it make and when I have success maybe we can switch to CMake.
I didn't use the scripts that you linked before because I would like to do it manually first because I want to learn something about the build process.
I also asked about if it would be possible to add our functionalities to kontact-trinity but those functionalities depend on our infrastructure so it would make no sense to add them. I can't say more because I didn't develop those things and I'm just starting with kontact.
Kind regards, Christoph
On Friday 29 of April 2022 09:59:08 Christoph Klassen wrote:
Hello Michele,
On 4/28/22 15:57, Michele Calgaro via tde-devels wrote:
some packages of TDE I could install successfully and now the next one would be tdelibs. But there is no configure-file. Am I supposed to use autoconf to create one and which configure.* file should I use for autoconf? I know that you're switching to CMake but I would like to do it with make this time.
Hi Chris, tdelibs is built with cmake these days. Have you checked out the packaging files for debian by the way? They contains all you need to build packages in debian, they will simplify your task a lot. Cheers Michele
Would it still be possible to build the package with make? I'm asking because our fork is using make and there are also more files like Makefile.am First I would like to do it make and when I have success maybe we can switch to CMake.
I didn't use the scripts that you linked before because I would like to do it manually first because I want to learn something about the build process.
I also asked about if it would be possible to add our functionalities to kontact-trinity but those functionalities depend on our infrastructure so it would make no sense to add them. I can't say more because I didn't develop those things and I'm just starting with kontact.
Kind regards, Christoph
Automake in core modules is not unused for a long time and it may not work well. Automake files are left there basically only because of their need during generate Apidox.
It is definitely a good idea to use CMake instead of automake. It is up to your choice whether you want to use CMake along with classic make or with ninja-build.
You do not have to use the comprehensive build scripts that Michele mentioned, but you can simply use the deb packaging files that are in tde-packaging GIT repository. Alternatively, you can download the source deb package and build yourself.
Cheers
On 4/29/22 12:01, Slávek Banko wrote:
Automake in core modules is not unused for a long time and it may not work well. Automake files are left there basically only because of their need during generate Apidox.
It is definitely a good idea to use CMake instead of automake. It is up to your choice whether you want to use CMake along with classic make or with ninja-build.
In the end I built tdelibs with cmake because I didn't know how to do it with make. But now I want to build tdebingings and there are no CMake-files. So, how do I build this package then?
You do not have to use the comprehensive build scripts that Michele mentioned, but you can simply use the deb packaging files that are in tde-packaging GIT repository. Alternatively, you can download the source deb package and build yourself.
Aren't the build scripts and the packaging files from the tde-packaging repo not the same?
Kind regards, Christoph
Hi Chris,
It is definitely a good idea to use CMake instead of automake. It is up to your choice whether you want to use CMake along with classic make or with ninja-build.
In the end I built tdelibs with cmake because I didn't know how to do it with make. But now I want to build tdebingings and there are no CMake-files. So, how do I build this package then?
On top of what Slavek already mentioned, we are progressively moving all the repos to cmake, so autotools support will be totally removed at some points. Already many modules can only be built with cmake since autotools support has already been removed. Re tdebindings, this has not yet been converted to cmake, so you need to use autotools.
You do not have to use the comprehensive build scripts that Michele mentioned, but you can simply use the deb packaging files that are in tde-packaging GIT repository. Alternatively, you can download the source deb package and build yourself.
Aren't the build scripts and the packaging files from the tde-packaging repo not the same?
tde-packaging (debian subfolder for your case), contains all the necessary files to build TDE modules in debian, either using dpkg-build, pbuilder or other building chains. My own scripts are simply a set of tools that work on top of the files from the packaging repo.
You should definitely use the files from tde-packaging, they will make your life easier. Whether to want to do it yourself or you my scripts is an optional choice.
Cheers Michele
Hi again!
On 4/29/22 16:59, Michele Calgaro via tde-devels wrote:
tde-packaging (debian subfolder for your case), contains all the necessary files to build TDE modules in debian, either using dpkg-build, pbuilder or other building chains. My own scripts are simply a set of tools that work on top of the files from the packaging repo.
You should definitely use the files from tde-packaging, they will make your life easier. Whether to want to do it yourself or you my scripts is an optional choice.
Finally I also tried your scripts and it's a really comfortable solution to build the packages. Also, they are very well documented on the Gitea-page. Thanks!
Hi! some packages of TDE I could install successfully and now the next one would be tdelibs. But there is no configure-file. Am I supposed to use autoconf ...The address book library. ... KPart for 'kate', the KDE advanced text editor. ... Personal certification manager. ... Auto-Updater for config files. ... This is the ..Download trinity-tdelibs-14.0.11-1.el8.x86_64.rpm for CentOS 8 from Trinity R14 ... /opt/trinity/share/icons/crystalsvg/16x16/actions/configure.png. https://www.cps-tester.co/
Hi! some packages of TDE I could install successfully and now the next one would be tdelibs. But there is no configure-file. Am I supposed to use autoconf ...Download trinity-tdelibs-14.0.11-1.el8.x86_64.rpm for CentOS 8 from Trinity R14 ... /opt/trinity/share/icons/crystalsvg/16x16/actions/configure.png. https://www.cps-tester.co/
-
binita felicity -
Christoph Klassen -
Michele Calgaro -
Slávek Banko