Hi, can someone help quickly please. I am facing an issue with vCal format conversion "quoted printable" and charset: UTF-8. I git cloned the tdepim package and following previous instructions I updated submodule for cmake. I do mkdir testbuild ; cd testbuild; cmake ..; make but nothing happens.
What am I doing wrong? This same procedure worked for tdelibs and some other packages.
I wanted to debug having the know how to add test capabilities - I wanted to add testing for libkcal and wanted to compile but in vain.
Thanks in advance
PS: the problem is that fromString is not working (fails) for TODO.
On 2016/05/18 04:46 AM, deloptes wrote:
Hi, can someone help quickly please. I am facing an issue with vCal format conversion "quoted printable" and charset: UTF-8. I git cloned the tdepim package and following previous instructions I updated submodule for cmake. I do mkdir testbuild ; cd testbuild; cmake ..; make but nothing happens.
What am I doing wrong? This same procedure worked for tdelibs and some other packages.
I wanted to debug having the know how to add test capabilities - I wanted to add testing for libkcal and wanted to compile but in vain.
Thanks in advance
PS: the problem is that fromString is not working (fails) for TODO.
Emanoil, for info what distro are you using? Cheers Michele
Michele Calgaro wrote:
On 2016/05/18 04:46 AM, deloptes wrote:
Hi, can someone help quickly please. I am facing an issue with vCal format conversion "quoted printable" and charset: UTF-8. I git cloned the tdepim package and following previous instructions I updated submodule for cmake. I do mkdir testbuild ; cd testbuild; cmake ..; make but nothing happens.
What am I doing wrong? This same procedure worked for tdelibs and some other packages.
I wanted to debug having the know how to add test capabilities - I wanted to add testing for libkcal and wanted to compile but in vain.
Thanks in advance
PS: the problem is that fromString is not working (fails) for TODO.
Emanoil, for info what distro are you using? Cheers Michele
Using debian TDE 14.0.3
regards
On 2016/05/19 06:04 AM, deloptes wrote:
Michele Calgaro wrote:
On 2016/05/18 04:46 AM, deloptes wrote:
Hi, can someone help quickly please. I am facing an issue with vCal format conversion "quoted printable" and charset: UTF-8. I git cloned the tdepim package and following previous instructions I updated submodule for cmake. I do mkdir testbuild ; cd testbuild; cmake ..; make but nothing happens.
What am I doing wrong? This same procedure worked for tdelibs and some other packages.
I wanted to debug having the know how to add test capabilities - I wanted to add testing for libkcal and wanted to compile but in vain.
Thanks in advance
PS: the problem is that fromString is not working (fails) for TODO.
Emanoil, for info what distro are you using? Cheers Michele
Using debian TDE 14.0.3
Ok, in Debian it is easy then. 1) clone the required module (tdepim) 2) clone the packaging info from the tde-packaging repo for the same module 3) copy (or replace) the debian folder from 2) to 1) 4.1) if you want a quick-n-dirty way, go to main module folder and use fakeroot debian/rules binary" 4.2) alternatively a cleaner way to build packages is by using pbuilder or dpkg-buildpackage
As long as you have all required packages available in your system, tdepim should build without problems, unless you are using Debian Strech and some libraries have been updated very recently (in such case you occasionally run into a FTBFS).
Cheers Michele
Michele Calgaro wrote:
On 2016/05/19 06:04 AM, deloptes wrote:
Michele Calgaro wrote:
On 2016/05/18 04:46 AM, deloptes wrote:
Hi, can someone help quickly please. I am facing an issue with vCal format conversion "quoted printable" and charset: UTF-8. I git cloned the tdepim package and following previous instructions I updated submodule for cmake. I do mkdir testbuild ; cd testbuild; cmake ..; make but nothing happens.
What am I doing wrong? This same procedure worked for tdelibs and some other packages.
I wanted to debug having the know how to add test capabilities - I wanted to add testing for libkcal and wanted to compile but in vain.
Thanks in advance
PS: the problem is that fromString is not working (fails) for TODO.
Emanoil, for info what distro are you using? Cheers Michele
Using debian TDE 14.0.3
Ok, in Debian it is easy then.
- clone the required module (tdepim)
- clone the packaging info from the tde-packaging repo for the same
module 3) copy (or replace) the debian folder from 2) to 1) 4.1) if you want a quick-n-dirty way, go to main module folder and use fakeroot debian/rules binary" 4.2) alternatively a cleaner way to build packages is by using pbuilder or dpkg-buildpackage
As long as you have all required packages available in your system, tdepim should build without problems, unless you are using Debian Strech and some libraries have been updated very recently (in such case you occasionally run into a FTBFS).
Cheers Michele
Hi Michele, you misunderstood. I did not want to build package, but build the tdepim source. For this I git clone tdepim and clone the cmake submodule. I try cmake but nothing happens. I guess the dpkg-buildpackage would also not work, but thats a guess.
regards
On 19/05/2016 06:43, deloptes wrote:
Michele Calgaro wrote:
On 2016/05/19 06:04 AM, deloptes wrote:
Michele Calgaro wrote:
On 2016/05/18 04:46 AM, deloptes wrote:
Hi, can someone help quickly please. I am facing an issue with vCal format conversion "quoted printable" and charset: UTF-8. I git cloned the tdepim package and following previous instructions I updated submodule for cmake. I do mkdir testbuild ; cd testbuild; cmake ..; make but nothing happens.
What am I doing wrong? This same procedure worked for tdelibs and some other packages.
I wanted to debug having the know how to add test capabilities - I wanted to add testing for libkcal and wanted to compile but in vain.
Thanks in advance
PS: the problem is that fromString is not working (fails) for TODO.
Emanoil, for info what distro are you using? Cheers Michele
Using debian TDE 14.0.3
Ok, in Debian it is easy then.
- clone the required module (tdepim)
- clone the packaging info from the tde-packaging repo for the same
module 3) copy (or replace) the debian folder from 2) to 1) 4.1) if you want a quick-n-dirty way, go to main module folder and use fakeroot debian/rules binary" 4.2) alternatively a cleaner way to build packages is by using pbuilder or dpkg-buildpackage
As long as you have all required packages available in your system, tdepim should build without problems, unless you are using Debian Strech and some libraries have been updated very recently (in such case you occasionally run into a FTBFS).
Cheers Michele
Hi Michele, you misunderstood. I did not want to build package, but build the tdepim source. For this I git clone tdepim and clone the cmake submodule. I try cmake but nothing happens. I guess the dpkg-buildpackage would also not work, but thats a guess.
regards
I don't think Michele misunderstood, he described how to build 'tdepim' from source, which is what you say you want to do.
Off the top of my head I can't remember if 'tdepim' is cmake ready or not. Actually, just checked, it is.
Cheers, Mike.
On 2016/05/19 05:07 PM, Michael Howard wrote:
Michele
Hi Michele, you misunderstood. I did not want to build package, but build the tdepim source. For this I git clone tdepim and clone the cmake submodule. I try cmake but nothing happens. I guess the dpkg-buildpackage would also not work, but thats a guess.
regards
I don't think Michele misunderstood, he described how to build 'tdepim' from source, which is what you say you want to do.
Off the top of my head I can't remember if 'tdepim' is cmake ready or not. Actually, just checked, it is.
Cheers, Mike.
Hi Emanoil, as Mike said, that is the way you build package starting from source in Debian/Ubuntu. I build them the same way. It building tdepim fails, there are two possibilities: 1) you are missing some dependency packages. This is most likely not highlighted when invoking cmake directly from CLI. If you use dpkg-buildpackage or pbuilder, they will check dependencies as well in the process and inform you if a required package is missing. 2) you are using Debian/Stretch and a recent change in a package cause a FTBFS, in which case we will need to prepare a fix for.
Most likely you are in case 1), although occasionally I run into 2) here and there (I use Debian/Stretch).
Cheers Michele
On Thursday 19 of May 2016 10:10:08 Michele Calgaro wrote:
On 2016/05/19 05:07 PM, Michael Howard wrote:
Michele
Hi Michele, you misunderstood. I did not want to build package, but build the tdepim source. For this I git clone tdepim and clone the cmake submodule. I try cmake but nothing happens. I guess the dpkg-buildpackage would also not work, but thats a guess.
regards
I don't think Michele misunderstood, he described how to build 'tdepim' from source, which is what you say you want to do.
Off the top of my head I can't remember if 'tdepim' is cmake ready or not. Actually, just checked, it is.
Cheers, Mike.
Hi Emanoil, as Mike said, that is the way you build package starting from source in Debian/Ubuntu. I build them the same way. It building tdepim fails, there are two possibilities:
- you are missing some dependency packages. This is most likely not
highlighted when invoking cmake directly from CLI. If you use dpkg-buildpackage or pbuilder, they will check dependencies as well in the process and inform you if a required package is missing. 2) you are using Debian/Stretch and a recent change in a package cause a FTBFS, in which case we will need to prepare a fix for.
Most likely you are in case 1), although occasionally I run into 2) here and there (I use Debian/Stretch).
Cheers Michele
I've done a rebuild tdepim 14.0.4~pre on Stretch and was completely without problems. It seems that so far no updates in Stretch did not cause breakage tdepim.
Tip for installing necessary dependencies:
apt-get build-dep tdepim-trinity
Tip for building: in debian/rules you can find DEB_CMAKE_EXTRA_FLAGS == options, which are used to build on Debian / Ubuntu.
Slávek Banko wrote:
On Thursday 19 of May 2016 10:10:08 Michele Calgaro wrote:
On 2016/05/19 05:07 PM, Michael Howard wrote:
Michele
Hi Michele, you misunderstood. I did not want to build package, but build the tdepim source. For this I git clone tdepim and clone the cmake submodule. I try cmake but nothing happens. I guess the dpkg-buildpackage would also not work, but thats a guess.
regards
I don't think Michele misunderstood, he described how to build 'tdepim' from source, which is what you say you want to do.
Off the top of my head I can't remember if 'tdepim' is cmake ready or not. Actually, just checked, it is.
Cheers, Mike.
Hi Emanoil, as Mike said, that is the way you build package starting from source in Debian/Ubuntu. I build them the same way. It building tdepim fails, there are two possibilities:
- you are missing some dependency packages. This is most likely not
highlighted when invoking cmake directly from CLI. If you use dpkg-buildpackage or pbuilder, they will check dependencies as well in the process and inform you if a required package is missing. 2) you are using Debian/Stretch and a recent change in a package cause a FTBFS, in which case we will need to prepare a fix for.
Most likely you are in case 1), although occasionally I run into 2) here and there (I use Debian/Stretch).
Cheers Michele
I've done a rebuild tdepim 14.0.4~pre on Stretch and was completely without problems. It seems that so far no updates in Stretch did not cause breakage tdepim.
Tip for installing necessary dependencies:
apt-get build-dep tdepim-trinity
Tip for building: in debian/rules you can find DEB_CMAKE_EXTRA_FLAGS == options, which are used to build on Debian / Ubuntu.
Hi all, I still feel misunderstood. Let me describe in more detail the situation I have. This is the procedure I used for tdevelop and tdelibs. And this same procedure does not work for tdepim.
First of all let me clear that I do not want to build a package. I just want to have a normal build (make) - that's it.
1. git clone http://system@scm.trinitydesktop.org/scm/git/tdepim 2. cd tdepim 3. git submodule update cmake Submodule path 'cmake' not initialized Maybe you want to use 'update --init'? 4. mkdir testbuild 5. cd testbuild 6. cmake .. 7. make
I also tried 3. rm -rf cmake 4. git clone https://system@scm.trinitydesktop.org/scm/git/tde-common-cmake
I guess I miss the proper step for checking out the cmake submodule
Sorry for being brief in the previous posts. I attached a log of what I did just now
Thanks in advance
On 2016/05/20 05:07 AM, deloptes wrote:
Slávek Banko wrote:
On Thursday 19 of May 2016 10:10:08 Michele Calgaro wrote:
On 2016/05/19 05:07 PM, Michael Howard wrote:
Michele
Hi Michele, you misunderstood. I did not want to build package, but build the tdepim source. For this I git clone tdepim and clone the cmake submodule. I try cmake but nothing happens. I guess the dpkg-buildpackage would also not work, but thats a guess.
regards
I don't think Michele misunderstood, he described how to build 'tdepim' from source, which is what you say you want to do.
Off the top of my head I can't remember if 'tdepim' is cmake ready or not. Actually, just checked, it is.
Cheers, Mike.
Hi Emanoil, as Mike said, that is the way you build package starting from source in Debian/Ubuntu. I build them the same way. It building tdepim fails, there are two possibilities:
- you are missing some dependency packages. This is most likely not
highlighted when invoking cmake directly from CLI. If you use dpkg-buildpackage or pbuilder, they will check dependencies as well in the process and inform you if a required package is missing. 2) you are using Debian/Stretch and a recent change in a package cause a FTBFS, in which case we will need to prepare a fix for.
Most likely you are in case 1), although occasionally I run into 2) here and there (I use Debian/Stretch).
Cheers Michele
I've done a rebuild tdepim 14.0.4~pre on Stretch and was completely without problems. It seems that so far no updates in Stretch did not cause breakage tdepim.
Tip for installing necessary dependencies:
apt-get build-dep tdepim-trinity
Tip for building: in debian/rules you can find DEB_CMAKE_EXTRA_FLAGS == options, which are used to build on Debian / Ubuntu.
Hi all, I still feel misunderstood. Let me describe in more detail the situation I have. This is the procedure I used for tdevelop and tdelibs. And this same procedure does not work for tdepim.
First of all let me clear that I do not want to build a package. I just want to have a normal build (make) - that's it.
- git clone http://system@scm.trinitydesktop.org/scm/git/tdepim
- cd tdepim
- git submodule update cmake
Submodule path 'cmake' not initialized Maybe you want to use 'update --init'? 4. mkdir testbuild 5. cd testbuild 6. cmake .. 7. make
I also tried 3. rm -rf cmake 4. git clone https://system@scm.trinitydesktop.org/scm/git/tde-common-cmake
I guess I miss the proper step for checking out the cmake submodule
Sorry for being brief in the previous posts. I attached a log of what I did just now
Thanks in advance
Hi Emanoil, I understand what you want to do, but the point is that just using cmake is not (or may not be) enough, because if a dependency package is missing from your system then the build would fail and you would not know why. If you just want a simple build, you can try this: 1) clone the required module (tdepim) 2) clone the packaging info from the tde-packaging repo for the same module. This contains debian related compiling stuff. 3) copy the debian folder from 2) to 1) 4) fakeroot debian/rules build. This will compile everything but will not build any .deb package at the end.
This way though you are still missing out on dependency check, so if any of the required packages is not available on your system, the compilation will most likely fails.
Just for info, Debian/Ubuntu have their own way and their own tools to easy compiling, building and packaging stuff. I strongly encourage you to spend a little bit of time to learn those things, you will get a lot of benefits once you understand that ;-)
Cheers Michele
Michele Calgaro wrote:
- fakeroot debian/rules build. This will compile everything but will not
build any .deb package at the end.
Thanks, this works now. I don't know what you mean with debian has tools for building - I thought I knew at least enough. And what I knew was sufficient to create/modify/build debian packages for some years now. It is also easy for me to understand why the rules file works. It is not easy to understand why in the case of tdepim it is necessary to go this way. Thanks for the motivation to try it and for the explanation.
PS: I removed kitchensync and the dependency on libopensync as obviously I don't want to build the former at this stage.
I don't know what you mean with debian has tools for building - I thought I knew at least enough. And what I knew was sufficient to create/modify/build debian packages for some years now. It is also easy for me to understand why the rules file works. It is not easy to understand why in the case of tdepim it is necessary to go this way. Thanks for the motivation to try it and for the explanation.
Building from source and then creating packages requires a lot of work. Debian/Ubuntu provides tools that automate most of it, you just need to learn a few basic commands. See here for some intro: https://www.debian.org/doc/manuals/maint-guide/build.en.html
Usually you build with dpkg-buildpackage or pbuilder, these are programs that take care of everything (config, checking dependencies, compiling, packaging, linting, ....). Moreover with pbuilder you can quickly build in a clean chroot environment, making sure you always build everything correctly.
It is really worth spending the time required to learn to compile/build in the Debian way, you will save much more time later on.
Cheers Michele
Michele Calgaro wrote:
I don't know what you mean with debian has tools for building - I thought I knew at least enough. And what I knew was sufficient to create/modify/build debian packages for some years now. It is also easy for me to understand why the rules file works. It is not easy to understand why in the case of tdepim it is necessary to go this way. Thanks for the motivation to try it and for the explanation.
Building from source and then creating packages requires a lot of work. Debian/Ubuntu provides tools that automate most of it, you just need to learn a few basic commands. See here for some intro: https://www.debian.org/doc/manuals/maint-guide/build.en.html
Usually you build with dpkg-buildpackage or pbuilder, these are programs that take care of everything (config, checking dependencies, compiling, packaging, linting, ....). Moreover with pbuilder you can quickly build in a clean chroot environment, making sure you always build everything correctly.
It is really worth spending the time required to learn to compile/build in the Debian way, you will save much more time later on.
Hi and thank you for the good words. I spend time learning and I will do so for the future. I good book is always worth reading. I read this document few years ago - from the time of squeeze. Looking now at it - it didn't change (that) much. I just never had the opportunity to use most of it and with time passing by a lot vanished from my memory, but thanks to knotes I have still a reference points. I went briefly through the document and I do not see things that are new to me.
I was just use to automake. I read a howto on cmake 5y ago, but did not use it frequently. I was expecting cmake to create working files, but in this case I need the debian/rules file to create working cmake file. This is the point that I was missing and I still do not understand why this should be the case. Usually it is the opposite.
But thanks - this was a good help.
regards
On Thursday 19 May 2016 22:07:04 deloptes wrote: [...]
Hi all, I still feel misunderstood. Let me describe in more detail the situation I have. This is the procedure I used for tdevelop and tdelibs. And this same procedure does not work for tdepim.
First of all let me clear that I do not want to build a package. I just want to have a normal build (make) - that's it.
- git clone http://system@scm.trinitydesktop.org/scm/git/tdepim
- cd tdepim
- git submodule update cmake
Submodule path 'cmake' not initialized Maybe you want to use 'update --init'? 4. mkdir testbuild 5. cd testbuild 6. cmake .. 7. make
[...]
I think you did not passed any arguments to cmake command. The correct command should be something like this:
cmake .. -DCMAKE_INSTALL_PREFIX=/path/to/kdelibs -DBUILD_ALL=ON -DWITH_ALL_FEATURES=ON
-
deloptes -
Michael Howard -
Michele Calgaro -
Serghei Amelian -
Slávek Banko