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:
>>>>> 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.
>>>> 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.
>>> 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).
>> 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/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/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
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 ;-)