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 HPUX

sem_post

sem_post(2)							System Calls Manual						       sem_post(2)

NAME

       sem_post  - unlock a POSIX semaphore

SYNOPSIS

DESCRIPTION

       is  used  to post the semaphore referenced by sem.  The calling thread will not return from its call to unless it can either: increment the
       semaphore value, if there are no blocked threads on this semaphore; give the semaphore to a  blocked  thread,  if  there  are  any  blocked
       threads on this semaphore; or have an error condition.

       If the semaphore value is < 0, the semaphore has blocked threads, waiting for it to become available (the absolute value of the semaphore's
       value indicates the number of waiters at that moment).  If the semaphore value is >= 0, the semaphore has no waiters.

       If the semaphore has no waiters at the time its value is checked, the semaphore's value will be atomically incremented, with respect to the
       checking of its value, up to its maximum value as specified by If the semaphore has waiters at the time its value is checked, the semaphore
       value is not changed.  Instead, the calling thread will attempt to wake up a waiter.  If the semaphore has waiters having realtime  priori-
       ties, the thread must wake up the highest priority waiter.  Otherwise the thread at the head of the channel queue is woken up.

       When  a waiter is successfully woken, the semaphore being posted will be given to the woken waiter.  In other words, the state of the sema-
       phore remains unchanged.  Instead, the semaphore being posted will be inherited by the waiter being woken from this call to

       If the specified semaphore referred to by sem is a named semaphore, then this semaphore must have been opened by the calling  process  with
       The  calling process must have both read and write permissions on the semaphore to perform this operation.  The routine may be called asyn-
       chronously, i.e. from a signal handler.

       To use this function, link in the realtime library by specifying on the compiler or linker command line.

EXAMPLES

       The following call to will post the semaphore sem.

RETURN VALUE

       A successful call to will return 0 and the calling thread would have posted the semaphore.  Otherwise, the call	to  will  return  -1  with
       errno set to the appropriate value of the error condition.

ERRORS

       fails and does not perform the requested operation if any of the following conditions are encountered:

	      [EPERM]	     The calling process does not have the privileges necessary to post the semaphore.

	      [EINVAL]	     The argument sem does not refer to a valid semaphore.

SEE ALSO

       <semaphore.h>.

STANDARDS CONFORMANCE

																       sem_post(2)

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 HPUX

sem_post