Hi,
I am getting the following error while building on Solaris 64 , while I am trying to build.
Error Snippet :-
----------------------
Makefile:57: *** multiple target patterns. Stop.
make: Leaving directory `/work1/patch/vds6053sun64o/vobs/jvi'
make: *** Error 2
make: Leaving directory... (0 Replies)
I've seen a few other threads like this, but they either went unanswered or failed to answer my question.
How do I set an environment variable in a Makefile?
What I'm trying to do is use GNU make to automate an ant build.
In order to run ant, I've got to first set a few environment... (1 Reply)
Hello,
I'm having a problem with a makefile script i'm trying to write.
I want to compile a C++ program in two possible ways: "make"
(default target, main) and "make debug". When i supply the debug
target, exactly the same as main should be built, but then with the
DEBUG flag (-g -D... (2 Replies)
Hi
I need to modify entire file starting from the 3 line. file looks like this
filename : exp
first line
second
1,"wes","est","ws"
1,"was","qwe","qwa"
also i have to replace the third content from 3 line by a counter . so the output should look like this:
first line
second... (12 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)
Goal: I'm trying to create a PHONY target inside my Makefile so that when I run the command "make backup",
It will move all the files that end in "~" into the specified backup folder.
Here is my code currently, and I'll explain the problem after:
.PHONY: backup
backup:
@mkdir -p... (2 Replies)
I am writing a Makefile for Cobol on Linux.My sample Makefile looks like below.
I do not want to Hardcode Program names in Makefile.Is there any way we can mention directories in Target and Prerequisites instead of File names sothat Makefile Pickup all the files in mentioned path as below.... (8 Replies)
Hi,
I need to use rsync to delete multiple files(only specified files not all) using --delete option, these files are located in different target folders.
Instead of running rsync command multiple times for each file, can we achieve this with one time execution?
your help is much... (0 Replies)
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 SUSE
module::build::compat
Module::Build::Compat(3pm) Perl Programmers Reference Guide 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.12.1 2010-04-26 Module::Build::Compat(3pm)