public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Mark Mussetter <mark@link-comm.com>
To: cygwin-xfree@cygwin.com
Subject: Re: problems with libX11.a
Date: Fri, 02 Jan 2004 15:42:00 -0000	[thread overview]
Message-ID: <5.1.0.14.0.20040102082344.00a8e6f8@link-comm.com> (raw)
In-Reply-To: <3FF36948.1020002@msu.edu>

Harold,

Sorry I forgot about that part.  The 'nbreaker' demo seemed to be the only 
demo causing problems and we were under some pressure to get the project 
built, so we moved the 'nbreaker' demo out of the demo directory so it 
wouldn't try to be built with the rest of the project.

I did some looking before removing the demo and found that 'GR_PIXMAP_ID' 
is NOT defined in any header.  I found a reference to 'GR_PIXMAP_ID' in the 
file 'original_mini-x.txt' which discussed all of the TYPEDEFS in the 
project.  This led me to the 'nano-X.h' header, which defines all of the 
other defines listed in 'oringal_mini-x.txt.'  I noticed that the comment 
on the typedef for 'GR_WINDOW_ID' mentioned that it was a "window or pixmap 
id."  I am assuming that if you were to define 'GR_PIXMAP_ID' in the same 
fashion as 'GR_WINDOW_ID' that you might be able to get the project to 
build...we just didn't have time to explore that option.

Mark


At 07:26 PM 12/31/2003 -0500, you wrote:
>Mark,
>
>Thanks, those instructions work until it gets to the 'nbreaker' demo:
>
>Linking /home/harold/x-devel/ports/MicroWindows/build/src/bin/launcher ...
>Updating dependencies in 
>/home/harold/x-devel/ports/MicroWindows/build/src/demos
>/nbreaker ...
>Compiling animate.c ...
>In file included from animate.c:41:
>nbreaker.h:160: error: syntax error before "GR_PIXMAP_ID"
>nbreaker.h:160: warning: no semicolon at end of struct or union
>nbreaker.h:161: warning: type defaults to `int' in declaration of `a'
>nbreaker.h:161: warning: data definition has no type or storage class
>nbreaker.h:171: error: syntax error before '}' token
>
>
>Seems that GR_PIXMAP_ID is not defined in the included headers.  Can you 
>describe how you worked through this?
>
>Harold
>
>Mark Mussetter wrote:
>
>>Hi Harold,
>>Thanks for your help.  We were able to get MicroWindows running after you 
>>pointed us in the right direction.  We already had the Xfree86-prog 
>>package but you comments about trying to link explicitly to libX11.a led 
>>us to the problem.  The following is a clip from Makefile.rules:
>>ifeq ($(X11), Y)
>>DEFINES += -DX11=1
>>ifneq ($(ARCH),CYGWIN)
>># Cygwin can't use this - the -lX11 needs to be specified
>># *after* the object files that use it, but this inserts
>># it at the start.  For Cygwin, we will add libX11.a to the
>># library list instead.
>>LDFLAGS += -L/usr/X11R6/lib -lX11
>>else
>>MW_CORE_LIBS += /usr/X11R6/lib/libX11.dll.a
>>endif
>>ifeq ($(ARCH),FREEBSD-X86)
>>INCLUDEDIRS += -I/usr/X11R6/include
>>endif
>>ifeq ($(ARCH),CYGWIN)
>>INCLUDEDIRS += -I/usr/X11R6/include
>>endif
>>endif
>>We changed the 10th line to its current state.  It used to say 
>>"MW_CORE_LIBS += /usr/X11R6/lib/libX11.a"
>>Once we made that change everything else fell into place and we were able 
>>to run the demos.
>>My steps were:
>>1. cd microwin/src
>>2. Typed "cp Configs/config.cygwin config" for the cygwin configuration.
>>    See CONTENTS and Configs/README for more information.
>>3. Typed "make"
>>4. Change the Makefile.rules file to link against libX11.dll.a instead of 
>>libX11.a
>>5. Typed "make"
>>4. Ran ./demo.sh
>>
>>Thanks again for your help,


      reply	other threads:[~2004-01-02 15:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-31 22:34 Mark Mussetter
2003-12-31 23:14 ` Harold L Hunt II
2003-12-31 23:23 ` Harold L Hunt II
2004-01-01  0:07   ` Mark Mussetter
2004-01-01  0:27     ` Harold L Hunt II
2004-01-02 15:42       ` Mark Mussetter [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5.1.0.14.0.20040102082344.00a8e6f8@link-comm.com \
    --to=mark@link-comm.com \
    --cc=cygwin-xfree@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).