Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
How do i compile Java in OSX?
- Thread starter jethroted
- Start date
- Sort by reaction score
mnkeybsness
macrumors 68030
you'll need a java program compiler. i use codewarrior, but you can try getting something free like bluej from www.versiontracker.com
Okay, here's what you do.
1st, you've got to find the main file. Sometimes it's labeled main, or the name of the program. It will be a .java file. Go in to terminal, and go to the file.
Then once you've found the file you type:
javac <filename.java>
This will create a .class file in the same directory as the .java file you compiled.
Then type java filename (do not put .class or .java after it).
This should complie and run the program. Let me know if you have any problems.
Physicsnerd
1st, you've got to find the main file. Sometimes it's labeled main, or the name of the program. It will be a .java file. Go in to terminal, and go to the file.
Then once you've found the file you type:
javac <filename.java>
This will create a .class file in the same directory as the .java file you compiled.
Then type java filename (do not put .class or .java after it).
This should complie and run the program. Let me know if you have any problems.
Physicsnerd
from the readme:
This is not a program like you think it is. This is an API. What these files let you do is write programs that can access the different fuctions of GNUTella. However, it is not a GNUTella client. Atleast it doesn't look to be. Can anyone verify my conclusion?
Physicsnerd
This is not a program like you think it is. This is an API. What these files let you do is write programs that can access the different fuctions of GNUTella. However, it is not a GNUTella client. Atleast it doesn't look to be. Can anyone verify my conclusion?
Physicsnerd
zimv20
macrumors 601
well, you could find a program someone else wrote to use the library, but in general, yes.
a jar is simply a collection of pre-compiled java files. it's akin to a unix .so library or (the dreaded) windows .dll.
like those, you put the jars in a known place and direct your java environment to that place (i think the environment variable is JARPATH, but i haven't done any java in 4 years).
i recommend buying a java book and doing some reading. (sorry, i have no recommendations on which book)
zimv20
macrumors 601
the jar _is_ the "binary."
errrr.... it is that simple. except when you're sharing code across executables, then you need to get into libraries (jarfiles, in the case of java).
and the added complexity that java runs in a virtual machine. but that complexity shouldn't affect you (since you're not writing something on the magnitude of a compiler).
buy a book. start small.
I guess that is what i'll have to do, although i didn't really want to get into programing, I just wanted to run an app. I realize they released the source code so developers could work on it, but they should have released an executable file as well so people who just want to run the app could do so.
as has been stated above, you didn't download an app. there is nothing to run, nor can there be. you downloaded an extension, or Application Programming Interface (API), that allows you to program with more features (objects, methods).
here's a WAY out there example....
you're writing the matrix, and you have a human named Guy New that you need to create. in the existing matrix code (java) there is no way to make Guy move. so, you download a human api that includes the ability for a human move. now you can use... humanGuyNew.Move()
where you couldn't before you had this api you downloaded.
also, i saw a post earlier about javac. you actually should run javac at the same directory level as the directory that contains the .java files. example--navigate to the directory that is at the same level as this directory, then type...
javac directory/filename.java
Taft
macrumors 65816
The problem here is that you don't understand the basic concepts of what a program is. Read the following very carefully...
What you downloaded was NOT an application or even the source to an application. You downloaded a bunch of code that other applications can use. This is often called an API, or a library, or a .dll, etc. Think of it as a bunch of compiled code that other applications can run. As an example, Cocoa is an API similar to this application. It provides Mac OS X programmers a bunch of code which makes creating GUI's much easier.
Second, the code you downloaded wasn't packaged very well. There was no makefile or ANT script or any other device to easily compile the code or run it. This isn't your fault: the prorammers are to blame. Even if this was code you wanted (you don't want it, by the way), there wouldn't have been an easy way to compile/install/run it.
Taft