[swift-users] swift compile fails on Fedora 13

[Matthew Chan]

Hi Remko,

Oh, I wasn't aware that Swiften wasn't available as a shared library. From
what I understand about fedora packaging policies (which closely mirror
other distros), I won't be able to have Xournal submitted for inclusion
unless swiften is available as a separately dynamically shared library.

That's ok though, because given the lead-time between our development
process of collaborative features and our stable releases to distros, I am
hoping that Swiften will be able to be included. Please let me know if
there's any information/testing I can give as a 3rd party Swiften user to
help move this process forward.

I think if you can provide Swiften as a shared lib in the repos, it will
gain popularity quickly. The other comprehensive C++ XMPP options available
are either extremely complicated (telepathy, libjingle) or not actively
maintained any more (gloox), and poorly documented (libpurple). I was quite
happy when I found Swiften and I do think that other devs requiring XMPP
features would be too.

Matt



2011/4/28 Remko Tronçon <remko at el-tramo.be>

> Hi Matthew,
>
> > Out of curiosity, since you have a fedora packager, is Swift/Swiften
> being
> > submitted for inclusion into the Fedora repos?
>
> As far as I know, swift is, but looking at
> http://pkgs.fedoraproject.org/gitweb/?p=swift.git , Swiften isn't yet.
>
> I know Jan (the Fedora packager) was pushing us to create a shared
> swiften library a while ago. I added this to our build system
> recently, but this probably wasn't adopted yet because there was no
> concrete demand yet for 1.0. However, C++ shared libraries are always
> a bit tricky to manage (as they're closely tied to the compiler and
> compiler settings), so I'm not 100% sure if we don't need to do some
> changes to Swiften to make this completely correct (although it did
> seem to work for Swift). I think we'll need to work with third-party
> Swiften users and packagers to check this flow and get it greased.
>
> That said, creating a swiften-dev package with a static .a lib should
> wor,k but then again probably has limited value without a .so package.
>
> > since we're thinking of making Swiften a dependency for Xournal.
>
> That would be great! ;-)
>
> cheers,
> Remko
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </lists/pipermail/swift-users/attachments/20110428/d3db28ee/attachment.htm>