libwpg-devel

[Libwpg-devel] web pages for libwpg

[Ariya H. <ari...@gm...>]

Hi folks,

For the past few days, I have created a draft or our web pages. I put
in our CVS repository under the module libwpg-www. If everything looks
fine, we should put the pages on-line as soon as possible.

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 also suggest we put the API documentation online, at least for
documentation of public classes. But we can do this later on.

So first, please have a look at the pages. Comments and suggestions
are welcomed.

Thank you!

Regards,

Ariya

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-----

Re: [Libwpg-devel] web pages for libwpg

[Ariya H. <ari...@gm...>]

> I just committed some fixes for the win32 build.

Very good. Thanks.

> MS Visual Studio:
> MinGW:

Is it possible for you to add this information to the
build_windows.htm web page? Unless I do it by myself (which I can't,
in the mean time), I don't have full confidence to write down all
these steps.

> 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 ;-)

I'll continue this on the original stream thread...

> 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 :-)

Fine with me.


Regards,

Ariya

Re: [Libwpg-devel] web pages for libwpg

[Smokey A. <alq...@ar...>]

At 2:15 PM +0200 on 5/23/07, Ariya Hidayat wrote:

>I reckon we may need similar information for Mac OS X but then
>again, I don't have access to any Mac machine.

Aside from stuff about creating a Universal Binary and/or targeting 
10.3.9 as well as 10.4, the Linux stuff should be fine for Mac OS X 
as well; building libwpd and its dependencies is the "hard" part ;-) 
Real Mac hackers probably know those bits, too; likely even Fridrich 
can fill in the details.

As I'm still on 10.3.9 and only 10.4 can build Universal Binaries, I 
can't say with certainty, of course, but at least I can build libwpg 
and wpg2odg (again--after some changes that went in cvs in the past 
few days) on 10.3.9 with gcc 3.3 (despite the purported gcc 4 
requirement), at least as a shared libs/binaries.

Some of the files I throw at it seem to have minor issues, but I feel 
comfortable saying libwpg and friends build and work on Mac OS X.

And the site looks very nice :)

Smokey
(still around, just rather busy)
-- 
Smokey Ardisson
alq...@ar...
http://www.ardisson.org/
------------------------------------------
"He is a fool who has forgotten what became of his ancestry
seven generations before him and who does not care what will
become of his progeny seven generations after him."
           --Kazakh Proverb

Re: [Libwpg-devel] web pages for libwpg

[Ariya H. <ari...@gm...>]

> Aside from stuff about creating a Universal Binary and/or targeting
> 10.3.9 as well as 10.4, the Linux stuff should be fine for Mac OS X
> as well; building libwpd and its dependencies is the "hard" part ;-)
> Real Mac hackers probably know those bits, too; likely even Fridrich
> can fill in the details.
>
> As I'm still on 10.3.9 and only 10.4 can build Universal Binaries, I
> can't say with certainty, of course, but at least I can build libwpg
> and wpg2odg (again--after some changes that went in cvs in the past
> few days) on 10.3.9 with gcc 3.3 (despite the purported gcc 4
> requirement), at least as a shared libs/binaries.

Thanks, Smokey. That's certainly an important information.

> Some of the files I throw at it seem to have minor issues, but I feel
> comfortable saying libwpg and friends build and work on Mac OS X.

Would it be good if you can write the details in a separate web page,
e.g. "Building for Mac OS X"? I can prepare the template and fill it
with some info from the linux page.
What do you think?

Regards,

Ariya

Re: [Libwpg-devel] web pages for libwpg

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

Nice to hear you again, Smokey. You cannot imagine how much we miss you :-)

Smokey Ardisson wrote:
> Aside from stuff about creating a Universal Binary and/or targeting 
> 10.3.9 as well as 10.4, the Linux stuff should be fine for Mac OS X 
> as well; building libwpd and its dependencies is the "hard" part ;-)

This will disappear with 0.9.x, since libgsf will not be dependency 
anymore; but it is possible that libwpd will be not the same thing 
anymore either. Let's see.

> Real Mac hackers probably know those bits, too; likely even Fridrich 
> can fill in the details.

My Mac Mini is now having a break resting somewhere in a box :-)

> As I'm still on 10.3.9 and only 10.4 can build Universal Binaries, I 
> can't say with certainty, of course, but at least I can build libwpg 
> and wpg2odg (again--after some changes that went in cvs in the past 
> few days) on 10.3.9 with gcc 3.3 (despite the purported gcc 4 
> requirement), at least as a shared libs/binaries.

Actually, it builds on win32 with gcc 3.4.5 and on CentOS4 with gcc 
3.4.6, so lowering requirements could be a solution. Moreover, MSVC 6 
and higher on win32 do the job too.

> Some of the files I throw at it seem to have minor issues, but I feel 
> comfortable saying libwpg and friends build and work on Mac OS X.
> And the site looks very nice :)

Very true, indeed!

> Smokey
> (still around, just rather busy)

The introductory sentence still applies :-)

Cheers

Fridrich