bug-gnubg
[Top][All Lists]
Advanced

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

Re: [Bug-gnubg] cmake


From: Michael Petch
Subject: Re: [Bug-gnubg] cmake
Date: Mon, 10 Mar 2008 14:25:20 -0700
User-agent: Microsoft-Entourage/11.4.0.080122



No I haven’t but its an option. I’d have to look into it. I’ve always used fink (And the Gnubg CVS source tree for builds) over the years. I don’t know how well maintained macports is, and not sure how friendly it is to GnuBg. I can try to give it a spin when I have time later in the week.

On 3/10/08 1:20 PM, "Paul Dann" <address@hidden> wrote:

Have you tried building GnuBG with MacPorts at all?

Paul


Michael Petch wrote:
Re: [Bug-gnubg] cmake
Oh I remember. There was one serious fink flaw regarding pango that I had to hack around. The builds from source refused to build the pangocairo component of pango - because of an autoconf bug on the 10.5 platform.
 
On 3/10/08 2:11 PM, "Michael Petch" <address@hidden> <mailto:address@hidden> wrote:
 
  
Funny thing is, I don’t have issues with autotools on OS/X. I recently upgraded my PPC system to OS/X 10.5, downloaded the fink libraries, dev and utilities needed did an autogen and except for a few minor issues the source built fine (Using sources from CVS). One issue has been corrected regarding the inclusion of multithreaded headers (That someone else on this forum had issues with as well), another had to do with an extra linker change needed on 10.5 OS/X, a bug with SSE on PPC (SSE doesn’t exist on PPC Mac’s since PPC use AltVec), and lastly a bug involving the Multithreaded code. There is a piece of assembler in the multithreaded code that uses an X86 specific instruction that doesn’t apply on PPC Mac’s (It is used for stack alignment). The current checks for __APPLE__ are insufficient since some code is not suited for the PPC platform (I’ll see about putting away changes to address this).
 
I am trying to narrow down a Priority 1 bug that causes a GUI hang issue that is preventing me from distributing a new binary. Hopefully next weekend I’ll get a chance to look at it.
 
Michael
 
On 3/10/08 7:55 AM, "Paul Dann" <address@hidden> <mailto:address@hidden>  wrote:
 
  
Hi Christian,
 
  Thanks for your reply.  I was starting to pull my hair out trying to get gnubg's autogen to work in MacOS X (Linux was OK).  I'm sure it's possible to make it work, but my heart sank at the prospect of delving further into autotools.  Given how much easier CMake is to work with, I thought I'd try my hand at porting, and it's been pretty successful so far.
 
  Anyway, given that CMake will happily live alongside autotools, I thought someone might be interested in some preliminary work on this.  For those that aren't aware, some benefits of CMake are:
 
* simpler configuration files
* truly cross-platform (no need for complete GNU toolchain (eg MSYS) in Windows)
* generates native project files (Makefiles / XCode projects / VC++ projects)
* interactive configuration
* prettier output (including progress in %)
 
  Check Wikipedia for more info :)  Oh, and I can provide a tarball of my current effort if people want to have a look without installing Git.
 
  I don't think KBackgammon made the migration to CMake.  I don't see it in KDE SVN anyway.  Regardless, I'd like to see a truly cross-platform Qt Backgammon.
 
Paul
 
Christian Anthon wrote:
  

On Mon, Mar 3, 2008 at 5:12 PM, Paul Dann <address@hidden> <mailto:address@hidden>  <mailto:address@hidden>  wrote:
  
 
  

  I don't know if this will be of interest to any of you, but I'm
 planning to use the GnuBG engine for a Qt Backgammon program, and having
 no experience maintaining an autotools-based build system, I decided to
 port GnuBG to CMake.
 
    
 
 
 
 
Hi Paul,
 
the autotools system should work on most platforms. The cvs version
may work better than 0.15. If you insist on building gnubg with cmake
you should look at the configure.in and Makefile.am in the main
directory and the Makefile.am in the lib/ directory. The resulting
config.h should also be of help.
 
I believe that the kde backgammon program interfaces with gnubg in
some way, so you may find guidance on that subject there. Also
remember that gnubg is released under the GPL license so if you do
anything beyond interfacing with it, your program should be GPL'ed as
well.
 
Christian.
 
  
 

 

_______________________________________________
Bug-gnubg mailing list
address@hidden
 http://lists.gnu.org/mailman/listinfo/bug-gnubg
 


 
Michael Petch
Quortech Solutions Ltd.
Cell: (403)804-5700
Home: (403)209-1628
Off:  (403)516-2612
 
 
This e-mail is the property of QuorTech Solutions, Inc. and iTechnology Customer Service and Support, Inc. and may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender and delete all copies of the message.
 
 

_______________________________________________
Bug-gnubg mailing list
address@hidden
 http://lists.gnu.org/mailman/listinfo/bug-gnubg
 


 
Michael Petch
Quortech Solutions Ltd.
Cell: (403)804-5700
Home: (403)209-1628
Off:  (403)516-2612
 
 
This e-mail is the property of QuorTech Solutions, Inc. and iTechnology Customer Service and Support, Inc. and may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender and delete all copies of the message.
 





Michael Petch
Quortech Solutions Ltd.
Cell: (403)804-5700
Home: (403)209-1628
Off:  (403)516-2612


This e-mail is the property of QuorTech Solutions, Inc. and iTechnology Customer Service and Support, Inc. and may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender and delete all copies of the message.

reply via email to

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