Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
From: Hendrik Sattler <post@he...> - 2007-01-08 13:04:33
even many eyes sometimes do not catch such small things. The last patch in CVS
misses a '\', so that libtool does not see the version info anymore and the
soname is lost.
Here's the fix:
RCS file: /cvsroot/openobex/openobex/lib/Makefile.am,v
retrieving revision 1.19
diff -u -r1.19 Makefile.am
--- lib/Makefile.am 31 Dec 2006 15:09:27 -0000 1.19
+++ lib/Makefile.am 8 Jan 2007 12:54:18 -0000
@@ -18,7 +18,7 @@
libopenobex_la_LDFLAGS = \
+ -no-undefined \
-version-info 4:0:3 \
This kills DLL creation for windows, though, as not all symbols are exported.
This means that another patch for this problem will follow, I first have to
take a look at it.
Am Montag 08 Januar 2007 14:03 schrieb Hendrik Sattler:
> This kills DLL creation for windows, though, as not all symbols are
> exported. This means that another patch for this problem will follow, I
> first have to take a look at it.
As promised, I made a patch for API enforcement for windows (means, creating
the lib more correctly). This makes it build again on win32.
While doing that, I found the GCC4 visibility feature and enabled that, too
(practically the same thing).
With this patch, the lib/obex.sym with its usage in lib/Makefile.am can go
away. Visibility does the same but you do not have to maintain two sets.
However, removing it makes it uncleaner when compiling with GCC < 4. Some
embedded people are still using gcc-3.4, thus I left it in.
You need visibility.m4 from gettext (or ask me for it).
PS: both patches should be included before next release!