Re: getting started with classpath
Hi! On Don, 25 Apr 2002 Brian Jones wrote: > Nic Ferrier <[EMAIL PROTECTED]> writes: > > > Maybe Brian or Anthony (or one of the other maintaienrs) should chip > > in here's a menu of things that are on my list of stuff to do but > > that I haven't got round to yet: > > > > - html and texinfo "getting started with Classpath and ORP" guide. I know I'm asking for a lot, but don't you think it would be worth to add some documentation on how to get started on a specific platform? I recently tried to get classpath running on a Mandrake 8.1 distro. No luck so far, since compiling automake, autoconfm glib etc. from scratch was not enough to get it working (I don't recall the details, but at the moment the gtk libs seem to be the problem). I don't know how complicated it is to use Windows, but I had quite some problems with Linux. > > - a very light webpage intro, an edited version of the above > > > > - add lot's of examples to the CNI section of the GCJ manual > > > > - improve the javadoc in the Classpath source code and create a > > texinfo manual using cp-tools texinfo doclet. > > Some good ideas here, but let's not exclude other JVMs such as SableVM > or kissme. A side question of mine at the moment is whether any of > these support working with the AWT and native peer code other than > GCJ. Don't you think it would be better to focus on one JVM (at least from the Classpath side) and get the AWT running there? Ciao, Andreas ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
Re: getting started with classpath
"Patrik Reali" <[EMAIL PROTECTED]> writes: > From: "Brian Jones" <[EMAIL PROTECTED]> > > Some good ideas here, but let's not exclude other JVMs such as SableVM > > or kissme. A side question of mine at the moment is whether any of > > these support working with the AWT and native peer code other than > > GCJ. > > Jaos has currently no support for the AWT. > Whenever this happens, I will have to provide my own native implementation, > because I'm not running on a *nix system. I think GTK works on Windows. Not sure about any other ports. Brian -- Brian Jones <[EMAIL PROTECTED]> ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
Re: getting started with classpath
From: "Brian Jones" <[EMAIL PROTECTED]> > Some good ideas here, but let's not exclude other JVMs such as SableVM > or kissme. A side question of mine at the moment is whether any of > these support working with the AWT and native peer code other than > GCJ. Jaos has currently no support for the AWT. Whenever this happens, I will have to provide my own native implementation, because I'm not running on a *nix system. -Patrik ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
Re: getting started with classpath
Andreas Rueckert <[EMAIL PROTECTED]> writes: > > Some good ideas here, but let's not exclude other JVMs such as SableVM > > or kissme. A side question of mine at the moment is whether any of > > these support working with the AWT and native peer code other than > > GCJ. > > Don't you think it would be better to focus on one JVM (at least from the > Classpath side) and get the AWT running there? Yes for development, but I thought we were talking about documentation? In the near future we should have support for IBM's JRVM in CVS (and in a release soon after) and at some point Kaffe may work with Classpath as well although that depends on people interested in Kaffe. Brian -- Brian Jones <[EMAIL PROTECTED]> ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
Re: Compilation error - More Info
Hi, Continuing with the compilation problem ... I have installed and usuccessfully tried with 3.0.4 (-bootclasspath '' seems to be invalid but I don't know what to fix there). So I installed jikes 1.15b and it seems to go further, but it doesn't compile either. There seem to be missing classes in javax.swing (at least they are not in CVS). I got: Found 2 semantic errors compiling "../javax/swing/event/InternalFrameEvent.java": 42. import javax.swing.JInternalFrame; <> *** Error: The import "javax/swing/JInternalFrame" is not valid, since it does not name a type in a packag e. Found 4 semantic errors compiling "../javax/swing/event/MenuDragMouseEvent.java": 43. import javax.swing.MenuElement; <-> *** Error: The import "javax/swing/MenuElement" is not valid, since it does not name a type in a package. Among others ... Has anyone had similar problems with the latest version from CVS ? CC --- Carlos Cavanna <[EMAIL PROTECTED]> wrote: > Hi, > > I have just checked out the latest version of > Classpath. > > I run: > > aclocal > autoheader > automake > autoconf > > and > > . ./configure --prefix=... --with-gcj --enable-jni > > Then, when I run "make" I get: > > Making all in lib > make[1]: Entering directory > `/scr1/cavanna/Thesis/classpath/classpath.cvs/classpath/lib' > top_builddir=.. /bin/sh ./gen-classlist.sh standard > /scr1/cavanna/bin/gcc-3.0.2/bin/gcj -bootclasspath > '' -classpath > ..:../vm/current:.: -C -d . @classes > gcj: cannot specify -o with -c or -S and multiple > compilations > make[1]: *** [compile-classes] Error 1 > make[1]: Leaving directory > `/scr1/cavanna/Thesis/classpath/classpath.cvs/classpath/lib' > make: *** [all-recursive] Error 1 > > I am using gcj 3.0.2 > > I did compile previous versions of classpath before, > and I am using the same > commands > I always use. > > Does anyone know about this error ? > > Thanks, > CC > > > ___ > Classpath mailing list > [EMAIL PROTECTED] > http://mail.gnu.org/mailman/listinfo/classpath __ Do You Yahoo!? Yahoo! Games - play chess, backgammon, pool and more http://games.yahoo.com/ ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
Classpath API javadoc
> Thank you so much for your detailed reply. I have a couple of responses > / sub-questions below: > > At 25 April 2002, you wrote: > >We do need more beginner doc. But we are still working hard on getting > >stable, usable versions of GCJ, Classpath, etc... out there and > >working. > > > >One of the things you could help us with is documentation. > > I would actually really like to help with documentation, as I find > this pretty lacking in many of even the very best Free projects (not > slamming anyone, I obviously think that working Free software is > better than no software or no choice, and i understand the volunteer > thing, etc., yadda yadda). > > I think my level of experience with coding versus documentation would > make me a much better contributor as a documenter than coder -- especially > in light of the fact that the things I could code best would be (coincidentally) > the things I am probably the least "clean room" on, since those are > things I've re-implemented before (though i guess not in a clean > room -- you should see my apartment these days). > > I think I write pretty well (sound of my arm breaking as it reaches > around to give me a pat on the back). What would you like help with > or what do you feel is lacking? Is it end-user doc, dev-doc, or > what exactly? Please, if I'm asking too many questions and this > is already answered, I can read some stuff if you forward me a pointer > / link...don't want to be a brain-drainer. There is an issue I have been meaning to raise lately, but never got round to. As part of the Classpath effort we are producing a large amount of javadoc documentation for the standard java class libraries. Unlike Sun, we don't have a reference page that people can use for an API reference (at least not that I know of). I think it's a waste of all the effort that has gone into commenting code, this resource should be made available and people should be encouraged to use it. Not only does it bring awareness to the project, but people can point out incorrect documentation (and potentially incorrect implementations) which is good for the project. On a technical level, all it requires is a daily script to run javadoc against Classpath CVS and a webserver. John Leuner ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
Re: getting started with classpath
> I have a gnawing interest in hacking on classpath, and I have read > a couple of times over the guide "hacking.html" that is linked from > the GNU site. It's just, I'm having a simultaneous-learning-curve > experience, and I'm wondering if anyone on this list can push me > off in the right direction to eventually being able to contribute. > > > My "problems" or rather questions are as follows: > 1. I only have experience using one JDK/JRE (Sun's), although I > have used it on many platforms. I noticed a strong linkage between > Classpath and (of course) the free JVM / compiler implementations. > That's cool, I get it, I am just not sure which components each > of these tools replace, and what their level of compliance / implementation > is. Is there maybe a best order to learn about these tools in? > I would like to know Free Java and work on it even, but am not sure > how to start. Well, I suggest you start with compilers. Try out jikes (it's quite similar to javac in behaviour) and move on from there to kjc. Next try and compile classpath itself. After that, get one of the free JVMs and try to get it to work with Classpath. You can also try out gcj. If you encounter anything 'surprising' with these tools, it's worthwhile to post the list, because ultimately we would want to provide a similar user-experience to that provided by the SUn software. > 2. How can I be certain I meet the "clean room" requirement? I > have browsed through several of sun's classes several times in source > code form as included on my Mac OS X machine. I know that I don't > remember any specifics, they were just instructive at the time. > Does this count? Yes > 3. If I write "pure java" implementations, do I need to worry much > about your notes on native code and VM integration? I have not done > any JNI programming, but I am okay with learning. I guess, a better > question is, what is the view of this project as far as native code, > VM integration, etc.? I get the feeling by browsing the classes > that there isn't much native code in the non-GUI components. Generally we try to minimize use of native code. IMO there are still some classes that could do with pure Java where native code is being used. You don't really need to worry much about native code and VM integration unless you're hacking the 'core' classes. In fact these classes have received the most attention and are probably in the best state. What needs more work is stuff that isn't used so often. > Any "getting started" tips would be much appreciated -- it seems > like there's a lot to learn for someone coming from a pure Sun world > as far as the raw implementation goes. Well, in the Sun world you don't have to worry much about the implementation because it's closed :-) (Ok, maybe the source to the class libraries is available for viewing, but it's not available for potential modification). You might struggle a bit with the various VMs since they are at various stages of maturity and not always in sync with the ever-changing Classpath. Don't hesitate to ask the VM developers or Classpath developers questions about getting things to work. John Leuner ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
Re: Compilation error - More Info
Carlos Cavanna <[EMAIL PROTECTED]> writes: > Has anyone had similar problems with the latest > version from CVS ? > > CC There were some recent checkins a day or two ago that added or merges quite a bit of Swing stuff. It is possible something didn't get included with that commit. Brian -- Brian Jones <[EMAIL PROTECTED]> ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
Re: Classpath API javadoc
John Leuner <[EMAIL PROTECTED]> writes: > > Thank you so much for your detailed reply. I have a couple of responses > > / sub-questions below: > > > > At 25 April 2002, you wrote: > > >We do need more beginner doc. But we are still working hard on getting > > >stable, usable versions of GCJ, Classpath, etc... out there and > > >working. > > > > > >One of the things you could help us with is documentation. > > > > I would actually really like to help with documentation, as I find > > this pretty lacking in many of even the very best Free projects (not > > slamming anyone, I obviously think that working Free software is > > better than no software or no choice, and i understand the volunteer > > thing, etc., yadda yadda). > > > > I think my level of experience with coding versus documentation would > > make me a much better contributor as a documenter than coder -- especially > > in light of the fact that the things I could code best would be (coincidentally) > > the things I am probably the least "clean room" on, since those are > > things I've re-implemented before (though i guess not in a clean > > room -- you should see my apartment these days). > > > > I think I write pretty well (sound of my arm breaking as it reaches > > around to give me a pat on the back). What would you like help with > > or what do you feel is lacking? Is it end-user doc, dev-doc, or > > what exactly? Please, if I'm asking too many questions and this > > is already answered, I can read some stuff if you forward me a pointer > > / link...don't want to be a brain-drainer. > > There is an issue I have been meaning to raise lately, but never got round to. > > As part of the Classpath effort we are producing a large amount of javadoc >documentation for the standard java class libraries. Unlike Sun, we don't have a >reference page that people can use for an API reference (at least not that I know >of). I think it's a waste of all the effort that has gone into commenting code, this >resource should be made available and people should be encouraged to use it. Not only >does it bring awareness to the project, but people can point out incorrect >documentation (and potentially incorrect implementations) which is good for the >project. > > On a technical level, all it requires is a daily script to run javadoc against >Classpath CVS and a webserver. Personally I think that the javadoc should be done per release, which I guess is why it hasn't been done yet. The cp-tools guys are well on the way to having the texinfo doclet working which will make the javadoc accessible from info and emacs. Nic ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
