The linker
A linker is another program which is invoked upon compiled object files. A linker just identifies thestructure of the object files, resolves the functions and object linkages and creates an executable

To understand linkers, it helps to first understand what happens “under the hood” when you convert a source file (such as a C or C++ file) into an executable file (a file that can be executed on your machine or someone else’s machine running the same architecture).

Under the hood, when a program is compiled, the compiler converts the source file into object byte code. This byte code (sometimes called object code) is mnemonic instructions that only your computer architecture understands. Traditionally, these files have an .OBJ extension.

After the object file is created, the linker comes into play. More often then not, a real program that does anything useful will need to reference other files. In C, for example, a simple program to print your name to the screen would consist of:
printf(“Hello Nick!\n”);

When the compiler compiled your program into an obj file, it simply put a reference to the printf function. The linker resolves this reference. Most programming languages have a standard library of routines to cover the basic stuff expected from that language. The linker links your OBJ file with this standard library. The linker can also link your OBJ file with other OBJ files. You can create other OBJ files that have functions that can be called by another OBJ file. The linker works, almost like a word processor’s copy and paste. It “copies” out all the necessary functions your program references and creates a single executable. Sometimes other libraries that are copied out are dependent on yet other OBJ or library files. Sometimes a linker has to get pretty recursive to do its job.

Note that not all operating systems create a single executable. Windows, for example, uses DLL’s that keep all these functions together in a single file. This reduces the size of your executable, but makes your executable dependant on these specific DLLs. DOS used to use things called Overlays (.OVL files). This had many purposes, but one was to keep commonly used functions together in 1 file (another purpose it served, in case you’re wondering, was to be able to fit large programs into memory. DOS has a limitation in memory and overlays could be “unloaded” from memory and other overlays could be “loaded” on top of that memory, hence the name, “overlays”). Linux has shared libraries, which is basically the same idea as DLL’s (hard core linux guys I know would tell me there are MANY BIG differences).

The procedure for compiling a C++ program is the same as for a C program, but uses the command g++ instead of gcc. Both compilers are part of the GNU Compiler Collection.

Sample C++ Program 1
======================

#include <iostream>
int main()
{
using namespace std;
cout << “Hello world!” << endl;
return 0;
}

The program can be compiled with the following command line:
g++ -Wall hello.cc -o hello

The resulting executable can be run in exactly same way as the C version, simply by typing its filename:
$ ./hello Hello, world!

Sample C++ Program 2
======================

#include <iostream>
#include <cmath>

using namespace std;

int main()
{
int x = 0;
while(x < 10) {
double y = sqrt((double)x);
cout << “The square root of ” << x << ” is ” << y << endl;
x++;
}
return 0;
}

Building on the Command Line

CL
Use the compiler (cl.exe) to compile and link source code files.

The compilers produce Common Object File Format (COFF) object (.obj) files. The linker produces executable (.exe) files or dynamic-link libraries (DLLs).

Link
Use the linker (link.exe) to link compiled object files.

MSBuild (Visual C++)
Use MSBuild to build Visual C++ projects and Visual Studio solutions from the command line. Invoking this utility is equivalent to running the Build project or Build Solution command in the Visual Studio integrated development environment.

The build process is controlled by the information in a project file (.vcxproj) that you can create and edit. The project file specifies build options based on build stages, conditions, and events.

DEVENV
Use DEVENV combined with a command line switch, such as /Build or /Clean, to perform certain build commands without displaying the Visual Studio IDE.

Devenv lets you set various options for the integrated development environment (IDE), and also build, debug, and deploy projects, from the command line. Use these switches to run the IDE from a script or a .bat file, for example, a nightly build script, or to start the IDE in a particular configuration.
For example, the command devenv /build myproject1.vbproj

NMake
Use NMake to automate tasks that build Visual C++ projects. The Microsoft Program Maintenance Utility (NMAKE.EXE) is a tool that builds projects based on commands contained in a description file.

Reference
http://msdn.microsoft.com/en-us/library/f35ctcxw.aspx

Header file vs Library

Generally, a header file notifies the compiler of certain things (mostly their existence or declarations) so that the compiler can correctly build a single translation unit (such as a single C file).

A library file is the actual executable code that does the work as specified in that header file. This is linked in by the linker to provide the actual functionality (the _definitions rather than just the declarations).

Header Files: These are the files that are included at the top of any program. If we use any function inside a program, then the header file containing declaration or definition of that function ,has to be included.Like printf() is defined in stdio.h.So, we must include it (by #include in order to use printf().

Library Files: These are the files which the compiler uses in order to define the functions which have been used in the program and had been declared inside the header file.Like, printf() has its complete definition ,like how it will work etc. in an I/O library! So, the compiler uses that library to get the machine code for printf.

Difference:
Header files are TEXT files while library files are BINARY. This means, we can read and modify the header file but not the library!
Header file is in C language while the library is in machine language!
Header file has to be included by the programmer while the compiler automatically relates the library file(s) with the program!

The post C++ basic for Build and Release Engineers appeared first on scmGalaxy.

Make for Windows: NMake

What is Nmake?
NMAKE is Microsoft’s implementation of the make tool. The Microsoft Program Maintenance Utility (NMAKE.EXE) is a 32-bit tool that builds projects based on commands contained in a description file.

Another definition found on web as well
nmake is the “make” program for Visual Studio. A “make” program builds (makes) an executable and/or package by reading a set of “make” files. These files are essentially scripts that specify what is to be made, what files (header, source code, resource) are needed for each output file, etc. So nmake can be used to completely automate the process.

A frequently asked question: “Where can I find make for Windows?“. The answer is: “Download and use NMake“.

Downloading NMake
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q132084

Direct Downloan Link of Nmake
http://download.microsoft.com/download/vc15/patch/1.52/w95/en-us/nmake15.exe

Installing NMake

Run the downloaded executable to extract the files. Copy both the NMAKE.EXE and the NMAKE.ERR file to your Perl bin directory, normally C:\Perl\bin. Make sure that you copy the NMAKE.ERR file as well.

1. Download nmake15.exe

2. Double click on nmake15.exe. It will generate 3 files: nmake.exe, nmake.err and readme.txt.

3. Copy nmake.exe and nmake.err to \perl\bin, which is where ActivePerl executable files are located.

4. Now try the nmake command in a command window. If you see the following message, NMake 1.5 is installed correctly:

>nmake

Microsoft (R) Program Maintenance Utility   Version 1.50    Copyright (c) Microsoft Corp 1988-94. All rights reserved.

NMAKE : fatal error U1064: MAKEFILE not found and no target specified    Stop.

Example of an NMake session

Normally building Perl modules and installing them consist of the following steps:

perl Makefile.pl
make
make test
make install

Reference:
http://msdn.microsoft.com/en-us/library/dd9y37ha%28v=vs.71%29.aspx

The post Make for Windows: NMake | What is Nmake? appeared first on scmGalaxy.