What is "build" and what is its relationship to the IDE?

Question

In the area of software development has a term that appears very often that is the build. It always comes 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 this).

I’d like to know what it is build and what relationship he has with IDE?

Answer 1

Is a microsoft conference... lie :P I say this because there are many possible contexts, there are two more used which seem to be than are speaking in the question

It has nothing very special, is what the translation says even, is the construction of the application, in the sense of generating the final executable.

By construction understand that you will compile, linkediting and any necessary step for the application to be in a state that can be executed. Usually take dependencies into account and avoid 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 do it, it generates the executable and you can already test what you have just done. There is software Builder which 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 the developer does all the time on his machine. It doesn’t touch version numbering.

• There’s the build "official" 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 (version of the project). In versioning schemes that the number of the build 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 larger process. They are considered builds automated. In the past, "compile" was used, but it was not semantically correct and the term "build".

  It is more common to be done on a dedicated server with the code committed for 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 a day, in extreme cases 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 receives the name of Agreement, there the build is part of the process.

  Some technologies have a very 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 place of develop.

IDE

At first it has nothing to do with IDE. Of course every IDE triggers the execution of build application for you by a click (probably in menu) or shortcut. Eventually some IDE has its own build, but it’s not very common, because it’s usually needed outside of the IDE and doesn’t have to have different mechanisms, the IDE calls what already exists externally (by command line or other integration, it can even be available in library).

Answer 2

What is?

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 may integrate the final product.

Relationship with the 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, very used to build and perform project tasks written in C and C++, but that to Java, for example, it has many disadvantages and is not used. The best known tools of Java have IDES support, and are easily run on any operating system.

Answer 3

Building is the process of transforming your source text files into one or more files called targets which are used when the application runs. Projects have a single target: an executable file (.exe), produced by the compiler the source files in intermediate object (obj) files that are then linked to various library files (.lib) and native Windows Dlls executable.

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 per the need of Visual Studio to create the target . exe Windows native file. You can think of it as Visual Studio at compile time running a "make" implicit file determined by its project type, its source files and other items, and its dependencies on other projects and libraries.

The configuration menu.

Build compile and connect only the source files that have changed since the last compilation, while Rebuild compile and connect all source files, regardless of whether they have 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 need to clean.

Build or Rebuild build or rebuild 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 project, building or rebuilding Solution is effectively the same as building or rebuilding.

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 hot key to compile.