In the area of software development there is a term that comes up very often which is build . It always popped up when I read about Android Studio and other development tools (usually IDEs), I think it should be part of this concept (I might be wrong about it).
I would like to know what is build and what is the relationship it has with IDE?
It's a Microsoft conference ... lie: P I say this because there are many possible contexts, there are two most used that seem to be of what is speaking in question
It does not have anything special, it's what the translation says, it's the construction of the application.
By construct understand that it will compile link and any step necessary for the application to be in the state that can be executed. Usually takes into account dependencies and avoids redoing what can be reused.
A build occurs every time you need to run a new version of the code (not to be confused with the project version). You have it done, it generates the executable and you can already test what you just did. There is software builder that takes care of doing everything right within certain criteria. It can be configured by an IDE or by hand (plain text, XML, etc.). It's something that the developer does all the time on your machine. Do not mess with version numbering.
There is the build "official" that is generated from time to time and can be made available to some people. One of these will eventually be released to the public ( project version ). In versioning schemes that the build number is used it is incremented whenever a new one is created.
It does not usually occur in interpreted languages.
The testing process, deeper analysis and even packaging can be done together. This is a bigger process. They are considered automated builds . In the past we used to use "compile", but it was not semantically correct and we used the term "build".
It's more common to be done on a dedicated server with the commited code by everyone and generates something to be consumed by test teams and even be released as official. It is common to have one or two a day, in extreme cases you can have several. Of course it depends on the size of the team, the organization needed. Some cases this is taken to the extreme and is called continuous integration , then the build is part of the process.
Some technologies have a process of their own and specific steps.
The term can be used in other contexts quite differently, some very specific or even something general like saying build instead of develop .
At first it has nothing to do with IDE. Of course, every IDE triggers the application's build execution for you by a click (probably a menu) or shortcut. Eventually some IDE has its own build mechanism, but it is not very common, even because it is usually needed outside the IDE and does not have to have different mechanisms, IDE calls what already exists externally command line or other integration, may even be available in the library).
What is it?
Build , in the context of software development, is a "compiled" version of a software or part of it that contains a set of features that can integrate the final product.
Relation to IDEs
The relationship is that some IDEs have a build mechanism. Speaking of some languages, there are thousands of build tools, the best known being make , much used to build and execute project tasks written in C and C++ , but for Java , for example, has many disadvantages and is not used. The best-known Java tools are supported by IDEs, and are easily run on any operating system.
Building is the process of transforming your code- source in one or more files called targets that are used when the application runs. The projects have a single target: an executable (.exe) file, produced by the compiler the source files in the intermediate object (obj) files that are then linked to various library (.lib) files and native Windows executable DLLs .
Building the executable with Visual Studio is different from UNIX in that you never explicitly run a compiler, linker, or other tools. Instead they run as needed by Visual Studio to create the native Windows .exe file. You can think of this as compile-time Visual Studio by running a "make" implicit file determined by your project type, your source files and other items, and their dependencies on other projects and libraries.
The setup menu.
Build or Rebuild builds or rebuilds all projects in your solution To set the startup project, right click on the desired project name in the Solution Explorer tab and select Set as startup project. The project name now appears in bold. Since home solutions usually have only one design, Build or Rebuild Solution is effectively the same as building or rebuilding.
Compile only compiles the current source file to be edited. Useful for quickly checking for errors when the rest of your source files are in an incomplete state that prevents a successful build of the entire project. Ctrl-F7 is the shortcut key to compile.
