Re: [Evolution-hackers] Compile Evolution Mail as .so file with API for other GUI on ARM device


Nice to meet the author of Anjal :)

I went through code and Wiki yesterday and I am starting to understand just a little piece of very high architecture.
I will try to compile EDS with my SDK for my ARM device. But first I need to familiarize with build process.

As I understand within EDS there is mail engine - this Camel library which I could use and link dynamically with my GUI.
Do you know if there is simple example that shows how to send email message?

Probably better way will be to use your e-mail-factory. Then I will be able to split GUI and Mail engine on two different processes.
Will your e-mail factory be an official part of Evolution soon?

I do not understand why you advice me to checkout branch of evolution. I thought that all data engines (mail and calendar) are covered by EDS.
And when I compile it I will be able to connect it with my GUI. It could be done over DBUS if I have two processes or just dynamic linking to GUI.
Do I think correctly?

Could you say, point me a document that describe how EDS store mails and calendar data. Is it some own database in file or some other mechanism?


On Mon, Jan 30, 2012 at 3:37 PM, Srinivasa Ragavan <sragavan gnome org> wrote:

On Mon, Jan 30, 2012 at 6:27 PM, Michal G. <guziemic spam gmail com> wrote:
> Hi,
> Thank you for answer.
> Yes. I'm looking for mail engine that will be able to communicate for
> instance over DBUS which some UI.
> My device does not uses, GTK and Cairo.
> It future, I would also append my software with Calendar functionality.

Calendar is already in EDS available over DBUS.

> I choosed to work with Evolution because I saw similar email client called
> Anjal that utilize Evolution but has own UI.

I was the author of Anjal. It was build with Gtk/Cairo on top of
libevolution-mail. Now after mbarnes's awesome library breaks, I broke
mail engine to a independent library that can reside in EDS (in the
future) which I currently server over DBUS.

You must checkout master branch of eds and evolution. is the dbus engine that Im
working on, which is still under development. Some apis are fun and
still not up to the mark. But you can use them and it works fine.


> Could you tell me from which git should I clone
> -
> -
> And could you tell where to start, or what should I read some to
> - build mail engine library ( - should
> I follow this process)
> - API of DBUS
> Michal
> On Sat, Jan 28, 2012 at 7:35 AM, Srinivasa Ragavan <sragavan gnome org>
> wrote:
>> Hi Michal,
>> On Fri, Jan 27, 2012 at 5:27 PM, Michal G. <guziemic spam gmail com>
>> wrote:
>> > Hi,
>> >
>> > I've been investigating a possibility of Evolution Mail
>> > cross-compilation
>> > for Linux X-less device (ARM) and use it as dynamic library that will
>> > provide me possibility to expose API that could be utilize by HMI layer.
>> >
>> > 1)    Is it possible to compile Evolution Mail without any user
>> > interface
>> > (pure –headless)? Or how much work would that require?
>> > 2)    Does Evolution architecture allows doing such split – mail
>> > supporting
>> > functionality and GUI?
>> > 3)    Is it possible to eliminate all unnecessary libs and resources?
>> > They’re using valuable device resources and may cause compilation
>> > problems.
>> > 4)    If I’m about hacking the build process to my needs (removing
>> > dependencies) where should I start?
>> IIUC you want to use the engine of evolution, but not the UI. If so,
>> I've been working on a mail daemon which has all the mail logic built
>> in and exposes mail (basic) interface over dbus. If you aren't
>> interested in that, you can look at which is a new
>> library that I added a week ago in master which provides most of what
>> you are looking at except the UI.
>> -Srini
>> >
>> > Best regards,
>> > Michal Guzieniuk
>> >
>> >
>> > _______________________________________________
>> > evolution-hackers mailing list
>> > evolution-hackers gnome org
>> > To change your list options or unsubscribe, visit ...
>> >
>> >

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]