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: Thu, 01 Jan 2004 00:07:00 -0000 [thread overview]
Message-ID: <5.1.0.14.0.20031231164636.01eee008@link-comm.com> (raw)
In-Reply-To: <3FF34E99.4060800@msu.edu>
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,
At 05:32 PM 12/31/2003 -0500, you wrote:
>Mark,
>
>Can you tell me your build steps and/or send me your build config file? I
>would like to try building at least nanox and see if it would be useful to
>distribute via Cygwin's setup.exe. Please send the config file to me
>privately if it is larger than 25 KiB.
>
>Thanks,
>
>Harold
>
>Mark Mussetter wrote:
>>Hello Everyone,
>>I'm running Cygwin on a Windows 2000 machine and I'm trying to get
>>MicroWindows going. My problem is that I'm getting the following error:
>>***
>>make[1]: *** No rule to make target `/usr/X11R6/lib/libX11.a', needed by
>>`/microwindows/microwindows-0.90/src/bin/nano-X'. Stop.
>>***
>>I do have "libX11.dll" but can't find the "libX11.a" library anywhere.
>>We've updated our Cygwin this morning using the Cygwin setup utility so I
>>think we are as current as we can be. We've done a search on the entire
>>Cygwin directory and "libX11.a" is nowhere to be found.
>>Can someone point me in the right direction to solving this problem?
>>Thanks in advance for any help,
>>
>>Mark Mussetter
>>Link Communications, Inc.
>>email: <mailto:mark@link-comm.com>mark@link-comm.com
>>phone: (406) 245-5002 ext 105
>>Fax: (406) 245-4889
>
>Mark Mussetter
>Link Communications, Inc.
>email: <mailto:mark@link-comm.com>mark@link-comm.com
>phone: (406) 245-5002 ext 105
>Fax: (406) 245-4889
next prev parent reply other threads:[~2004-01-01 0:07 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 [this message]
2004-01-01 0:27 ` Harold L Hunt II
2004-01-02 15:42 ` Mark Mussetter
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.20031231164636.01eee008@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).