10 More Discussions You Might Find Interesting
1. Programming
xmake is a make-like build utility based on lua. (Link to project site: xmake)
The project focuses on making development and building easier and provides many features (.e.g package, install, plugin, macro, action, option, task ...), so that any developer can quickly pick it up and enjoy the... (1 Reply)
Discussion started by: waruqi
1 Replies
2. Programming
Hi,
Could someone tell me why make utility is mostly preferred for compilation and generating executable in UNIX rather than any user created scripts which contains commands for compilation? (2 Replies)
Discussion started by: naan
2 Replies
3. Programming
Hi,
I'm trying to create a C program that functions like the make utility in UNIX for personal use. My program would read in from a generic makefile and execute whatever is in that makefile but I'm not sure as to where I should start coding.
I would appreciate any help.
Thanks. (1 Reply)
Discussion started by: kratos.
1 Replies
4. UNIX for Dummies Questions & Answers
Hi want to know the syntax of printing something (value or variable) in GNU make utility. I give this in the Makefile:
echo "Hi"
OR
@echo "Hi"
But I only get error this when I run make (at the line where I have echo):
Makefile:9: *** missing separator. Stop.
Whats the problem? How can... (2 Replies)
Discussion started by: radiatejava
2 Replies
5. Solaris
(Sorry for previous not on enlish! I did not realized it is english forum. )
I am looking for help with Make utility. I could not get help from the 'man' pages.
1. About Macro (as a variable): It is clear about defining any macro in beginning or in command line, but isn't it no way to redefine... (0 Replies)
Discussion started by: alex_5161
0 Replies
6. UNIX for Dummies Questions & Answers
Hello all
im looking for some kind of utility that convert make files to dsp files
is there any kind of tool/script that does this job?
thanks (1 Reply)
Discussion started by: umen
1 Replies
7. Solaris
Hi Guys,
I m very confused about the make/makefile utility in all unix.
1) My questions is why we need make.
2) Why some source code needs to complile.
3) I download the Bind 9 from Sunfreeware.com. I use pkgadd -d to install the bind. I 'm struck here becasue I can't find /etc/named.conf... (2 Replies)
Discussion started by: bigmoon
2 Replies
8. Programming
I wrote a makefile, every thing is working fine,
But One of the C header files which is created by me is kept in a different folder other than the current directory,
I have given this PATH to VPATH Variable
Example :- VPATH = /home/user1/projects/victor.h
It gives an error as : file... (4 Replies)
Discussion started by: victorvvk
4 Replies
9. Programming
When we run the make utility , make compiles only those files which are undergone changes(other files which have not undergone any changes are not recompiled)
The Following quotes says
When you run the make utility, it examines the modification times of files and determines what needs to be... (4 Replies)
Discussion started by: victorvvk
4 Replies
10. Programming
The following is my makefile. When I run "make", it gives me a bunch of error. I've compiled each file separately and there are no compilation errors.
The target is "monprc". Have a look below:
monprc: monprc.o monrep.o dsz.o
cc -o monprc monprc.o monrep.o dsz.o
monprc.o: monprc.c... (1 Reply)
Discussion started by: Yifan_Guo
1 Replies
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)