10 More Discussions You Might Find Interesting
1. Programming
i have make file which i try to make them generic
but it keeps to compline it missing include directory
this is the makefile :
CXX=g++
CPPFAGS= -Wall -O0 -g -std=c++14
INCLUDES = -I/home/vagrant/libuv/include -Isrc
LIBS_DIRS = -L/home/vagrant/libuv/build
LDFLAGS=... (7 Replies)
Discussion started by: umen
7 Replies
2. UNIX for Beginners Questions & Answers
Hello,
I am creating a file with all the source folders included in my git branch, when i grep for the used source, i found source included as relative path instead of absolute path, how can convert relative path to absolute path without changing directory to that folder and using readlink -f ? ... (4 Replies)
Discussion started by: Sekhar419
4 Replies
3. UNIX for Advanced & Expert Users
Currently I am using this laborious command
lvdisplay | awk '/LV Path/ {p=$3} /LV Name/ {n=$3} /VG Name/ {v=$3} /Block device/ {d=$3; sub(".*:", "/dev/dm-", d); printf "%s\t%s\t%s\n", p, "/dev/mapper/"v"-"n, d}'
Would like to know if there is any shorter method to get this mapping of... (2 Replies)
Discussion started by: royalibrahim
2 Replies
4. Shell Programming and Scripting
Hi experts,
I have multiple file names ending with .jsp located in $SOME_DIR, $SOME_DIR/f1/,$SOME_DIR/f2/test,$SOME_DIR/f3/fa
and there are equivalent class files in $SOME_DIR/WEB-INF/classes/_pages,$SOME_DIR/WEB-INF/classes/_pages/_f1,... (0 Replies)
Discussion started by: oraclermanpt
0 Replies
5. Shell Programming and Scripting
I want to pattern match only path part from below and replace them with new path string.
LoadModule jk_module /fldrA/fldrBaf/fldrCaa/modules/mod_jk.so
JkWorkersFile /fldrA/fldrBaf/fldrCaa/config/OHS/ohs1/workers.properties
JkLogFile... (4 Replies)
Discussion started by: kchinnam
4 Replies
6. Shell Programming and Scripting
Hi All,
Can you please provide some pointers to move files from Base path to multiple paths in efficient way.Folder Structure is already created.
/Path/AdminUser/User1/1111/Reports/aaa.txt to /Path/User1/1111/Reports/aaa.txt
/Path/AdminUser/User1/2222/Reports/bbb.txt to... (6 Replies)
Discussion started by: karthikgv417
6 Replies
7. Shell Programming and Scripting
Hi,
I have a file abcd.txt which has contents in the form of full path file names i.e.
$home> vi abcd.txt
/a/b/c/r1.txt
/q/w/e/r2.txt
/z/x/c/r3.txt
Now I want to retrieve only the directory path name for each row
i.e
/a/b/c/
/q/w/e/
How to get the same through shell script?... (7 Replies)
Discussion started by: royzlife
7 Replies
8. Shell Programming and Scripting
I have a script in which i want to print absolute path of the same script irrespective of path from where i run script.
I am using
test.sh:
echo "pwd : `pwd`"
echo "script name: $0"
echo "dirname: `dirname $0`"
when i run script from /my/test/dir/struct as ../test.sh the output i... (10 Replies)
Discussion started by: rss67
10 Replies
9. Shell Programming and Scripting
Hi:
I have a requirement as below:
I have some standard Unix commands modified and kept them in a directory say /usr/clsh/bin. For example I have a script named "ls" kept here which is modified version of "ls" (say it always gives long listing i.e. ls -l).
When any user logs on and types... (2 Replies)
Discussion started by: ramesh_samane
2 Replies
10. UNIX for Dummies Questions & Answers
Hi,
I have a file with about 60 lines of path:
app-defaults/boxXYZ.......
I want to change this to /my/path/goes/here/app-defaults/boxXYZ, but of course vi doesn't like the regualr :s/old/new/ command.
Is there any other quick way to do this?
Thanks ;) (2 Replies)
Discussion started by: Yinzer955i
2 Replies
Module::Build::Compat(3pm) User Contributed Perl Documentation Module::Build::Compat(3pm)
NAME
Module::Build::Compat - Compatibility with ExtUtils::MakeMaker
SYNOPSIS
# In a Build.PL :
use Module::Build;
my $build = Module::Build->new
( module_name => 'Foo::Bar',
license => 'perl',
create_makefile_pl => 'traditional' );
...
DESCRIPTION
Because "ExtUtils::MakeMaker" has been the standard way to distribute modules for a long time, many tools (CPAN.pm, or your system
administrator) may expect to find a working Makefile.PL in every distribution they download from CPAN. If you want to throw them a bone,
you can use "Module::Build::Compat" to automatically generate a Makefile.PL for you, in one of several different styles.
"Module::Build::Compat" also provides some code that helps out the Makefile.PL at runtime.
METHODS
create_makefile_pl($style, $build)
Creates a Makefile.PL in the current directory in one of several styles, based on the supplied "Module::Build" object $build. This is
typically controlled by passing the desired style as the "create_makefile_pl" parameter to "Module::Build"'s "new()" method; the
Makefile.PL will then be automatically created during the "distdir" action.
The currently supported styles are:
traditional
A Makefile.PL will be created in the "traditional" style, i.e. it will use "ExtUtils::MakeMaker" and won't rely on "Module::Build"
at all. In order to create the Makefile.PL, we'll include the "requires" and "build_requires" dependencies as the "PREREQ_PM"
parameter.
You don't want to use this style if during the "perl Build.PL" stage you ask the user questions, or do some auto-sensing about the
user's environment, or if you subclass "Module::Build" to do some customization, because the vanilla Makefile.PL won't do any of
that.
small
A small Makefile.PL will be created that passes all functionality through to the Build.PL script in the same directory. The user
must already have "Module::Build" installed in order to use this, or else they'll get a module-not-found error.
passthrough (DEPRECATED)
This is just like the "small" option above, but if "Module::Build" is not already installed on the user's system, the script will
offer to use "CPAN.pm" to download it and install it before continuing with the build.
This option has been deprecated and may be removed in a future version of Module::Build. Modern CPAN.pm and CPANPLUS will
recognize the "configure_requires" metadata property and install Module::Build before running Build.PL if Module::Build is listed
and Module::Build now adds itself to configure_requires by default.
Perl 5.10.1 includes "configure_requires" support. In the future, when "configure_requires" support is deemed sufficiently
widespread, the "passthrough" style will be removed.
run_build_pl(args => @ARGV)
This method runs the Build.PL script, passing it any arguments the user may have supplied to the "perl Makefile.PL" command. Because
"ExtUtils::MakeMaker" and "Module::Build" accept different arguments, this method also performs some translation between the two.
"run_build_pl()" accepts the following named parameters:
args
The "args" parameter specifies the parameters that would usually appear on the command line of the "perl Makefile.PL" command -
typically you'll just pass a reference to @ARGV.
script
This is the filename of the script to run - it defaults to "Build.PL".
write_makefile()
This method writes a 'dummy' Makefile that will pass all commands through to the corresponding "Module::Build" actions.
"write_makefile()" accepts the following named parameters:
makefile
The name of the file to write - defaults to the string "Makefile".
SCENARIOS
So, some common scenarios are:
1. Just include a Build.PL script (without a Makefile.PL script), and give installation directions in a README or INSTALL document
explaining how to install the module. In particular, explain that the user must install "Module::Build" before installing your module.
Note that if you do this, you may make things easier for yourself, but harder for people with older versions of CPAN or CPANPLUS on
their system, because those tools generally only understand the Makefile.PL/"ExtUtils::MakeMaker" way of doing things.
2. Include a Build.PL script and a "traditional" Makefile.PL, created either manually or with "create_makefile_pl()". Users won't ever
have to install "Module::Build" if they use the Makefile.PL, but they won't get to take advantage of "Module::Build"'s extra features
either.
For good measure, of course, test both the Makefile.PL and the Build.PL before shipping.
3. Include a Build.PL script and a "pass-through" Makefile.PL built using "Module::Build::Compat". This will mean that people can
continue to use the "old" installation commands, and they may never notice that it's actually doing something else behind the scenes.
It will also mean that your installation process is compatible with older versions of tools like CPAN and CPANPLUS.
AUTHOR
Ken Williams <kwilliams@cpan.org>
COPYRIGHT
Copyright (c) 2001-2006 Ken Williams. All rights reserved.
This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
SEE ALSO
Module::Build(3), ExtUtils::MakeMaker(3)
perl v5.14.2 2012-06-27 Module::Build::Compat(3pm)