Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place! |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
07-04-2003, 04:19 PM
|
#1
|
LQ Newbie
Registered: Jun 2003
Posts: 20
Rep:
|
Binaries? Source code?
Hi!
I was wondering what was exactly the difference between a binary and source. Because they often give you the choice to download the binaries or the source.
Is there a difference in the installation procedures? One is an executable, the other one is not? What do i need to download if i want to run the application?
Thx, i'm very confused.
Jo_Nak.
|
|
|
07-04-2003, 04:21 PM
|
#2
|
Senior Member
Registered: Jun 2003
Location: California
Distribution: Slackware
Posts: 1,181
Rep:
|
The source code is simply that; all the code that the program uses to run. These files (generally tar.gz) need to be gunzipped, untarred, and then generally ./configure 'd, make 'd, and make install 'd. Think of binaries like Windows .EXE files; it's the executable part of the program. With the source code, though, it is possible to customize the install and tailor it to your needs through the ./configure process
|
|
|
07-04-2003, 04:40 PM
|
#3
|
LQ Guru
Registered: Mar 2003
Location: New Jersey
Distribution: Arch Linux
Posts: 1,445
Rep:
|
Programmers write programs in source code. C, Java, etc. Unfortunatly, computers actually can not read this code, its only "human readable".
Computers speak in machine code (binary, 0s and 1s). So a binary is just that. A program where the source code has been converted ("compiled" is the usual term) into machine ready code.
When you compile (./configure, make) something, all you are doing is converting source --> binary. So a binary makes it easier for you.
|
|
|
07-04-2003, 06:17 PM
|
#4
|
Member
Registered: Jul 2003
Location: London
Posts: 548
Rep:
|
If you're a newbie, I strongly suggest using some sort of binary. That way, you can get help keeping track of dependencies. Personally, having gone through depency hell already, i now use debian, with it's handy apt-get feature. to install something, just apt-get <package>. That way, it'll automaticaly install any dependencies for you.
|
|
|
All times are GMT -5. The time now is 10:47 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|