Re: [Libwpg-devel] web pages for libwpg

[Fridrich S. <fri...@bl...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ariya Hidayat wrote:
> The information is mostly complete, except for building_windows.htm,
> which is about building libwpg under Windows. I hope Fridrich can fill
> some holes there, as I have no experience nor knowledge on how to do
> that. I reckon we may need similar information for Mac OS X but then
> again, I don't have access to any Mac machine.

I just committed some fixes for the win32 build.

MS Visual Studio:

Now it can build a static library and statically linked multithread (do
not ask me why, but the free as beer VS8 does not have anymore single
thread C runtimes, so multithread is a must) binaries. They build with
MSVC6 and with VS8. Their only runtime dependency is a kernel32.dll, so
they should run basically on any win32. The build is simple: use the
libwpg.dsw project file located in build/win32 and to have somewhere in
the include path <libwpd/WPXStream.h> and <libwpd/libwpd_types.h>
headers. Libwpd is not needed in the link process, so one does not
really need to build it.
The only difficulty can be that when one is building a cvs checkout, the
libwpg.h file is not existing (normally generated by the autofoo build
process at configure time). The solution is to copy the libwpg.h.in into
libwpg.h and replace the occurences of @WPG_MAJOR_VERSION@,
@WPG_MINOR_VERSION@ and @WPG_MICRO_VERSION@ with the values found in
configure.in file.

MinGW:

A static library, a DLL and statically or dynamically built wpg2raw.exe
and wpg2svg.exe can be build on win32 using gcc (MinGW). There is also
need to have pkgconfig for win32 and the above-mentioned headers. Again,
libwpd is not a dependency needed at runtime and nothing links with it,
so if one does not want to build it, it is completely ok to put the
headers and the *.pc files to a location where pkgconfig and g++ will
find them.

> I also suggest we put the API documentation online, at least for
> documentation of public classes. But we can do this later on.

Ariya, I would still insist on the fact that we should treat the stream
and buffer version of WPGraphics::parse and WPGraphics::generateSVG at
the same level of importance ;-) And yay for hosting the api
documentation, that is normally built if doxygen is in the path,
somewhere. Uwog, can you try to help us with it. Moreover, once the
regression suite exists, would be nice to have some results publicly
accessible :-)

Cheers

Fridrich
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFGVW5iu9a1imXPdA8RAjNHAJ9z6EY0bufYRa+IoLsWMZQZ5Ry+fQCfUHFV
Irh9CFO21NzufyeTXA+aOgM=
=l4JZ
-----END PGP SIGNATURE-----