Skip to main content

Make file and including external file

Now in this section, we will create a folder to contain some extra files.
1- How to compile those files.
2- We will create a separate folder to contain the obj files.
3- We will create a separate folder to the output executable as well.

Will create a folder called "api" inside the source folder:
this folder will contain:

mmath.h

#ifndef _MMATH_H_
#define _MMATH_H_

double Add(int a, int b);

#endif


mmath.c
#include "mmath.h"

double Add(int a, int b)
{
    return a+b;
}

Let's update out main as well...

main.c
#include <stdio.h>
#include "api/mmath.h"

int main(int argc,char *argv[])
{
    double res = Add(23,26);
    printf("You see, u see this... I'm running\r\n");
    printf("%f\r\n", res);
    printf("Externals Executed\r\n");
    return 0;
}
Now How to compile this?

We need to include our custom header file as well while compiling and we also need to out put the results to bin folder....

So, we include a directory where source code is, using -I<DirectoryName>

So, here we go...


$ gcc -c -Iapi  ./api/mmath.c -o ./obj/mmath.obj

for now this is good...

Let's compile main.


$ gcc -c -Iapi main.c -o./obj/main.obj

Let's link objs and form .exe now ...

$ gcc ./obj/main.obj ./obj/mmath.obj -o ./bin/mobi.exe


 So, crossponding make file look like this:

mobi.mk

CC=gcc
OUT=mobi.exe
TARGET=main
OBJ=./obj
BIN=./bin
INCLUDE=./api
IPATH=-I$(INCLUDE)


all: clean compile build

build:
    $(CC)  $(OBJ)/$(TARGET).obj $(OBJ)/mmath.obj  -o $(BIN)/$(OUT)

compile:
    $(CC) -c $(IPATH)  $(INCLUDE)/mmath.c -o $(OBJ)/mmath.obj
    $(CC) -c $(IPATH)  $(TARGET).c -o $(OBJ)/$(TARGET).obj

clean:
    rm -f $(BIN)/* $(OBJ)/*

Looks a bit scary by now :(


Let's try it now ...


$ make -f ./mobi.mk
rm -f ./bin/* ./obj/*
gcc -c -I./api  ./api/mmath.c -o ./obj/mmath.obj
gcc -c -I./api  main.c -o ./obj/main.obj
gcc ./obj/main.obj ./obj/mmath.obj -o ./bin/mobi.exe

 Let's execute it...

$ ./bin/mobi.exe
You see, u see this... I'm running
49.000000
Externals Executed


 yupiii... let's do more make file ...

Comments

Popular posts from this blog

Culture Information and Localization in .NET

Namespace: System.Globalization CultureInfo Class:                 It provides information like the Format of numbers and dates, Culture’s Calendar, Culture’s language and sublanguage (if applicable), Country and region of the culture. The Basic use of CultureInfo class is shown here: • How string Comparisons are performed • How Number Comparison & Formats are performed • Date Comparison and Formats. • How resources are retrieved and used. Cultures are grouped into three categories: Invariant Culture : It’s Culture Insensitive. It can be used to build some trial application. It can be also used to build an application with hard-coded expiry date that ignores cultures. But using it for every comparison will be incorrect and inappropriate. Neutral Culture : English(en), Frensh(fr), and Spanish(sp). A neutral culture is related to language but it’s not related to specific regi...

Exposing .NET Components to COM

Namespace: System.Runtime.CompilerServices Building .NET Components for use by COM .Net framework generates COM Proxies known as COM Callable Wrapper (CCW) to be used by COM. No matter how many COM clients consume a given managed object, .Net runtime will create a single CCW. Write down you class and before building it, Select the configuration form the project properties named “ Register for COM interop ”. Hiding public .NET Classes from COM To hide a class or member just use the following attribute: [ComVisible(true/false)] . Deploying COM-Enabled Assemblies :       Check the following necessaries before creating CCW: 1.        All class have default constructor (no parameter). 2.        Exposed Types should be public . 3.        Any member exposed should be public . 4.        Abstract classes will not b...

Using ADO.NET Transaction Object, Saving CLR Objects and SqlNotificationRequest

Serializable allows one transaction to complete before the other start. SqlConnectoin support named savpoint to roll back to; that’s an equaliant to save transaction command in MS SQL Server. Using TransactionScope Object : A transaction can’t span multiple connections.   Local and distributed transaction ares supported in 1.x you have to Enterpeise seveices library to regiser multiple connections and then call EnlistDistributedTransaction. Distributed Transaction Coordinator is required for Distributed transaction that’s available on windows 2000 & +. In 2.X and later use TransactionScope object. Serializable allows one transaction to complete before the other start. SqlConnectoin support named savpoint to roll back to; that’s an equaliant to save transaction command in MS SQL Server. Using TransactionScope Object : Dispoase of the transaction must be called to complete the transaction. Distributed Transaction : ...