Usage: javac <options> <source files>
where possible options include:
-g Generate all debugging info
-g:none Generate no debugging info
-g:{lines,vars,source} Generate only some debugging info
-O Optimize; may hinder debugging or enlarge class file
-nowarn Generate no warnings
-verbose Output messages about what the compiler is doing
-deprecation Output source locations where deprecated APIs are used
-classpath <path> Specify where to find user class files
-sourcepath <path> Specify where to find input source files
-bootclasspath <path> Override location of bootstrap class files
-extdirs <dirs> Override location of installed extensions
-d <directory> Specify where to place generated class files
-encoding <encoding> Specify character encoding used by source files
-target <release> Generate class files for specific VM version
Originally posted by Peter Tran:
If you can execute java, then you should be able to execute javac, because they are both in the jdk1.2.2\bin directory. If you type javac, do you see the following?
If yes, then your path is fine.
-Peter
"JavaRanch, where the deer and the Certified play" - David O'Meara
Do not use cute names like "Justin Case" or "Adam Baum". Do not use the names of celebrities.
SCJP
Visit my download page
Originally posted by Randall Twede:
Buffalo Bill,
Your name does not comply with the Javaranch naming guidelines which can be found at http://www.javaranch.com/name.jsp
In particular
Do not use cute names like "Justin Case" or "Adam Baum". Do not use the names of celebrities.
please register again with a valid name.
"JavaRanch, where the deer and the Certified play" - David O'Meara
-Nate
Write once, run anywhere, because there's nowhere to hide! - /. A.C.
My pie came with a little toothpic holding up this tiny ad:
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com
|