Based on the above tutorial I created this Makefile
It works, but it's not using the compiler flags to speedup the code. I realisz that the problem is that the flags are in the wrong place, they should be before the .o files are created. I guess I shall put them in the CFLAGS? I read somewhere that since the CFLAGS are made to be adjusted by the end-user, it's a bad practice to set them in the Makefile. If that is the case, where should I put the compiler flags?
Besides that, I do not comprehend the purpose of "-I". The tutorial says
Quote:
The -I. is included so that gcc will look in the current directory (.) for the include file hellomake.h.
. But doesn't always gcc looks in the current directory for .h files? As far as I know, it's the double "" around a .h file that makes gcc look in the current directory for the file, if it was <>, it would look for them in the global directories like /usr/include.
Hi, I'm trying to run the module load command in a Makefile and i'm getting the following error:
make: module: command not found
Why is this? Is there any way to run this command in a Makefile?
NOTE: command - module load msjava/sunjdk/1.5.0 works fine outside of the Makefile (2 Replies)
I have 2 libraries in 2 different directories that I build with Makefiles.
library B depends on library A. If I modify a .cpp file in library A and run lib B's Makefile can I have B's makefile to automatically rebuild library A?
I am now rebuilding A, followed by B... but I'd like B to... (0 Replies)
Hello guys !
Need a bit of help is compiling a code, the makefile for which was originally designed to work on a 32-bit Linux platform, for a 64-bit Linux platform.
My platform is Ubuntu 10.04 LTS 64-bit. I am trying to compile a code called csim, file name csim-1.1.tar.gz. To compile this... (0 Replies)
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
1. The problem statement, all variables and given/known data:
Basically, the prompt is make a makefile with various sub makefiles in their respective subdirectories. All code... (1 Reply)
Hello,
I am attempting to build gcc 4.0.4 on my Mac (OS X). When I use the "make" command, it returns with something like this:
Makefile:6089: *** missing separator. Stop.
This means that at the given line, I must go into the file and insert a TAB before the contents of that line. I have... (1 Reply)
Hello All,
I have a file, but I want to separate the file at a particular record with comma"," in the line
Input file
APPLE6SSAMSUNGS5PRICEPERPIECEDOLLAR600EACH010020340URX581949695US
to
Output file
APPLE6S,SAMSUNGS5,PRICEPERPIECE,DOLLAR600EACH,010020340URX581949695,US
This is for... (11 Replies)
Hello everybody, I'll get one more help
I have a cabundle file that I need to separate into 2 parts, the first sequence and the second sequence, I thought of several things but I did not remember anything that could actually accomplish this separation and transform into 2 variables, first... (4 Replies)
Discussion started by: c0i0t3
4 Replies
LEARN ABOUT HPUX
uuid-config
UUID-CONFIG(1) Universally Unique Identifier UUID-CONFIG(1)NAME
uuid-config - OSSP uuid API build utility
VERSION
OSSP uuid 1.6.2 (04-Jul-2008)
SYNOPSIS
uuid-config [--help] [--version] [--all] [--prefix] [--exec-prefix] [--bindir] [--libdir] [--includedir] [--mandir] [--datadir] [--acdir]
[--cflags] [--ldflags] [--libs]
DESCRIPTION
The uuid-config program is a little helper utility for easy configuring and building applications based on the uuid(3) library. It can be
used to query the C compiler and linker flags which are required to correctly compile and link the application against the uuid(3) library.
OPTIONS
uuid-config accepts the following options:
--help
Prints the short usage information.
--version
Prints the version number and date of the installed uuid(3) library.
--all
Forces the output of all flags, that is, including extra flags which are not OSSP uuid specific.
--prefix
Prints the installation prefix of architecture independent files
--exec-prefix
Prints the installation prefix of architecture dependent files.
--bindir
Prints the installation directory of binaries.
--libdir
Prints the installation directory of libraries.
--includedir
Prints the installation directory of include headers.
--mandir
Prints the installation directory of manual pages.
--datadir
Prints the installation directory of shared data.
--acdir
Prints the installation directory of autoconf data.
--cflags
Prints the C compiler flags which are needed to compile the uuid(3)-based application. The output is usually added to the CFLAGS
uuidiable of the applications Makefile.
--ldflags
Prints the linker flags (-L) which are needed to link the application with the uuid(3) library. The output is usually added to the
LDFLAGS uuidiable of the applications Makefile.
--libs
Prints the library flags (-l) which are needed to link the application with the C uuid(3) library. The output is usually added to the
LIBS uuidiable of the applications Makefile.
EXAMPLE
CC = cc
CFLAGS = -O `uuid-config --cflags`
LDFLAGS = `uuid-config --ldflags`
LIBS = -lm `uuid-config --libs`
all: foo
foo: foo.o
$(CC) $(LDFLAGS) -o foo foo.o $(LIBS)
foo.o: foo.c
$(CC) $(CFLAGS) -c foo.c
SEE ALSO uuid(3), uuid(1), OSSP::uuid(3).
04-Jul-2008 OSSP uuid 1.6.2 UUID-CONFIG(1)