What is "build" and what is its relationship with the IDE?
In the area of software development has a term that appears very often that is build. It always came to me when I read about Android Studio and other development tools (usually IDEs), I think it should be part of this concept (I may be wrong about it).
I would like to know what is Build and what is the relationship it has with the IDE?
3 answers
Is a Microsoft conference ... lie: P I say this because there are many possible contexts, there are two more used that seem to be than you are talking about in question
It has nothing very special, it is what the translation says even, it is the construction of the application, in the sense of generating the final executable.
By construction understand that it will compile, linkedition and any steps necessary for the application to be in a state that can be run. It usually takes into account dependencies and avoids redoing what can be repurposed.
-
A build occurs every time you need to run a new version of the code (not to be confused with Project version). You have it done, it generates the executable and you can already test what you just did. There is a builder software 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. Does not interfere with version numbering.
-
There is the "Official" build which is generated from time to time and which can be made available to some people. One of them 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.
Does not usually occur in interpreted languages.
O testing process, deeper analyses and even packaging can be done together. This is a larger process. Automated builds are considered. In the past we used to use "compile", but it was not semantically correct and we went on to use the term"build".
It is more common to be done on a dedicated server with Code committed by everyone and generates something to be consumed by Test teams and even be released as something official. It is common to have one or two per day, in extreme cases can have several. Of course, it depends on the size of the team, the necessary organization. Some cases this is taken to the extreme and is named after continuous integration, then the build is part of the process.
Some technologies have their own process and specific steps.
The term can be used in other contexts quite differently, some very specific or even something general like saying build in instead of develop .
IDE
At First has nothing to do with IDE. Of course every IDE triggers the execution of the build of the application for you by a click (probably in menu) or shortcut. Eventually some IDE has its own engine of build , but it is not very common, because it is usually necessary outside the IDE and does not have to have different mechanisms, the IDE calls what already exists externally (by command line or other integration, can even be available in 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 will be able to integrate the final product.
relationship with IDEs
The relationship is that some IDEs have a build engine. Speaking of some languages, there are thousands of build tools, the best known being make, very used to build and execute tasks of projects written in C and C++, but which for Java, for example, has many disadvantages and is not used. The most well-known Java tools have IDEs support, and are easily run on any operating system.
Building is the process of turning your source code text files into one or more files called targets that are used when the application runs. Projects have a single target: an executable file (.exe), produced by the compiler the source files into intermediate object (obj) files that are then linked to multiple library files (.lib) and native executable Windows DLLs.
Building the executable with Visual Studio is unlike UNIX in that you never explicitly run a compiler, linker, or other tools. Instead they run as needed by Visual Studio to create the file .native Windows target exe. You can think of it as Visual Studio at compile time by running an implicit "make" file determined by your project type, your source files and other items, and your dependencies on other projects and libraries.
The menu of setting.
Build compile and link only the source files that have changed since the last build, while Rebuild compile and link all the source files, regardless of whether they have been changed or not. Build is the normal thing to do and it's faster. Sometimes versions of the project's target components can get out of sync and a Rebuild is required to make the build successful. In practice, you never you need to clean up.
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 typically have only one project, build or rebuild Solution is effectively the same as build or rebuild.
Compile only compiles the current source file to be edited. Useful to quickly check 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 hotkey to compile.