bug-gnubg
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-gnubg] Re: compiling gnubg for windows (fwd)


From: Øystein Johansen
Subject: Re: [Bug-gnubg] Re: compiling gnubg for windows (fwd)
Date: Sun, 21 Jul 2002 02:18:06 +0000
User-agent: Mutt/1.2.5i

On Sat, Jul 20, 2002 at 09:33:50PM +0200, address@hidden wrote:
> Hi,
> 
> Can you help me compile? The version without GUI compiles but not with GTK.
> I'll tell you how far I got and what problems I have.

Hi Kees!

I think it is much easier to use mingw instead of cygwin!
Get mingw gcc-2.95.2 at www.mingw.org (forget about cygwin!)

> I've been trying to compile gnubg under windoze (ME) using acepoints
> instructions http://mole.dnsalias.org/~acepoint/GnuBG/faq.html#SEC17

I have never tried to compile under ME, but I know there is a problem
with 'make' under win95 and win98. (win2000 and winNT works good)

> Besides the utils  mentioned on acepoints page  you also  need something
> like the cygwin UNIX utils of course which I have.

Actually not! Forget about cygwin, it will only confuse both you and
the compiler. 

> After installing everything I run
> 
> $ sh configure --with-gtk  --disable-nls --disable-gtktest  
> --with-gtk-prefix="C:/gcc-2.95.2"

Don't run configure at all. Just get a config.h file that suits you.
Get my config.gui here:

http://home.online.no/~oeysteij/config.gui

and rename that to config.h

comment out the HAVE_GDBM line if don't have gdbm 
comment out the HAVE_XML line if don't have xml

Get the Makefile here:
http://home.online.no/~oeysteij/Makefile

and this one to the lib directory:

http://home.online.no/~oeysteij/lib/Makefile

type 'make'

(Maybe you have to edit the Makefile if you use a resent snapshot, there's
two files added in the source. gtkchequer.c and gtkcube.c. You should
therefore add gtkchequer.c and gtkcube.c in the SRC definiton, and gtkcube.o
and gtkchequer.o in the OBJS section of the Makefile.)   

If 'make' fails on ME (as it does on win95 and win98), you can use a
build script instead. Mail me again if you need this.

> (the gtk test always fails, so I chose to turn it off, nls does not compile,
> prob. because no /usr/locale on windoze) I don't worry about this yet)

I guess you have downloaded the gtk libraries on Tor's site? You need
both the runtime libraries and the development packages.

> Should I then use the generated Makefile, or (according to acepoints) download
> Makefile from http://home.online.no/~oeysteij/Makefile and use that?

As I said: Don't even get cygwin nor run configure. Just use the Makefile.
Maybe you have to add the path to your include header files directory in the
Makefile, (CFLAGS = -I/path/to/where/you/put/your/gtk/headers/).It's still
better to use the Makefiles from my site, than generating something 
nonsense from a cygwin configure. 
 
> Neither compile as-is. In both I have to add to INCLUDE
> 
> -IC:/gcc-2.95.2/include/glib-2.0/ -IC:/gcc-2.95.2/lib/glib-2.0/include/ 
> -IC:/gcc-2.95.2/lib/gtk+/include/ -IC:/gcc-2.95.2/gdbm-1.8.0/win32b
> 
> or it won't find header files. I installed all the  gtk stuff in the gcc
> dir, maybe that's why?
> 
> Then it gets as far as:
> 
> In file included from database.c:25:
> C:\gcc-2.95.2\gdbm-1.8.0\win32b\gdbm.h:163: syntax error before `extern'

Make sure your files are saved with unix style endlines. That may confuse
the compiler, if the c-code uses a macro.
 
> Thanks for any help you can offer. Should I reinstall gcc and gtk to separate
> directories perhaps?

I keep my compiler in c:\mingw\

I then installed the gtk headers in c:\mingw\include\gtk\

I then think the compiler will find the header files all by it self.

Just mail me if you get some problems again!

> Kees

-Øystein
(excuse my typos, I'm slightly drunk....) 

-- 
It's remarkable that a science which began with the consideration of
games of chance should have become the most important object of human
knowledge....   The most important questions of life are, for the most
part, really only problems of probability.          -- Laplace, 1812



reply via email to

[Prev in Thread] Current Thread [Next in Thread]