public inbox for rhug-rhats@sourceware.org
 help / color / mirror / Atom feed
From: Gary Benson <gbenson@redhat.com>
To: rhug-rhats@sources.redhat.com
Subject: Properties files
Date: Fri, 13 Dec 2002 03:20:00 -0000	[thread overview]
Message-ID: <20021213111954.GA18208@redhat.com> (raw)

Hi all,

I just spent a couple of days chasing what I thought was a gcj bug but
that turned out not to be.  Some of the packages have .properties
files as well as .java files, and these are dealt with in the
Makefiles as follows:

| FOOBAR_PROP_S = \
| file1.properties \
| file2.properties
| 
| FOOBAR_PROP_O = $(FOOBAR_PROP_S:.properties=.o)
| 
| %.o: %.properties
|      $(top_srcdir)/mkinstalldirs `dirname $@`
|      $(GCJ) --resource `echo $< | sed "s/.*\/src\/share\///g"` -o $@ -c $<
| 
| lib_bar_foo_la_LIBADD = $(FOOBAR_PROP_O)

Now, Tomcat 4 has one case where there exists File.java and
File.properties, meaning that they both compile to the same .o file.
This causes all sorts of 'multiple definition of File' and 'File
changed size from 46 to 22 bytes in File.o'

To avoid this in future I'd like to make the following changes to all
packages that have .properties files.

1. Change FOOBAR_PROP_O = $(FOOBAR_PROP_S:.properties=.o)
       to FOOBAR_PROP_O = $(FOOBAR_PROP_S:.properties=_prop.o)

2. Change %.o: %.properties
       to %_prop.o: %.properties

Any objections?

Cheers,
Gary

[ gbenson@redhat.com ][ GnuPG 85A8F78B ][ http://inauspicious.org/ ]

             reply	other threads:[~2002-12-13 11:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-13  3:20 Gary Benson [this message]
2002-12-13 10:49 ` Anthony Green
2002-12-15 23:45   ` Gary Benson

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=20021213111954.GA18208@redhat.com \
    --to=gbenson@redhat.com \
    --cc=rhug-rhats@sources.redhat.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).