public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Harold L Hunt II <huntharo@msu.edu>
To: discuss@nedit.org
Cc: cygx <cygwin-xfree@cygwin.com>
Subject: Cygwin/X NEdit package maintainership
Date: Fri, 02 Jan 2004 05:29:00 -0000	[thread overview]
Message-ID: <3FF501A6.40101@msu.edu> (raw)

It might be wise if someone from the NEdit project would review the 
Cygwin/X NEdit package.  The goal would be to determine if the Cygwin/X 
NEdit package has any common or easily detectable platform-dependent bugs.

To download the NEdit source package for Cygwin/X, grab the package from 
the following link, or take note of the directory that it is in and find 
another mirror in the list at cygwin.com.  You can also use Cygwin's 
setup.exe to grab the NEdit source package and it will be automatically 
unpacked in /usr/src.

http://mirrors.kernel.org/sources.redhat.com/cygwin/release/XFree86/nedit/nedit-5.4-1-src.tar.bz2

If you grabbed the source package manually, move it to /usr/src and 
unpack it with 'tar xjf nedit-5.4-1-src.tar.bz2'.

Check the file nedit-5.4/CYGWIN-PATCHES/nedit.README for information on 
which packages are required at build-time.

Build the package with the following set of commands:

./nedit-5.4-1.sh prep && ./nedit-5.4-1.sh conf > conf.log 2>&1 && 
./nedit-5.4-1.sh build > build.log 2>&1 && ./nedit-5.4-1.sh install > 
install.log 2>&1

Now you should have a directory full of the .o files that can be used to 
make incremental builds if you find fixes that need to be made.

Please carefully note any problems that you find and send them to both 
lists that this message was sent to.

Thanks for your help,

Harold


             reply	other threads:[~2004-01-02  5:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-02  5:29 Harold L Hunt II [this message]
2004-01-02 20:41 ` Nathan Gray
2004-01-02 22:15   ` Harold L Hunt II
2004-01-02 23:39     ` Nathan Gray
2004-01-03  3:29       ` Harold L Hunt II

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=3FF501A6.40101@msu.edu \
    --to=huntharo@msu.edu \
    --cc=cygwin-xfree@cygwin.com \
    --cc=discuss@nedit.org \
    /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).