117682 - Need better integration of libical for build system

Status: VERIFIED DUPLICATE of bug 178798

(Calendar :: Internal Components, defect)

Description

[hacker formerly known as [e-mail]]

What's the actual plan for integrating libical into the build system?  Is
calendar going to be tied to the in-tree version of libical?  If so, then we
need to remove the check for libical on the system from mozilla/configure.in or
add a version number check.  My calendar enabled builds stopped working a few
weeks ago for no apparent reason and I believe it was because the required
version of libical got bumped without any indication from the build system.

I have mixed feelings about requiring people to install libical on the system
before they can test calendar.  It's the proper thing to do if calendar was
going to be dependent upon actual libical releases rather than some cvs hacked
version.  So the natural question is, is the in-tree version of libical going to
deviate from the standard release outside of build changes?

Comment 1

[hacker formerly known as [e-mail]]

Attachment: Build libical as part of the tree

Here's a hack that builds libical using its default autogen.sh script but
installs it into the local build tree and copies the installed bits to
mozilla's $(DIST)/bin .

Comment 2

[hacker formerly known as [e-mail]]

Attachment: mozilla/other-licenses/libical/mozilla.mk.in

Comment 3

[Brant Gurganus]

*** Bug 116776 has been marked as a duplicate of this bug. ***

Comment 4

[hacker formerly known as [e-mail]]

*** This bug has been marked as a duplicate of 178798 ***

Comment 5

[Brant Gurganus]

VERIFIED DUPLICATE

Comment 6

[Reed Loden [:reed]]

The bugspam monkeys have been set free and are feeding on Calendar :: Internal Components. Be afraid for your sanity!