Tommy Reilly <[EMAIL PROTECTED]> writes:
> I know you guys are super busy but what are the chances of getting you
> to set up one of those cvsweb interfaces (so people can browse the
> tree without checking it out)?
I think a lot of people are using the same stuff the Linux project
does to do the same. That code has something to do with parsing C/C++
files and doesn't really handle Java. I know that someone has made
changes which allow it to work with Java, but I've not followed up on
this since.
If you just want a checkout of the CVS tree available on the web using
Indexes and Apache I can do that without any problems. If you want
what I was talking about before, I'll need some guidance since I've
not had the time to look into this any more for a while.
> I've been raving about the
> autoconf/automake/libtool/jdeps set up you guys got to the Apache
> JServ folks (java.apache.org). I'm doing the build environment and
> want to do something similiar.
That's a fairly flattering comment for all of us since all of us
contribute to making the build process work. I think we're just
trying to make something which works and it will be refined over time.
> Who's primarily responsible for the build setup you guys got? Are you
> using the standard versions of all these tools? I tried to build this
> stuff on my Solaris box and configure bombed out:
>
> checking for Guile... ./configure: guile-config: not found
> configure: cannot find guile-config; is Guile installed?
I'm responsible for sticking in that Guile bit. Paul's testsuite
stuff requires you have the most recent release of Guile installed. A
proper install of this Guile will give you the necessary
autoconf/automake macros. You can pick up Guile from prep.ai.mit.edu
of course. It looks like the testsuite is still not nailed down since
we're going to be developing a testsuite similar to the JCK (my guess)
with Transvirtual and Cygnus (this info is from the web pages).
We're using automake 1.3, autoconf 2.12, and Guile 1.2.91 -> 1.3.
I've been doing a lot of the configure.in work and the working
involving using jdeps to make the Java compile go. We still have some
work to do with the native compile and then plenty to do on the
install stuff. Configure.in needs a lot of work as well for different
VMs and compilers.
> I built and installed guile but don't have a guile-config file
> anywhere. What's this supposed to be? In what capacity is guile
> being used? The hackers guide doesn't say anything about it.
After you've installed Guile, try running `aclocal;automake;autoconf'
in the buildroot directory for Classpath. Configure shouldn't bomb
after that.
> As soon as we get 1.0b1 of JServ out the door I plan on investigating
> using classpath/japhar instead of Sun's JDK. This along with a
> Solaris port should hopefully make up for picking your brains and
> copying your build environment now. This will have to wait until I
> graduate in December though.
That falls in line with our timeline fairly well (I'm guessing).
> I've heard of a free JSDK floating around. When do guys suspect
> you'll be ready for extensions like this?
Someone else wanna take this one?
About JDK 1.0.2. This would presumably make you inelligible from
contributing code to the project when that code is replacing 1.0.2
functionality. Later extensions such as Swing shouldn't be covered,
but Paul and the FSF can probably answers the questions completely
after reviewing the agreement you signed.
Brian
--
|-------------------------------|Software Engineer
|Brian Jones |[EMAIL PROTECTED]
|[EMAIL PROTECTED] |http://www.nortel.net
|http://www.classpath.org/ |------------------------------
