Message: previous - next
Month: February 2012

Re: [trinity-devel] build order question - apps not listed in HowToBuild wiki?

From: "David C. Rankin" <drankinatty@...>
Date: Sun, 19 Feb 2012 17:27:04 -0600
On 02/19/2012 03:43 PM, Darrell Anderson wrote:
> I am building against TQt3 right now. Mostly going well, but I'll need to report a handful of build issues.
> Regarding dependencies and order:
> avahi-tqt and libart-lgpl must be built before tdelibs. The former is optional, the latter is not.

Got it :)
> libcaldav and libcarddav must be built before tdepim. Both are optional. The tdepim build options include -DWITH_CALDAV and -DWITH_CARDDAV. When set to ON then both of the dependency packages must be built and installed.

There should NOT be a desktop built today that is NOT fully
caldav/carddav/webdav aware. The basic critical functionality they provide to
interface with groupware backends (eGroupWare - my preference) is required in 2012.

As an illustration, iOS is fully 'dav' aware while Android is not. For
businesses with groupware backends, there is no choice, iOS wins hands down.
Android does NOT provide this capability and the 3rd party pay-for Android apps
the supposedly support it are hit or miss making Android useless compared to iOS
in this situation. The 'davs' provides seamless integration to calendar and
contacts with bi-directional update capabilities.

I would pretty much consider them a MUST for TDE if TDE is going to be a modern
competitive desktop from a base capabilities standpoint.

> I never have read anything about the build order for tqca-tls, but I always build that package after tqtinterface and before building arts. By the way, the original qca package never was converted to tqca (bug report 817).
> The remaining three dependency packages are tdebindings related as far as I know. I have yet to build any of them although that is on my to-do list. Before GIT, tdebindings build without problems with or without any of those dependencies. If those packages are not installed then tdebindings should build but without that component support. When we finally get the bugs out of building tdebindings the same will apply. Some folks want to drop tdebindings altogether, others don't. That package doesn't mean much to most users --- unless and until they use a third party package that expects those bindings. A while ago we discussed how many of the bindings remained valid and we don't know.
> Not mentioned are the various libraries packages. I believe three of them are tdebindings related: libtqt-perl, pytdeextensions, and python-trinity. I haven't tried to build those. The other libraries are graphics related, such as support for gwenview, digikam, etc. I believe all libraries packages are optional.
> The bottom line is we all (including me!) need to start building all of these packages, whether or not we find them useful. That is the only way we will discover build issues and bugs. :)
> Darrell

+1, I want to see TDE the #1 desktop and it won't get there if it only provides
3/4 of the packages and capabilities that 3.5.10 did :)

David C. Rankin, J.D.,P.E.