Hello
I have compilation directory structure the top level Makefile is the one that contains all the sub directories
I want to set in this Makefile env variable say : setenv OPTIMIZATION_LEVEL "1"
and when all the sub directories done compiling it will set this variable to different lavel... (0 Replies)
Hi.
I what to write a make file that inside a target I want to check if a directory exists.
some like:
### make
a:
if ;then
<command 1>
else
<command 2>
fi
### make end
Thanks a lot
---------------------- (2 Replies)
Hi,
I want to append some compiler flags to CFLAGS_LOCAl variable defined in one makefile.
I am trying to append required flags in another makefile like this:
CFALGS_LOCAL = $(CFLAGS_LOCAL) +check=all
but when I make, I get the error:
../../../../rules/target.rules:4: *** Recursive... (2 Replies)
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)
Greetings!
Basically, I would like to properly handle this with gnu make:
alltools: my_tool mysecond_tool mythird_tool etc_tool
%_tool: dir1/%_tool.vf dir2/%_tool/subdir2/%_tool.ver
<tab>@echo done
%.vf:
<tab>RUN_VF $*
%.ver:
<tab>RUN_VER $*
So, if I were to do something like:... (0 Replies)
Hi,
I have a small piece of Makefile script which throw's error on Sun Sparc machine, but works fine with Sun Optron, Linux, AIX machines.
FOO=Naveen
test1:FOO=Dhilip
test1:
@echo FOO is ${FOO}
test2:
@echo Me is ${FOO}
Output on Sun Sparc -
ukhml-v890new-~/test: make test1... (5 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 guys,
I could use advise from more experienced guys about my Makefile. In short, the problem with my Makefile is that $< doesnt change
inside my rule.
Here is my Makefile:
# Makefile for CORE
CC = gcc.exe
AS = as.exe
AR = ar.exe
INCLUDE = \
-I../lib/tomcrypt/inc \... (1 Reply)
Hi,
in makefile, if the sourc and dest in different directory, no matter the source file changed or not, it seems the dest always been build, how do you resolve this?
Thanks.
peter (1 Reply)
I make to parse the release version from a text file and set the release version label into a Makefile variable. I tried:
VERSION := `grep vsn s1db.app|sed -e s/*\"// -e s/\"*//`
but looks like make, unlike shell, literally just take the entire `grep ...` as the variable value.
Then I tried... (3 Replies)
Discussion started by: benkial
3 Replies
LEARN ABOUT DEBIAN
dh_auto_install
DH_AUTO_INSTALL(1) Debhelper DH_AUTO_INSTALL(1)NAME
dh_auto_install - automatically runs make install or similar
SYNOPSIS
dh_auto_install [buildsystemoptions] [debhelperoptions] [--params]
DESCRIPTION
dh_auto_install is a debhelper program that tries to automatically install built files. It does so by running the appropriate command for
the build system it detects the package uses. For example, if there's a Makefile and it contains a install target, then this is done by
running make (or MAKE, if the environment variable is set). If there is a setup.py or Build.PL, it is used. Note that the Ant build system
does not support installation, so dh_auto_install will not install files built using Ant.
Unless --destdir option is specified, the files are installed into debian/package/ if there is only one binary package. In the multiple
binary package case, the files are instead installed into debian/tmp/, and should be moved from there to the appropriate package build
directory using dh_install(1).
DESTDIR is used to tell make where to install the files. If the Makefile was generated by MakeMaker from a Makefile.PL, it will
automatically set PREFIX=/usr too, since such Makefiles need that.
This is intended to work for about 90% of packages. If it doesn't work, or tries to use the wrong install target, you're encouraged to skip
using dh_auto_install at all, and just run make install manually.
OPTIONS
See "BUILD SYSTEM OPTIONS" in debhelper(7) for a list of common build system selection and control options.
--destdir=directory
Install files into the specified directory. If this option is not specified, destination directory is determined automatically as
described in the "DESCRIPTION" section.
-- params
Pass params to the program that is run, after the parameters that dh_auto_install usually passes.
SEE ALSO debhelper(7)
This program is a part of debhelper.
AUTHOR
Joey Hess <joeyh@debian.org>
9.20120909 2011-10-19 DH_AUTO_INSTALL(1)