01-22-2013
I agree in principle. When writing new makefiles, one should write it as one system so it can run efficiently.
When you have to use someone else's makefiles however, you have very little control.
If you're not rewriting them, cramming them all together in one folder is hardly better than keeping them separate. When they were in folders, they were at least organized. Now it's one awful pile.
What option are you trying to pass, to what? If you're not calling make again, there's not a lot to pass options to.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I have concatenated 2 makefiles, to produce 1 however it is not running all of the code, producing a fatal error: symbol referencing errors. No output written. Can anybody please help? (4 Replies)
Discussion started by: Dan Rooney
4 Replies
2. UNIX for Dummies Questions & Answers
I need to develop a makefile that spans across directories. For example, let's say i have an upper level directory (main) and about 2 subdirectories. I want my .cpp files and .o files to be in one subdirectory. I want my .a files to be in the other subdirectory. The .a files are made up of the... (0 Replies)
Discussion started by: benjie_asu
0 Replies
3. Shell Programming and Scripting
for example in my make file im building path from env variables and string but need to see what is did
what is the best way to print the result?
say I have in my Makefile :
exec_prefix = $(RUN_ENV_LOCAL)/apache
and I will like to print the exec_prefix value , how can it be done ? (1 Reply)
Discussion started by: umen
1 Replies
4. UNIX for Advanced & Expert Users
Solved........ (0 Replies)
Discussion started by: klam
0 Replies
5. UNIX for Dummies Questions & Answers
Are the programs written on schedulers ,thread library , process management, memory management, et al called systems programs ? How are they different from the programs that implement functions like open() , printf() , scanf() , read() .. they have a prefix sys_open, sys_close, sys_read etc , right... (1 Reply)
Discussion started by: vishwamitra
1 Replies
6. Programming
I have several programs in several directories and want to use make to build the executables. What I have done is to put the main programs in their own directory together with a makefile to build the program. Then I am thinking of having another makefile residing in the directory above so I can run... (1 Reply)
Discussion started by: kristinu
1 Replies
7. Programming
I have the following part of a makefile and want to simplify it
using rules rather than having to code the same two blocks
when I need ti build another program.
An having difficulty doing it
all: 1dvel2 1dvel 2dvel
... (8 Replies)
Discussion started by: kristinu
8 Replies
8. Programming
I am trying to practice to create Makefiles. The goal is to create a makefile such that if a change is made to any of the source code files, the project can be rebuilt by typing make at the command line.
I have the following files:
ac.cc: has include ac.h and pg.h
fr.cc: has main... (8 Replies)
Discussion started by: pintu1228
8 Replies
9. UNIX for Dummies Questions & Answers
Hey guys,
Suppose i run passwd via bash shell. It is a suid program, which temporarily runs as root(owner) and modifies the user entries.
However, when i write a C file and give 4755 permission and root ownership to the 'a.out' file , it doesn't run as root in bash shell. I verified this by... (2 Replies)
Discussion started by: syncmaster
2 Replies
10. UNIX for Beginners Questions & Answers
Hi All,
I was going through some makefiles where I saw occurrences of explib_subdirs and expinc_subdirs, which I could not understand.
Exporting libs to subdirs ? Exporting include files to specified subdirs ? When do we need to do that ?
What I could understand is, for a build, I would... (4 Replies)
Discussion started by: alltaken
4 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)