C++ application development Post: 302701525

Sponsored Content

Top Forums Programming C++ application development Post 302701525 by Corona688 on Sunday 16th of September 2012 01:30:49 PM

09-16-2012

Registered User

The larger the project, the more work must be done when you end up ripping out all the IDE garbage to re-import into a newer or different IDE.

It doesn't help as much as you think, either, if you learn what you're doing first, which I think you should do at the very least! If you've never compiled anything yourself, never used a makefile, most of the options in an IDE will never make sense. It's not like makefiles are hard. Put all these files in the same folder and run make:

Code:

// libraryfunction.c

double square(double value)
{
        return(value*value);
}

Code:

// libraryfunction.h

#ifndef __LIBRARYFUNCTION_H__
#define __LIBRARYFUNCTION_H__

extern double square(double);

#endif/*__LIBRARYFUNCTION_H__*/

Code:

//main.c
#include "libraryfunction.h"
#include <math.h>
#include <stdio.h>

int main(void)
{
        printf("%f\n", square(sin(0.5)));
        return(0);
}

Code:

# Makefile

# Built-in variable for linker, defines libraries.
LDFLAGS=-lm
# Built in variable for CC, defines compile flags
# For C++ the simlar variable CXXFLAGS is used.
CFLAGS=-ggdb

# Note the eight spaces in front is actually a tab and MUST BE a tab
myapp:main.o library.o
        $(CC) $(LDFLAGS) $^ -o $@

...and that's a complete makefile. It knows how to convert .c and .cpp files into .o files by itself, so you just make a rule which builds your application out of .o files.

Whenever your .c files are newer than your .o files it rebuilds the .o files. Whenever your .o files are newer than myapp, it rebuilds myapp.

$@ is a special variable for 'output file'. It becomes myapp.
$^ is a special variable for 'input files'. It becomes main.o library.o.

Last edited by Corona688; 09-16-2012 at 02:38 PM..

This User Gave Thanks to Corona688 For This Post:

Corona688

View Public Profile for Corona688

Visit Corona688's homepage!

Find all posts by Corona688

We Also Found This Discussion For You

1. Shell Programming and Scripting

Difference between development and Production unix servers for a application??

Hi all I am running a major script of my application in development for implementing code changes for process improvement in time. The script runs in production once in a month . It takes 8 hours 30 mins in Production server . what surprice me is , when I run the same script in development server...

LEARN ABOUT OPENSOLARIS

neon-config

NEON-CONFIG(1)							       neon							    NEON-CONFIG(1)

NAME

       neon-config - script providing information about installed copy of neon library

SYNOPSIS

       neon-config [--prefix] [--cflags | --libs | --la-file | --support feature | --help | --version]

DESCRIPTION

       The  neon-config  script  provides information about an installed copy of the neon library. The --cflags and --libs options instruct how to
       compile and link an application against the library; the --version and --support options can help determine whether the library	meets  the
       applications requirements.

OPTIONS

       --cflags
	      Print the flags which should be passed to the C compiler when compiling object files, when the object files use neon header files.

       --libs Print the flags which should be passed to the linker when linking an application which uses the neon library

       --la-file
	      Print the location of the libtool library script, libneon.la, which can be used to link against neon by applications using libtool.

       --version
	      Print the version of the library

       --prefix dir
	      If dir is given; relocate output of --cflags and --libs as if neon was installed in given prefix directory. Otherwise, print the in-
	      stallation prefix of the library.

       --support feature
	      The script exits with success if feature is supported by the library.

       --help Print help message; includes list of known features and whether they are supported or not.

EXAMPLE

       Below is a Makefile fragment which could be used to build an application against an installed neon library, when the neon-config script can
       be found in $PATH.

       CFLAGS = `neon-config --cflags`
       LIBS = `neon-config --libs`
       OBJECTS = myapp.o
       TARGET = myapp

       $(TARGET): $(OBJECTS)
	    $(CC) $(LDFLAGS) -o $(TARGET) $(OBJECTS) $(LIBS)

       myapp.o: myapp.c
	    $(CC) $(CFLAGS) -c myapp.c -o myapp.o

AUTHOR

       Joe Orton <neon@webdav.org>.

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

       +--------------------+-----------------+
       |  ATTRIBUTE TYPE    | ATTRIBUTE VALUE |
       +--------------------+-----------------+
       |Availability	    | SUNWneon	      |
       +--------------------+-----------------+
       |Interface Stability | Volatile	      |
       +--------------------+-----------------+
NOTES

       Source for Neon is available on http://opensolaris.org.

neon 0.25.5							  20 January 2006						    NEON-CONFIG(1)

We Also Found This Discussion For You

1. Shell Programming and Scripting

Difference between development and Production unix servers for a application??

Discussion started by: sakthifire

LEARN ABOUT OPENSOLARIS

neon-config