"Aaron M. Renn" <[EMAIL PROTECTED]> writes:
> Brian Jones wrote:
> > > The problem with Option 2 is that it requires that the user have JavaDeps
> > > installed in order to build because the maintainer build options rebuilds
> > > the .deps file, which is something few people will want to do.
> >
> > Does it require this? The reason I say this is because the user
> > wouldn't have a target to be made in /lib at all in the distribution.
> > Only if the user configured the maintainer version would it require it
> > and then we're prefectly within our rights to require anything we want
> > to make the build work according to the GNU coding documentation.
>
> What I'm saying is that if the person does an --enable-maintainer-build in
> order to create the target in lib that rebuilds the classes (perhaps because
> he wants to recompile the classes to fix a bug), then he needs JavaDeps
> because enable-maintainer tries to rebuild the .deps file. We need to be
> able to compile the classes without rebuilding the .deps file IMO.
Okay, so we probably need another configure option which avoids
rebuilding .deps and does the compile and the default should be to not
recompile the java classes. I think I understand now.
> BTW: Were you able to build and get things running with what is in there
> now? Did you try a make dist and a build from the distribution file that
> creates? We should probably make sure that things are working for someone
> besides me first before we try to perfect the process.
I had some trouble with the Japhar+Classpath stuff resulting in a bus
error. I've not tracked down the problem yet. I've also not done a
make dist recently, did you fix that one little problem (which wasn't
elaborated upon) that you were having?
Brian
--
|-------------------------------|Software Engineer
|Brian Jones |[EMAIL PROTECTED]
|[EMAIL PROTECTED] |http://www.nortel.net
|http://www.classpath.org/ |------------------------------
