First, my thanks to Robin for his persistance in trying to get this to work.
At 9:19 AM +1200 8/15/02, Alex Shepherd wrote:
The problem here is that the project file has a reference to a bunch of
libraries but with JBuilder Personal it does not allow per project library
definitions only personal global definitions. (to provoke you to buy the
next version) so It is looking for the library definition in your personal
home directory (where ever Windows decides that is) This is something you
have to do personally as I am not sure how we could convinve WinCVS to put
the library definition there.
OK, this makes more sense to me now. For the record, JBuilder is putting this type of information in
C:\Documents and Settings\jake\.jbuilder7
on my son's PC running XP. (He gave me an account called "jake"). I've also seen it stored in
C:\Documents and Settings\Owner\.jbuilder7
C:\Documents and Settings\All Users\.jbuilder7
C:\.jbuilder7
This is the problem with automagically installing files on Windows; it's _really_ hard to figure out where they go! We have a similar problem with the JMRI preferences. I solved that by having them stored the first time the program starts up, but JBuilder doesn't do that.
Robin was also having a couple of problems with what JBuilder choses to build. I've added a bunch of explicit entries to the project definition jmri.jpx file and committed it back to CVS. Hopefully that will fix the "class not found" problems.
Perhaps this recipe will now work (if so, we should write it out in more detail):
Start from scratch with a new folder.
check out the source from CVS
move the project/java/lib file to somewhere convenient, away from
the project folder. (This is to avoid confusion later on,
because we're going to make a global config point to the
contents) (_Don't_ move the project/lib file, that's needed at
runtime)
Start JBuilder. Immediately select Project -> Project Properties,
click on the Build pane, then the Required Libraries pane within that.
JMRIlibraries will be shown in red. Click it and hit Edit.
On the resulting "class" tab, click "add" and add each of the
.jar files from your moved lib file. There are seven of them,
and you have to add each one.
click OK, click OK
From the main menu, click Project -> Rebuild
Click the "diamond" to run the JmriDemo program.
At this point, you should have a working app. Configure it, save and restart.
Also, you can run the pure DecoderPro app by sliding down the upper right box to the DecoderPro.java file, clicking it to open on the right, right-clicking the DecoderPro tab to select "Run with jmri defaults".
Hopefully, this all works... Its a pain to set up the libraries, but apparently the free JBuilder requires absolute path names in its library-definition file. That makes it really hard for us to provide one that you can just move into place.
At 10:44 AM +1200 8/15/02, Alex Shepherd wrote:
If all this turns out to be too difficult, then if we moved to an ANT based
build (which is also supported in JB7) then those who do not have JB Pro or
Ent could maybe download the Java IDE at and develop
using this. Using ANT would be more work but it would give us more control.
People could even just download a JDK and ANT and use Notepad to edit the
code and call ANT from the command line, like many UNIX users have done for
the last 30 years...
Mike Davison get this to work a little while back. If you've got ant installed, you can do a
cvs -d :pserver:anonymous@...:/cvsroot/jmri co ant
ant jmridemo
to checkout, build and run the program. "ant decoderpro" does the obvious thing too. I've not tried it on Windows, but it worked this morning on MacOS X and Linux.
Bob
--
--------------
Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)
Bob Jacobsen