[Questions] about compiling

[V!persting]

I have some questions about compiling.

1) What does compiling actually mean?
2) Why use compiling? what is so good about it?
3) What does compiling do?

srry for those noob questions, but im about to start to follow some simple compile guides to learn it. but i dont get a clue what it is.

[Le Froid]

1) Compiling means putting source codes together into a computer-readable language, without compiling you would need to know what

MZ       ÿÿ  ¸       @                                     º ´ Í!¸LÍ!‹
ÔARÿU‹V‹n@‹
ÔA‹Â+ÅÇD$@   ?ÇD$8   ?ÇD  À>ÇD  À>‹)jL$<Qƒì‹Ì‰9‰A‰Y‰Q‹V8‹
ÔARÿU_^][ƒÄHÃÌÌÌÌÌÌÌV‹ñ‹‹Qô…ҍAðW‹8tLS‹XP…Û[} ‹Aø…À}
hW €èöÿÿÇAô    ‹_Æ  ^ÃÉÿðÁ
I…É‹‹PÿR‹‹ÏÿPƒÀ‰_^ÃÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌQS‹ƒëU‹k‰L$‹‹VÿP‹t$‹jV‹Èÿ…ÀuèSøÿÿ;î}‹õN‹ÑWÁéx‰|$só¥‹Êƒáó¤‰hCƒÉÿðÁI…É_‹‹SÿR‹D$‹L$^]‰[Y ÌÌÌÌÌVW‹|$‹ñ‹‹Hð‹ƒèjWPÿR…ÀuèÞ÷ÿÿƒÀ_‰^ ÌÌÌÌ‹ƒèHƒÊÿðÁJ…Ò‹‹PÿRÃÌÌÌ‹‹T$ƒèV‹p;ò~‹Öƒx^~ ‰T$é
ÿÿÿ‹@;Â}=   ~   ëÀ;Â}‹Â‰D$égÿÿÿ ÌÌÌÌV‹ñ‹F8ƒèÇ„HƒÊÿðÁJ…Ò‹‹PÿR‹F4ƒèHƒÊÿðÁJ…Ò‹‹PÿR‹F$ƒèHƒÊÿðÁJ…Ò‹‹PÿR‹v ƒîFƒÉÿðÁI…É‹‹VÿR^ÃÌ¡ BV‹ñ¹ BÿPƒÀ‰‹Æ^ÃÌÌÌÌÌÌÌV‹ñÇÀ¡ B¹ BÿPƒÀ‰F ‹ B¹ BÿRƒÀ‰F$3À¹   ‰F(‰F,ˆF‰F‰F‰F‰F‰N‰N‹Æ^ÃÌÌÌÌÌÌÌÌÌÌV‹ñè˜ÿÿÿÇ„¡ B¹ BÿPƒÀ‰F4‹ B¹ BÿRƒÀ‰F8€N13À‰FD‰FL‰FH‰FPÇF<   ÇF@   ‹Æ^ÃÌÌÌÌÌÌÌV‹ñ…ötè”þÿÿVètÌ  ƒÄ^ÃÌÌÌÌÌÌÌÌÌV‹ñ‹‹Püƒè¹   +Ê‹P‹D$+**Ê}P‹Îè þÿÿ‹^ ÌÌÌS‹$…ÛU‹éu
è¯üÿÿ][ ‹T$…Òu
hW €èHóÿÿ‹E V‹ò+ð¹   +HüW‹xô‹@ø+ÃÈ}S‹Íè³ýÿÿ‹T$;÷‹E wS0QPÿƒÄë‹Ë‹ò‹ÑÁé‹øó¥‹Êƒáó¤…Û_^|›‹E ;Xø“‰Xô‹E ]Æ [ ÌÌÌÌÌÌ‹T$…ÒW‹ùu3ÀPRèLÿÿÿ‹Ç_ ‹ÂVpŠ

means

2)Look at 1...also, it is the ONLY way to make programs and .exe's NOTHING in your comp would run without it

3) read 1 and 2

[quickx]

1) What does compiling actually mean?
Basically putting the code of something together in a working form.

2) Why use compiling? what is so good about it?
It put whatever you'r wanting to use together in a working form. Basically (for ascent) it makes the server files (.exe/.confs and the rest).

3) What does compiling do?
Read 1 and 2.

[Pragma]

1) What does compiling actually mean?
depending on what language you use it compiles it into a language readable by the computer (usually 0s and 1s) and what timmy showed is what i believe to be ASCII which can easily be converted into 0s and 1s, lots of computer calculators can do calculations like that.
2) Why use compiling? what is so good about it?
well, you just have to. Java is compiled down to byte code which is read by the JVM (java virtual machine) installed on most OS (like windows, mac OSX, and linux usually have the JVM) then the JVM turns the byte code into 0s and 1s making java able to run on anything with the jvm

thats a but more then you were proly asking for huh =P

[warsheep]

Sigh, so here I go me too.


1) What does compiling actually mean?

I don't know what it actully means, only what it does, which you can read in the next points.

2) Why use compiling? what is so good about it?

Compiling isn't an object, its more something you do.
The reason its smart to compile on your own, is that you can get a bigger understanding of what you are working on. To see how ascent works, you will need to see the source. And when you have the source, why not compile it, and get the newest version?

3) What does compiling do?

There are many programming languages. We have c#, c++, java, j, and so on. But, as far as I know, the computer only understands 1 and 0. Thats right.

1010101111011010011110101010101111

thats a random number, but, that is a example on how everything looks. Confusing? Yes, thats why we don't program in it. Instead, we program in easier languages, and let the compiling process make it all easier.


This information most likely contain errors;
read about it at wikipedia or somewhere else to be sure you get the correct information.

[Steph]

I have some questions about compiling.

1) What does compiling actually mean?
2) Why use compiling? what is so good about it?
3) What does compiling do?

srry for those noob questions, but im about to start to follow some simple compile guides to learn it. but i dont get a clue what it is.

Here's an analogy for you. We'll compare it to making a sandwich, it might make it easier to understand.

1) What does compiling actually mean?

It means taking all your ingredients and putting them together to make a sandwich that you can eat.

When you download ascent from the SVN, or take any 'uncompiled' software, it's like having the bread, butter, meat, sauce for your sandwich in front of you. Now, just because you have all the ingredients infront of you, doesnt make those ingredients a sandwich automatically. You have to make, or compile, your sandwich so that it becomes what you wanted to eat.

2) Why use compiling, what's so good about it.

Well, if you wanted a sandwich, you have to make it from all of your ingredients. None of the ingredients by themselves are a sandwich, they only become a sandwich when you add them all together.

3) What does compiling actually do?

To compile software I use Visual C++ 2003, the uncompiled software, when you download it, has a script ending with .vcproj, VC++ 2003 uses this script to build the piece of software, it's basically the instructions to making our Ascent sandwich.

We've all explained in this thread what compiling means to us, hopefully it's made it clearer to you.

Basically it's the act of building a piece of software from its core components to something we can use.

[V!persting]

Sigh, so here I go me too.


Thanks i understand its very hard to help me out.....


To all the rest, Timmy, Steph, Insane and Quickx thank you very much.+Rep

[Gastricpenguin]

No one really hit the head of the nail on this one, so ill give my input.

1) What does compiling actually mean?
Compiling is a function most retail developement programs, such as visual studios 2003, 2005 and 2008 use. Compiling is the the act of taking a source code and building it into a solution. You would probably be more familiar with solutions that end with .exe or .dll. Pure and simple, compiling does this: Source -> DLL / EXE

2) Why use compiling? what is so good about it?
Since compiling is an action you cant really use it. Whats good about compiling your own ascent core, is that you can edit just about anything. Within repacks, cores are always precompiled. You can never be too sure with repacks though. Sometimes people enable rootkits in their source, then compile it into the revision. Most of the time its easily detectable. But compiling your own ascent makes sure you are safe

3) What does compiling do?
As i said in question 1, compiling takes a source code (input) and builds it into a user defined output (DLL or EXE)

Hope I helped and sorry im late

[~SaiLyn~]

No one really hit the head of the nail on this one, so ill give my input.

1) What does compiling actually mean?
Compiling is a function most retail developement programs, such as visual studios 2003, 2005 and 2008 use. Compiling is the the act of taking a source code and building it into a solution. You would probably be more familiar with solutions that end with .exe or .dll. Pure and simple, compiling does this: Source -> DLL / EXE

2) Why use compiling? what is so good about it?
Since compiling is an action you cant really use it. Whats good about compiling your own ascent core, is that you can edit just about anything. Within repacks, cores are always precompiled. You can never be too sure with repacks though. Sometimes people enable rootkits in their source, then compile it into the revision. Most of the time its easily detectable. But compiling your own ascent makes sure you are safe

3) What does compiling do?
As i said in question 1, compiling takes a source code (input) and builds it into a user defined output (DLL or EXE)

Hope I helped and sorry im late

Gastric i know your good in words , but sometimes SHHH you will be confusing more the ppl that just begin on this .. hehe