01-30-2011
Rather, I'd make one general rule which doesn't match all the files but DOES accept the input and output type you want. Then one great big rule that matches all inputs and produces all outputs, which make should deduce needs to call the general rule lots of times.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Normally you would have something like..
if
then
foo bar
fi
but what if you wanted to do something like
if
then
foo bar
fi
How do I get Unix to accept anything that matches a pattern of FILENAME with anything after it during an in if statement? (3 Replies)
Discussion started by: LordJezo
3 Replies
2. UNIX for Dummies Questions & Answers
Hi everyone
first of all you should know that I've been working with solaris for a few days only. :)
I need to install some programs and I have had the following troubles:
1. When I used /.configure it showed the following message:
"no acceptable C compiler found in $PATH"
I included... (2 Replies)
Discussion started by: eldiego
2 Replies
3. Linux
hello everyone,
while i am compiling a c++ module.at the compilation end i am getting the following error.
=======================
Configuration lookup disabled for target"/swtemp/usbs/cc/unix-ce/root/subsys/cb/cdbc/obj_0001/HP-UX//rdr_types.h"
what does it mean.can somebody clarify the... (0 Replies)
Discussion started by: mannam srinivas
0 Replies
4. UNIX for Dummies Questions & Answers
hi,
i am trying to run make command in solaris 9.
its giving the error:
make:Fatal error:Command failed for target 'obj/gp_unix.o'
i came to know X11 should be inastalled for gp_unix.o.But it is already installed.still the same error.
./configure worked fine.
can anybody please suggest... (3 Replies)
Discussion started by: rosalina
3 Replies
5. Shell Programming and Scripting
I am trying to install Expect 5.43 on my Solaris 10 x86 PC. When I run the make file I get - Command failed for target 'exp_inter.o'. I tried to find the file (find / -name exp_inter.o -print 2>/dev/null) but could not. Where can I get this file from? (2 Replies)
Discussion started by: pazzy
2 Replies
6. Programming
hello all,
attached you can find a tool (written in C) that i really need to make it compile under linux
i am able to compile and run it successfully in mac os x, but in linux the compilation fails
the only thing that i did so far is to change the following
#include <sys/malloc.h> to... (13 Replies)
Discussion started by: OneDreamCloser
13 Replies
7. UNIX for Dummies Questions & Answers
Suppose executable X produces files A and B from nothing, Y produces C from A, Z produces D from B, and my final goal is to produce C and D. I wrote the following makefile:
.PHONY: all
all: C D
C: A
Y A
D: B
Z B
A B:
X
This makefile seems to reflect all dependencies, as it should... (2 Replies)
Discussion started by: ybelenky
2 Replies
8. Programming
I have been trying to split up my src directory to clear out files that are not re-compiled very often. Now I have the following setup in my trunk,
trunk/bld
trunk/src/
trunk/src/src_server
trunk/makefile.linux
In the make file, I have compile rules
SOURCELOC = src
# compile src c++... (4 Replies)
Discussion started by: LMHmedchem
4 Replies
9. HP-UX
Hi,
I wanted to configure new iscsi port on HPUX system, i added the target port address and configured it, once done, went to array side and searched for that host iqn number , but was nt able to find the same, came to host, then when i ran "iscsiutil -pVS" command it gave me below result
... (0 Replies)
Discussion started by: Vinay Kumar D
0 Replies
10. 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
LEARN ABOUT DEBIAN
mh_patchpoms
MAVEN(1) User Commands MAVEN(1)
NAME
Maven - Patches the POM files using the Maven dependency rules.
SYNOPSIS
mh_patchpoms [option]...
DESCRIPTION
Reads the file debian/$package.poms and tranform each POM file listed in the .poms file into a POM file using the Debian versions of the
libraries. Also keeps a backup of each POM file which can be restored with mh_unpatchpoms
OPTIONS
-h --help: show this text
-V --version: show the version
-p<package> --package=<package>: package to act on
-k --keep-pom-version: keep the original version of the POMs but,
convert all other versions in dependencies and plugins If there is a parent POM, keeps its version except when the parent is already
registered in the Maven repository
-e<version>, --set-version=<version>: set the version for the POM,
do not use the version declared in the POM file.
-r<rules> --rules=<rules>: path to the file containing the
rules to apply when cleaning the POM. Optional, the default location is debian/maven.rules
-R<rule>, --extra-rule=<rule>: extra rule to apply when cleaning the POM
May occur multiple times, instead of or in addition to -r
-u<rules> --published-rules=<rules>: path to the file containing the
extra rules to publish in the property debian.mavenRules in the cleaned POM. Optional, the default location is debian/maven.pub-
lishedRules
-U<rule>, --extra-published-rule=<rule>: extra rule to publish
May occur multiple times, instead of or in addition to -u
-i<rules> --ignore-rules=<rules>: path to the file containing the
rules used to remove certain dependencies from the cleaned POM Optional, the default location is debian/maven.ignoreRules
-I<rule>, --extra-ignore-rule=<rule>: extra rule used to remove dependencies
from the transformed POM May occur multiple times, instead of or in addition to -i
-c<rules> --clean-ignore-rules=<rules>: path to the file containing the
rules use to remove certain dependencies from the cleaned POM, in addition to the ignore rules specified previously. This is useful
in situations such as when the Maven clean target requires more dependencies or plugins to ignore than the build target. All rules
defined in clean-ignore-rules will be added to the existing rules in ignore-rules. Optional, the default location is
debian/maven.cleanIgnoreRules
-s --no-rules: don't apply any rules for converting versions,
do not even convert versions to the default 'debian' version
--no-publish-used-rule: don't publish the rule used to transform
a POM's own attributes in debian.mavenRules
-d --debian-build: transform during a Debian build, which means that
some POM elements will be removed
-b --build-no-docs: if the build doesn't need to build documentation, use this
option to remove some POM elements (in particular plugins) which are useless here and may require extra dependencies and make the
packaging harder.
-m<repo root>--maven-repo=<repo root>: location of the Maven repository,
used to force the versions of the Maven plugins used in the current POM file with the versions found in the repository
-v --verbose: show more information while running
-n --no-act: don't actually do anything, just print the results
See also: mh_installpoms(1), mh_patchpom(1)
Maven Repo Helper version 1.7.1 January 2012 MAVEN(1)