22 Apr
2022
22 Apr
'22
4:18 p.m.
Hello,
which compiler version is used to build kontact-trinity and where can I
find this information?
I'm asking because my task is to build a different "fork" of kontact 3.5
on Bullseye and that build doesn't work yet so I want to compare that
fork with the TDE version of kontact so I can patch the fork. I have to
admit that I know little about building packages. Still, it's my task so
somehow I have to find my way through.
Greetings,
Christoph
23 Apr
23 Apr
12:58 p.m.
On 2022/04/23 01:18 AM, Christoph Klassen wrote:
Hello,
which compiler version is used to build kontact-trinity and where can I find this
information?
I'm asking because my task is to build a different "fork" of kontact 3.5 on
Bullseye and that build doesn't work yet so
I want to compare that fork with the TDE version of kontact so I can patch the fork. I
have to admit that I know little
about building packages. Still, it's my task so somehow I have to find my way
through.
Greetings,
Christoph
Hi Christoph,
you use the compiler of your distro, which in case of Bullseye is gcc/g++ unless you
switched to clang (which also works).
Cheers
Michele
24 Apr
24 Apr
6:27 a.m.
On Friday 22 of April 2022 18:18:59 Christoph Klassen wrote:
Hello,
which compiler version is used to build kontact-trinity and where can I
find this information?
I'm asking because my task is to build a different "fork" of kontact 3.5
on Bullseye and that build doesn't work yet so I want to compare that
fork with the TDE version of kontact so I can patch the fork. I have to
admit that I know little about building packages. Still, it's my task so
somehow I have to find my way through.
Greetings,
Christoph
Hi Christoph,
as Michele mentioned, we use the default distribution compiler. For
supported versions of Debian distribution, it includes GCC from version
6.3 to version 11.x. To build on FreeBSD, Clang is used there.
Cheers
--
Slávek
25 Apr
25 Apr
7:45 a.m.
On 4/24/22 08:27, Slávek Banko wrote:
Hi Christoph,
as Michele mentioned, we use the default distribution compiler. For
supported versions of Debian distribution, it includes GCC from version
6.3 to version 11.x. To build on FreeBSD, Clang is used there.
Thanks to both of you, Michele and Slávek!
And which C(++)-standard is used? As far as I know you can set the
standard with CPPFLAGS/CXXFLAGS when you add a parameter. In the file
acinclude.m4.in I found the line "CXXFLAGS="-ansi [...]" and I read that
sometimes the standard C89 is also called ANSI C, but I couldn't find
out what the parameter -ansi stands for in the CXXFLAGS.
Can you help me to bring light into the darkness? I would also be
grateful, if you had articles or the like, so I could read about it.
Kind regards,
Christoph
8:23 a.m.
Christoph Klassen wrote:
Thanks to both of you, Michele and Slávek!
And which C(++)-standard is used? As far as I know you can set the
standard with CPPFLAGS/CXXFLAGS when you add a parameter. In the file
acinclude.m4.in I found the line "CXXFLAGS="-ansi [...]" and I read that
sometimes the standard C89 is also called ANSI C, but I couldn't find
out what the parameter -ansi stands for in the CXXFLAGS.
Can you help me to bring light into the darkness? I would also be
grateful, if you had articles or the like, so I could read about it.
I can share my experience when I started contributing to the project. I must
admit it was also very dark where I was standing.
1. Lets start with the target distribution. I use debian (stable).
Your approach should be also based on the target distro.
2. Ressources: https://www.trinitydesktop.org/development.php
You can also check the WIKI
https://wiki.trinitydesktop.org/How_to_Build_TDE_Core_Modules
https://wiki.trinitydesktop.org/Category:Developers
3. Clone the repository and setup the build environment
a. https://wiki.trinitydesktop.org/Project_GIT_Information#Using_GIT
b. depends on the distribution. I use kind of frankenstein
I used some ideas from the "buildscripts", but did not want to use
all
I wrote my own set of Makefiles
4. After building the packages, you need to manage them. I used a howto
called "SimpleDebianRepository". This way I can build and install on all
the PCs and VMs I control in the local network or via VPN.
I hope it helps
BR
--
FCD6 3719 0FFB F1BF 38EA 4727 5348 5F1F DCFE BCB0
8:26 a.m.
On Monday 25 of April 2022 09:45:22 Christoph Klassen wrote:
On 4/24/22 08:27, Slávek Banko wrote:
Hi Christoph,
for TDE releases <= r14.0.11 there apply, that for CMake builds is used the
default C++ standard of distribution compiler, while for Automake builds
was enforced "-ansi", which actually enforces C++98. This enforcement of
the old standard for Automake builds was canceled. For the upcoming
R14.0.12 we set as a minimum required standard C++11.
Because tdepim is built using CMake, there is no need to deal with files
related to Automake build process - ie acinclude.m4.in, configure.in*,
Makefile.in.
See related commits in common "admin" and "cmake" modules:
https://mirror.git.trinitydesktop.org/cgit/admin/commit/?h=r14.0.x&id=b…
https://mirror.git.trinitydesktop.org/cgit/admin/commit/?h=r14.0.x&id=a…
https://mirror.git.trinitydesktop.org/cgit/cmake/commit/?h=r14.0.x&id=1…
Cheers
--
Slávek
Hi Christoph,
as Michele mentioned, we use the default distribution compiler. For
supported versions of Debian distribution, it includes GCC from
version 6.3 to version 11.x. To build on FreeBSD, Clang is used there.
Thanks to both of you, Michele and Slávek!
And which C(++)-standard is used? As far as I know you can set the
standard with CPPFLAGS/CXXFLAGS when you add a parameter. In the file
acinclude.m4.in I found the line "CXXFLAGS="-ansi [...]" and I read that
sometimes the standard C89 is also called ANSI C, but I couldn't find
out what the parameter -ansi stands for in the CXXFLAGS.
Can you help me to bring light into the darkness? I would also be
grateful, if you had articles or the like, so I could read about it.
Kind regards,
Christoph
9:06 a.m.
On 4/25/22 10:23, deloptes wrote:
I can share my experience when I started contributing to the project.
I must
admit it was also very dark where I was standing.
1. Lets start with the target distribution. I use debian (stable).
Your approach should be also based on the target distro.
2. Ressources: https://www.trinitydesktop.org/development.php
You can also check the WIKI
https://wiki.trinitydesktop.org/How_to_Build_TDE_Core_Modules
https://wiki.trinitydesktop.org/Category:Developers
3. Clone the repository and setup the build environment
a.
https://wiki.trinitydesktop.org/Project_GIT_Information#Using_GIT
b. depends on the distribution. I use kind of
frankenstein
I used some ideas from the "buildscripts", but did not
want to use all
I wrote my own set of Makefiles
4. After building the packages, you need to manage them. I used a howto
called "SimpleDebianRepository". This way I can build and install on all
the PCs and VMs I control in the local network or via VPN.
Thanks, but I visited these links already :)
On 4/25/22 10:26, Slávek Banko wrote:
for TDE releases <= r14.0.11 there apply, that for
CMake builds is used the
default C++ standard of distribution compiler, while for Automake builds
was enforced "-ansi", which actually enforces C++98. This enforcement of
the old standard for Automake builds was canceled.
Thanks for the explanation! That makes things clearer.
For the upcoming
R14.0.12 we set as a minimum required standard C++11.
When is that release planned?
Kind regards,
Christoph
9:10 a.m.
On 4/25/22 11:06, Christoph Klassen wrote:
On 4/25/22 10:26, Slávek Banko wrote:
Okay, this one I can answer myself because there was an email saying
that the release is planned for end of April.
For the upcoming
R14.0.12 we set as a minimum required standard C++11.
When is that release planned?
3:05 p.m.
On 2022/04/25 06:10 PM, Christoph Klassen wrote:
On 4/25/22 11:06, Christoph Klassen wrote:
Hi Chris,
R14.0.12 should be out in a week.
In Debian, you can also look at this scripts:
https://mirror.git.trinitydesktop.org/gitea/TDE/tde-packaging/src/branch/ma…
you can follow the instructions on the README file and things should pretty much work. If
not, let me know and I will
look into the issue. This should **greatly** simplify building tde in debian.
Cheers
Michele
On 4/25/22 10:26, Slávek Banko wrote:
Okay, this one I can answer myself because there was an email saying that the release is
planned for end of April.
For the upcoming
R14.0.12 we set as a minimum required standard C++11.
When is that release planned?
26 Apr
26 Apr
8:09 a.m.
On 4/25/22 17:05, Michele Calgaro via tde-devels wrote:
Hi Chris,
R14.0.12 should be out in a week.
In Debian, you can also look at this scripts:
https://mirror.git.trinitydesktop.org/gitea/TDE/tde-packaging/src/branch/ma…
you can follow the instructions on the README file and things should
pretty much work. If not, let me know and I will look into the issue.
This should **greatly** simplify building tde in debian.
Thanks Michele! The problem is that I'm working with a fork of the
"normal" Kontact 3.5 and not the one from TDE. Maybe it can still be
helpful to look at the scripts. The reason why we don't just use
kontact-trinity is that we already have additional functions which would
be missing if we used kontact-trinity. Still, maybe it's possible that
we implement patches or features which we can contribute to the
Trinity-project.
Kind regards,
Christoph
9:44 a.m.
On 2022/04/26 05:09 PM, Christoph Klassen wrote:
Thanks Michele! The problem is that I'm working
with a fork of the "normal" Kontact 3.5 and not the one from TDE. Maybe
it can still be helpful to look at the scripts. The reason why we don't just use
kontact-trinity is that we already have
additional functions which would be missing if we used kontact-trinity. Still, maybe
it's possible that we implement
patches or features which we can contribute to the Trinity-project.
Kind regards,
Christoph
That would be great. Maybe we can merge those extra functionality and then you can move to
kontact-trinity which would
probably simplify things for your end.
Feel free to reach out to us in case :-)
Cheers
Michele
736
days inactive
740
days old
10 comments
4 participants
participants (4)
-
Christoph Klassen -
deloptes -
Michele Calgaro -
Slávek Banko