From: Tom Tromey <tromey@redhat.com>
To: Marc Boorshtein <marc.boorshtein@octetstring.com>
Cc: eclipse@sources.redhat.com
Subject: Re: ant support?
Date: Mon, 04 Aug 2003 18:54:00 -0000 [thread overview]
Message-ID: <874r0xmf96.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1060018592.5749.12.camel@ldap.myhost.com>
>>>>> "Marc" == Marc Boorshtein <marc.boorshtein@octetstring.com> writes:
Marc> ok, thanks! this might sound like a dumb question, but how do I
Marc> apply this patch? I've never worked with patches and rpms.
Hmm, there's no simple way to explain it. In the below I assume
you're going to go out on the net (or man pages or whatever) and read
up about rpmbuild, patch, etc.
The simplest thing to do is to make a new eclipse source file and
then rebuild.
So first, install (rpm -i) prepare the SRPM (rpmbuild -bp).
The new eclipse build directory will be ../BUILD/eclipse-something.
Go to the ant plugin subdirectory: plugins/org.eclipse.ant.core.
Apply the patch with "patch -p0 < patch-file".
Now go back to the eclipse build directory (../..).
Run:
./build -bc /usr/share/java/libgcj-3.5-tree-ssa.jar -arch x86 -os linux -ws gtk -target makeSourceTarball
This will make a new eclipse-src.tar.gz file (in "..").
Copy this over the eclipse-src.tar.gz in SOURCES.
Now go to SPECS and do a full eclipse build ("rpmbuild -ba
eclipse-blahblah.spec").
I know that's pretty brief, but I don't have time to go into all the
details. I'm afraid you'll have to do a lot of the legwork on your
own.
For this to work you'll need the ant RPM (and all its dependencies)
installed. You'll also need gcc-ssa and friends.
Tom
next prev parent reply other threads:[~2003-08-04 18:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-04 16:23 Marc Boorshtein
2003-08-04 17:26 ` Tom Tromey
2003-08-04 17:43 ` Marc Boorshtein
2003-08-04 18:54 ` Tom Tromey [this message]
2003-08-04 18:56 ` Marc Boorshtein
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=874r0xmf96.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=eclipse@sources.redhat.com \
--cc=marc.boorshtein@octetstring.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).