08-27-2002
There are several things to note, keep in mind that the make utility and makefiles are extremely versatile and can become extremely complicated.
I'll start at the beginning with some basics, if need be I can go into more detail later.
make does not need a makefile! If you have a file called prog.c you can type
10 More Discussions You Might Find Interesting
1. Programming
Hi, I am very new with makefile topics , maybe this is a very symple question...
I have this code wich compile very good ( I get it from the net), I will call it code A.
I have to add it with a program that is all ready in use, (code B) that also compile good. When I put together it doesnt... (7 Replies)
Discussion started by: pmoren
7 Replies
2. Programming
My make file is
CFLAGS = -Wall -g
LDFLAGS = -lm
CC = g++
all: server client
rc4.o: rc4.cpp rc4.h
${CC} ${CFLAGS} -c rc4.cpp
server.o: server.cpp rc4.h
${CC} ${CFLAGS} -c .cpp
client.o: client.cpp rc4.h
${CC} ${CFLAGS} -c client.cpp
server: server.o... (2 Replies)
Discussion started by: neerajgoyal12
2 Replies
3. Programming
Hi all,
I have 4 '.cpp' files and 1 header files:
Tools.cpp
Code1.cpp
Code2.cpp
Code3.cpp
and Tools.hh
Now all Code1.cpp, Code2.cpp, Code3.cpp
use functions stored in Tools.cpp.
Currently, what I do to compile all of them is using
this simple shell script: (1 Reply)
Discussion started by: monkfan
1 Replies
4. UNIX for Advanced & Expert Users
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)
Discussion started by: hernandinho
2 Replies
5. Programming
I need to create an executable with these two makefiles(they both have libaries i
need(qt and ruby))
i have extconf.rb
gui.ui
gui_include.h
main.cpp
ScaleIM_client.rb
ui_gui.h
i want to combine them all into one executable
please!... (2 Replies)
Discussion started by: gjgfuj
2 Replies
6. Programming
Hi,
Here is my makefile http://pastie.org/1104332. I am trying to compile different .c files and .s files (assembly files) from different sub directories into E:/em35x/build/mfg-sample-app-cortexm3-iar-em357-em3xx-dev0680/ then the linker should link all the .o files from the build directory... (1 Reply)
Discussion started by: blade2008
1 Replies
7. Programming
Im trying to build a makefile for the first time in many years and Im coming to a screaching halt on something that should be child's play; just compiling two files. Here is an excerpt of the make file.
(using GMAKE on a TI compiler)
CCHP = <<compiler>>
PROJ_DIR = .
APP_DIR ... (2 Replies)
Discussion started by: DrNismo
2 Replies
8. Emergency UNIX and Linux Support
I had created a Makefile for my project. my project file hierarchy is like this:
1. a source folder with main.c and Makefile in it
2. and a top level Makefile
here is the Makefile in src folder
all: program
program: main.c
gcc -o program main.c
clean:
rm programand here is top... (3 Replies)
Discussion started by: majid.merkava
3 Replies
9. Programming
hello, I'm trying to create a makefile to run multiple c files. I am able to run one c file only with the code I have when I tried to run 2 or more c files I'm not able. here is my code
# $Source: /home/hectormasencio/make/Makefile,v $
# $Date: 2012/11/27 11:35:30 $
CC= gcc
OBJS= temp.o... (3 Replies)
Discussion started by: Hector M.
3 Replies
10. Programming
I have written this makefile and am getting an error saying
make nfd
gfortran -O -Wall -fbacktrace -fno-align-commons -c -o fd.o fd.f
fd.f:49: Error: Can't open included file 'fd.par'
make: *** Error 1
The directory structure is as follows
.
├── library
│ ├── fd
│ │ ├──... (3 Replies)
Discussion started by: kristinu
3 Replies
KMK(1) simple makefiles for complex tasks KMK(1)
NAME
kmk - framework for writing simple makefiles for complex tasks
SYNOPSIS
kmk [OPTIONS]
DESCRIPTION
kmk and its helper tools are an extension to GNU make to ease writing portable Makefile.
The goals of the kBuild framework:
- Similar behavior cross all supported platforms.
- Flexibility, don't create unnecessary restrictions preventing ad-hoc solutions.
- Makefile can very simple to write and maintain.
There are four concepts being tried out in the current kBuild incaration:
- One configuration file for a subtree automatically included.
- Target configuration templates as the primary mechanism for makefile simplification.
- Tools and SDKs for helping out the templates with flexibility.
- Non-recursive makefile method by using sub-makefiles.
kBuild does not provide any facilities for checking compiler/library/header configurations, that's not in its scope. If this is important
for your project, check out the autoconf tool in the GNU build system. It is possible to use kBuild together with autoconf if you like, but
you might just as well use the full GNU package.
On Debian systems, the kBuild binaries can be found in /usr/bin and its data files in /usr/share/kBuild.
SEE ALSO
make(1)
HOMEPAGE
More information about kBuild project can be found at <http://svn.netlabs.org/kbuild/>.
AUTHOR
kBuild was written by Knut St. Osmundsen <bird-kBuild-spam@anduin.net>.
This manual page was written by Daniel Baumann <daniel@debian.org>, for the Debian project (but may be used by others).
0.1.98svn2318 2009-04-09 KMK(1)