Sponsored Content
Top Forums Shell Programming and Scripting Building programs from separate makefiles Post 302759445 by Corona688 on Tuesday 22nd of January 2013 10:23:48 AM
Old 01-22-2013
One of the simpler ways to do this is recursive make:

Code:
outputfolder/outputfile:outputfolder/Makefile
        make -C outputfolder

which is equivalent to cd outputfolder ; make

This lets you call a makefile in another folder without having to incorporate it into your own lock, stock, and barrel.

make supports recursion directly, and will tell you how deep into recursion it is.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Combining makefiles

I have concatenated 2 makefiles, to produce 1 however it is not running all of the code, producing a fatal error: symbol referencing errors. No output written. Can anybody please help? (4 Replies)
Discussion started by: Dan Rooney
4 Replies

2. UNIX for Dummies Questions & Answers

makefiles in a directory and subdirectories

I need to develop a makefile that spans across directories. For example, let's say i have an upper level directory (main) and about 2 subdirectories. I want my .cpp files and .o files to be in one subdirectory. I want my .a files to be in the other subdirectory. The .a files are made up of the... (0 Replies)
Discussion started by: benjie_asu
0 Replies

3. Shell Programming and Scripting

How can I print variables im using in makefiles?

for example in my make file im building path from env variables and string but need to see what is did what is the best way to print the result? say I have in my Makefile : exec_prefix = $(RUN_ENV_LOCAL)/apache and I will like to print the exec_prefix value , how can it be done ? (1 Reply)
Discussion started by: umen
1 Replies

4. UNIX for Advanced & Expert Users

makefiles

Solved........ (0 Replies)
Discussion started by: klam
0 Replies

5. UNIX for Dummies Questions & Answers

Are programs like sys_open( ) ,sys_read( ) et al examples of system level programs ?

Are the programs written on schedulers ,thread library , process management, memory management, et al called systems programs ? How are they different from the programs that implement functions like open() , printf() , scanf() , read() .. they have a prefix sys_open, sys_close, sys_read etc , right... (1 Reply)
Discussion started by: vishwamitra
1 Replies

6. Programming

Makefiles for different programs

I have several programs in several directories and want to use make to build the executables. What I have done is to put the main programs in their own directory together with a makefile to build the program. Then I am thinking of having another makefile residing in the directory above so I can run... (1 Reply)
Discussion started by: kristinu
1 Replies

7. Programming

Makefile for building multiple programs

I have the following part of a makefile and want to simplify it using rules rather than having to code the same two blocks when I need ti build another program. An having difficulty doing it all: 1dvel2 1dvel 2dvel ... (8 Replies)
Discussion started by: kristinu
8 Replies

8. Programming

First time programmer needs Help with Makefiles

I am trying to practice to create Makefiles. The goal is to create a makefile such that if a change is made to any of the source code files, the project can be rebuilt by typing make at the command line. I have the following files: ac.cc: has include ac.h and pg.h fr.cc: has main... (8 Replies)
Discussion started by: pintu1228
8 Replies

9. UNIX for Dummies Questions & Answers

Difference between inbuilt suid programs and user defined root suid programs under bash shell?

Hey guys, Suppose i run passwd via bash shell. It is a suid program, which temporarily runs as root(owner) and modifies the user entries. However, when i write a C file and give 4755 permission and root ownership to the 'a.out' file , it doesn't run as root in bash shell. I verified this by... (2 Replies)
Discussion started by: syncmaster
2 Replies

10. UNIX for Beginners Questions & Answers

Makefiles

Hi All, I was going through some makefiles where I saw occurrences of explib_subdirs and expinc_subdirs, which I could not understand. Exporting libs to subdirs ? Exporting include files to specified subdirs ? When do we need to do that ? What I could understand is, for a build, I would... (4 Replies)
Discussion started by: alltaken
4 Replies
Makefile::AST::Evaluator(3pm)				User Contributed Perl Documentation			     Makefile::AST::Evaluator(3pm)

NAME
Makefile::AST::Evaluator - Evaluator and runtime for Makefile::AST instances SYNOPSIS
use Makefile::AST::Evaluator; $Makefile::AST::Evaluator::JustPrint = 0; $Makefile::AST::Evaluator::Quiet = 1; $Makefile::AST::Evaluator::IgnoreErrors = 1; $Makefile::AST::Evaluator::AlwaysMake = 1; $Makefile::AST::Evaluator::Question = 1; # $ast is a Makefile::AST instance: my $eval = Makefile::AST::Evaluator->new($ast); Makefile::AST::Evaluator->add_trigger( firing_rule => sub { my ($self, $rule, $ast_cmds) = @_; my $target = $rule->target; my $colon = $rule->colon; my @normal_prereqs = @{ $rule->normal_prereqs }; # ... } ); $eval->set_required_target($user_makefile) $eval->make($goal); DESCRIPTION
This module implementes an evaluator or a runtime for makefile ASTs represented by Makefile::AST instances. It "executes" the specified GNU make AST by the GNU makefile semantics. Note that, "execution" not necessarily mean building a project tree by firing makefile rule commands. Actually you can defining your own triggers by calling the add_trigger method. (See the "SYNOPSIS" for examples.) In other words, you can do more interesting things like plotting the call path tree of a Makefile using Graphviz, or translating the original makefile to another form (like what the makesimple script does). It's worth mentioning that, most of the construction algorithm for topological graph s (including implicit rule application) have already been implemented in Makefile::AST and its child node classes. CONFIGURE VARIABLES
This module provides several package variables (i.e. static class variables) for controlling the behavior of the evaluator. Particularly the user needs to set the $AlwaysMake variable to true and $Question to true, if she wants to use the evaluator to do special tasks like plotting dependency graphs and translating GNU makefiles to other format. Setting $AlwaysMake to true will force the evaluator to ignore the timestamps of external files appeared in the makefiles while setting $Question to true will prevent the evaluator from executing the shell commands specified in the makefile rules. Here's the detailed listing for all the config variables: $Question This variable corresponds to the command-line option "-q" or <--question> in GNU make. Its purpose is to make the evaluator enter the "questioning mode", i.e., a mode in which "make" will never try executing rule commands unless it has to, "and" echoing is suppressed at the same time. $AlwaysMake This variable corresponds to the command-line option "-B" or "--always-make". It forces re-constructing all the rule's targets related to the goal, ignoring the timestamp or existence of targets' dependencies. $Quiet It corresponds to GNU make's command-line option "-s", "--silent", or "--quiet". Its effect is to cancel the echoing of shell commands being executed. $JustPrint This variable corresponds to GNU make's command line option "-n", "--just-print", "--dry-run", or "--recon". Its effect is to print out the shell commands requiring execution but without actually executing them. $IgnoreErrors This variable corresponds to GNU make's command line option "-i" or "--ignore-errors"ieXXIt's used to ignore the errors of shell commands being executed during the make process. The default behavior is quitting as soon as a shell command without the "-" modifier fails. CLASS TRIGGERS
The "make_by_rule" method of this class defines a trigger named "firing_rule" via the Class::Trait module. Everytime the "make_by_rule" method reaches the trigger point, it will invoke the user's processing handler with the following three arguments: the self object, the Makefile::AST::Rule object, and the corresponding "Makefile::AST::Command" object in the context. By registering his own processing handlers for the "firing_rule" trigger, the user's code can reuse the evaluator to do his own cool things without traversing the makefile ASTs himself. See the "SYNOPSIS" for code examples. CODE REPOSITORY
For the very latest version of this script, check out the source from http://github.com/agentzh/makefile-parser-pm <http://github.com/agentzh/makefile-parser-pm>. There is anonymous access to all. AUTHOR
Zhang "agentzh" Yichun "<agentzh@gmail.com>" COPYRIGHT AND LICENSE
Copyright (c) 2007-2008 by Zhang "agentzh" Yichun (agentzh). This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself. SEE ALSO
Makefile::AST, Makefile::Parser::GmakeDB, pgmake-db, makesimple, Makefile::DOM. perl v5.12.4 2011-08-17 Makefile::AST::Evaluator(3pm)
All times are GMT -4. The time now is 10:00 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy