Alexandre Julliard wrote:
I'd prefer if we could abstract parts of the current checks and put
that into aclocal. For instance many tests do something like
AC_CHECK_HEADER(xx.h)
if ac_cv_header_xx = yes
then
AC_CHECK_LIB(xx)
fi
Actually, now that I look at it, I'm a little confused
Hello,
I've spent some time trying to integrate libtool
(http://www.gnu.org/software/libtool) with Wine, and it seems to work
pretty well so far. Libtool is a configurable shell script used to
abstract the building and linking of libraries on a wide variety of
platforms.
Enclosed is an
Juergen Schmied wrote:
I would convert the current documentation in html, sort the topics, write a first
index
and put a additional top ten of questions and answers from cemw and wine-devel
into it if we could agree to do so.
Any thoughts on converting the docs to DocBook
As part of an effort to improve the accessibility of the Wine
documentation, I've converted (most of) the contents of the
wine/documentation directory into DocBook (an SGML variant). Naturally,
quite a bit of the content is old and crusty, and perhaps even flat out
wrong, but hopefully that can
On Wednesday, June 21, 2000, Patrik Stridvall [EMAIL PROTECTED] wrote:
3. Configuring Wine
- Customizing .winerc
- Builtin vs. native DLLs
- x11drv
- Look feel
- Keyboard
Even though the ttydrv doesn't currently work
very well we probably should have a section
On Wednesday, June 21, 2000, Patrik Stridvall [EMAIL PROTECTED] wrote:
This means of course that Alexandre and anybody that want to write
documentation must have it installed but that is not unreasonable IMHO.
Also, I would like to make a standing offer to convert any plain text
files into
On Wednesday, June 21, 2000, Patrik Stridvall [EMAIL PROTECTED] wrote:
I have only look very briefly on DocBook but it doesn't
look much more complicated than HTML and learning HTML
was very easy.
Yes, it's kind of verbose, especially with lists and tables, but for the
most part, the tag
[ I somehow forgot to mail this... ]
On Wednesday, June 21, 2000, Eric Pouech [EMAIL PROTECTED] wrote:
WINE USER'S GUIDE
For the day-to-day user; maintaining Wine on your system. How to
configure the basic services, like fonts, printing, multimedia.
perhaps what's missing is the
On Thursday, June 22, 2000, Patrik Stridvall [EMAIL PROTECTED] wrote:
Well, that is a problem for everything except pure text.
I'm more intrested in specific DocBook problems.
I'll try to come up with some more DocBook-specific limitations.
Then we have all the in code documention of the
On Thursday, June 22, 2000, Gerald Pfeifer [EMAIL PROTECTED] wrote:
I do like DocBook as a source format.
However, regular users should not have to deal with DocBook in any way.
I think we can cover the users if we include the generated HTML (and
possibly generated flat text) in with the
On Monday, July 10, 2000, Veksler Michael [EMAIL PROTECTED] wrote:
On Mon, 10 Jul 2000, Wilbur N. Dale wrote:
These are my latest additions to the HOWTO.
The patch is big because you have repeated big 'configure' artifacts all
over the directory tree:
ltconfig ltmain.sh configure
On Friday, August 18, 2000, Albert den Haan [EMAIL PROTECTED] wrote:
Someday we will actually write the contents for the
wine/documentation/patches.sgml file and this question will be easier to
answer :)
Looks like you just did. (c:
Here is some draft content for the file that I would add
On Jan 17, 2001, Jon Griffiths [EMAIL PROTECTED] wrote:
Thanks for the feedback though. If I get time I might scribble up some docs
on using unicode. Its taking a little getting used to, so it might be useful
for others working with Winelib in the future...
If you do get some docs
On Jan 18, 2001, Uwe Bonnes [EMAIL PROTECTED] wrote:
this is a problem with installed tools and what tools to install.
hertz:/spare/bon/wine/documentation make wine-doc/index.html
db2html wine-doc.sgml
make: db2html: Command not found
make: *** [wine-doc/index.html] Error 127
I don't
On Jan 18, 2001, Joerg Mayer [EMAIL PROTECTED] wrote:
On Thu, Jan 18, 2001 at 09:09:35AM -0600, Jeremy White wrote:
then documentation/wine-doc contains a nice set of HTML pages that
can be used by the user (or tarballed into an RPM g).
I've had problems building the documentation on a
15 matches
Mail list logo
