08-09-2012
Argh, I meant a compiling macro! *facepalm* Can I do it with a compiling macro?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
This stems from the following thread https://www.unix.com/showthread.php?t=18299
I have a makefile which makes either executables or a shared library.
i.e. make -f unix.mak will create the executables and
make -f unix.mak libolsv will create the shared library.
Since these have to be... (4 Replies)
Discussion started by: vino
4 Replies
2. UNIX for Dummies Questions & Answers
I'm trying to define a variable named sin
I already have a variable named cos, which has the value "hello"
I want sin to have the value of "hellothere",
so sin would be something like
sin = $cos & "there"
but I'm not sure that I know the syntax.
Can anyone help?
:confused: (4 Replies)
Discussion started by: sailorliones
4 Replies
3. Shell Programming and Scripting
Hey all, I was wondering if someone would take a look at this script I'm working on. I don't know if i have the syntax correct for my variables and if the for loop is written correctly.
any assistance would be greatly appreciated.
#!/usr/bin/bash
###########################################... (12 Replies)
Discussion started by: em23
12 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
Is it possible to send a custom signal to a process?
e.g. Send signal 9999 to my process, which handles it with some custom handler.
How would one do this? (12 Replies)
Discussion started by: joha
12 Replies
6. Shell Programming and Scripting
I can't seem to get a rule in my Makefile to ever run... even if I change the rule to force make to re-enter the rule, or if I change the dependent files the rule depends on. Any ideas why the second rule is being ignored here?
#MAKEFILES = $(DIRS:%=$(ROOT)/%/Makefile)
#$(MAKEFILES):... (0 Replies)
Discussion started by: foureightyeast
0 Replies
7. Homework & Coursework Questions
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)
Discussion started by: Tatl
1 Replies
8. UNIX for Dummies Questions & Answers
Hi All,
I have a trivial question but I dont know how to solve it.
So basically I'm working on a USB key and I have a directory with some scripts which I use to work on files present in other directories within the USB or sometimes on the main harddisk too. The problem is every time I have to... (3 Replies)
Discussion started by: pawannoel
3 Replies
9. Programming
I am trying to create a makefile to build a program and am getting the following error:
make -f tsimplex.mk
make: *** No rule to make target `/main/tsimplex_main.cpp', needed by `tsimplex_main.o'. Stop.
OPSYS = $(shell uname -s )
TARGET = tsimplex
ROOTDIR = ../../..
GTSDIR =... (1 Reply)
Discussion started by: kristinu
1 Replies
10. Shell Programming and Scripting
Hi all,
I want to know the entry point (default rule to be executed) in a makefile once all defined variables are evaluated. I do not have all: in my makefile and I give
"make" without any parameter in command line.
thanks........ (3 Replies)
Discussion started by: useless79
3 Replies
MKDEP(1) BSD General Commands Manual MKDEP(1)
NAME
mkdep -- construct Makefile dependency list
SYNOPSIS
mkdep [-aDdopq] [-f file] [-s suffixes] -- [flags] file ...
DESCRIPTION
mkdep takes a set of flags for the C compiler and a list of C source files as arguments and constructs a set of include file dependencies
which are written into the file ``.depend''. An example of its use in a Makefile might be:
CFLAGS= -O -I../include
SRCS= file1.c file2.c
depend:
mkdep -- ${CFLAGS} ${SRCS}
where the macro SRCS is the list of C source files and the macro CFLAGS is the list of flags for the C compiler.
The options are as follows:
-a Append to the output file, so that multiple mkdep's may be run from a single Makefile.
-D Post process (as -d) but read the list of filenames from stdin.
-d Post process and merge previously created (for example by ``cc -MD x.c'') depend files into a single file.
-f Write the include file dependencies to file, instead of the default ``.depend''.
-o Add an additional .OPTIONAL line for each dependent file.
-p Cause mkdep to produce dependencies of the form:
program: program.c
so that subsequent makes will produce program directly from its C module rather than using an intermediate .o module. This is useful
for programs whose source is contained in a single module. -p is equivalent to specifying a null suffix with -s.
-q Do not print a warning for inaccessible files when -d is given.
-s Expand each target filename to a list, replacing the '.o' suffix with each element of suffixes. The list of suffixes may be space or
comma separated.
FILES
.depend File containing list of dependencies.
SEE ALSO
cc(1), cpp(1), make(1)
HISTORY
The mkdep command appeared in 4.3BSD-Tahoe.
BUGS
Some characters special to make(1), most notably the comment character, are not escaped correctly if they appear in file names. This can
lead to unparseable output or silently cause dependencies to be lost.
BSD
October 15, 2010 BSD