On Sat, 2009-10-03 at 14:33 +0100, Lukas Zeller wrote:
> the "unilib" or "combi_engine" is ready and pushed on synthesis/
> indefero unilib branch!
>
> I adapted the classic makefiles, and leave the automake stuff to
> you :-) Thanks!
Updated :-) Works fine in my SyncEvolution client->server tests, both
with dynamic and static linking. I pushed my updated "unilib" branch to
moblin.org. I intend to update it slightly this afternoon before pushing
a matching SyncEvolution.
The main commit is this:
autotools build: switched to new combi engine
configure/make build all files required for client
and server engine into the same libsynthesis. The
SDK always assumes that the engine is linked
directly and thus has undefined references to the
engine entry points.
An application which doesn't want to link against
the engine has to provide dummy entry points, then
later open libsynthesis.so.0 in ConnectEngine. Should
be provided as part of the Synthesis source code, together
with a corresponding synthesis_sdk.pc.
That the SDK depends on the engine entry points is defined
in config.h, not in the shared SDK/target_options.h.
The rationale is that not all SDK users might want the
extra dependency. To make this work, the relevant SDK
source code has to include config.h when available.
This patch builds upon the (incompletely merged and obsolete)
build update for two separate libraries and thus removes
obsolete code. It cleans up the selection of files a bit
(SDK contained some unused code).
The branch also carries some other fixes and (in case you want to merge
it, if not, I'll drop it) an 'extern "C" { static ... }' patch.
What I want to add later today is the dummy entry symbol part.
> Which also means that my change in generic_types.h could be the single
> most critical change for the Linux 64bit builds, as I reset uInt32/
> sInt32 to be really 32 bit again. See commit message of 33b0242610 (64
> bit: adjusted generic_types.h to make sure uInt32/sInt32 IS 32bits).
I though we had reverted to a "sane" define of uInt32/sInt32 already a
while ago. Well, we'll see. I'm glad to hear that you now also
struggling with 64 bit issues, eh, I mean, that I have capable
assistance right at the source (sic) with these kind of problems ;-)
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
_______________________________________________
os-libsynthesis mailing list
[email protected]
http://lists.synthesis.ch/mailman/listinfo/os-libsynthesis
