12-29-2007
how to enable #ifdef macro in the command line of make?
[Keyword] Linux, C++, make, macro
In source code, we used some #ifdef macros. How can I enable #ifdef macro in the command line of "make" (NOTE: I do NOT want to change source code or makefile to define that macro from time to time).
e.g. test.cpp:
...
#ifdef TEST1
// code segment for test1
...
#endif
...
#ifdef TEST2
// code segment for test2
...
#endif
....
Question: How can I enable either macro via command line of make?
e.g. make ????? -> enable TEST1
make ????? -> enable TEST2
Thanks in advance!
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello the great gurus :)
I'm quite new to this, so perhaps I'm asking a simple and trivial question (which is good, because you'll answer for sure :))))
Anyway. I have an amount of *.c files (about 100), and what I want to do, is to surround a specific function call with #ifdef and #endif.
... (6 Replies)
Discussion started by: xxxaxa
6 Replies
2. Programming
I think there is no problem to use any macro in a new macro definishion, but I have a problem with that.
I can not understand why?
I have a *.mak file that inludes file with many definitions and rules.
##############################################
include dstndflt.mak
...
One of the... (2 Replies)
Discussion started by: alex_5161
2 Replies
3. Homework & Coursework Questions
I have no idea what the following means. The teacher is too advanced for me to understand fully. We literally went from running a few commands over the last few months to starting shell scripting. I am not a programmer, I am more hardware oriented. I wish I knew what this question was asking... (3 Replies)
Discussion started by: Wookard
3 Replies
4. Shell Programming and Scripting
I have a file with stats for different month, I use the cat and grep combination to search for different month.
cat <file> | grep "April"
cat <file> | grep "May"
cat <file> | grep "June"
etc.
How do you make this command interactive. So that I can give the values for the search. Thanks... (7 Replies)
Discussion started by: purelltab
7 Replies
5. Shell Programming and Scripting
Task A: Make a one-line Unix command - using pipe(s) - to display the number of files in your home directory including the hidden files that begin with '.'
Task B:Make a one-line Unix command - using pipe(s) - to display the number of unique zip codes in famous.dat (hint: use -u on sort)
Task... (1 Reply)
Discussion started by: wises
1 Replies
6. Shell Programming and Scripting
Hi Guys,
I have a a bash script and i am exporting a variable in it.
I am calling a csh script from this bash script.
The variable "ABC" will be visible in csh script.
ks.bash
export ABC = abc
./kp.csh
ab.csh
echo $ABC
setenv ABC =cde (i want to assign this value to ABC only if... (4 Replies)
Discussion started by: vdhingra123
4 Replies
7. UNIX for Dummies Questions & Answers
Why can I not use the enable command?
*sofiazoe* (2 Replies)
Discussion started by: anglenasalt
2 Replies
8. Programming
DELETED (2 Replies)
Discussion started by: ProgMan2015
2 Replies
9. Homework & Coursework Questions
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
1. The problem statement, all variables and given/known data:
1) The script is executed in the Korn shell.
2) Name the shell script file is asg6s.
3) The asg6s file is... (7 Replies)
Discussion started by: ProgMan2015
7 Replies
10. UNIX for Advanced & Expert Users
Heyas
I'm currently trying to make 'make uninstall' work properly, as it doesnt remove empty directories.
To do so, i've applied:
uninstall-hook:
if test -d $docdir; then rmdir $docdir; fi
As stated (example) in automake - 'make uninstall': Howto remove empty directories - Stack... (2 Replies)
Discussion started by: sea
2 Replies
PMCPP(1) General Commands Manual PMCPP(1)
NAME
pmcpp - simple preprocessor for the Performance Co-Pilot
SYNOPSIS
pmcpp [-D name[=value] ...] [infile]
DESCRIPTION
pmcpp provides a very simple pre-processor for manipulating Performance Metric Name Space (PMNS) files for the Performance Co-Pilot (PCP).
It is most commonly used internally to process the PMNS file(s) after pmLoadNameSpace(3) or pmLoadASCIINameSpace(3) is called.
Input lines are read from infile (or standard input if infile is not specified), processed and written to standard output.
All C-style comments of the form /* ... */ are stripped from the input stream.
There are no predefined macros for pmcpp although macros may be defined on the command line using the -D option, where name and value must
follow the same rules as described below for the #define directive.
pmcpp accepts the following directives in the input stream (like cpp(1)):
* #include "filename"
or
#include <filename>
In either case the directory search path for filename tries filename first, then the directory for the command line infile (if any),
followed by the $PCP_VAR_DIR/pmns directory. #include directives may be nested, up to a maximum depth of 5.
* #define name value
Defines a value for the macro name which must be a valid C-style name, so leading alphabetic or ``_'' followed by zero or more alphanu-
merics or ``_''. value is optional (and defaults to an empty value) but when present it may not contain white space and quoting or
escaping is not supported.
* #undef name
Removes the macro definition, if any, for name.
* #ifdef name
...
#endif
or
#ifndef name
...
#endif
The enclosing lines will be stripped or included, depending if the macro name is defined or not.
Macro substitution is achieved by breaking the input stream into words separated by white space or one of the characters ``.'' or ``:'' -
this matches the syntax of the PMNS, see pmns(5). Each word is checked and if it matches a macro name, the word is replaced by the macro
value, otherwise the word is unchanged.
There is generally one output line for each input line, although the line may be empty if the text has been stripped due to the handling of
comments or conditional directives. When there is a change in the input stream, an additional output line is generated of the form:
# line "name"
to indicate the following line of output corresponds to line number line of the input file name.
Important cpp(1) features that are not supported by pmcpp include:
* #if expr
...
#endif
* Nested use of #ifdef or #ifndef.
* #else within an #ifdef or #ifndef.
* Stripping C++ style comments, as in // comment
* Error recovery - the first error encountered by pmcpp will be fatal.
* cpp(1) command line options like -U , -P and -I.
PCP ENVIRONMENT
Environment variables with the prefix PCP_ are used to parameterize the file and directory names used by PCP. On each installation, the
file /etc/pcp.conf contains the local values for these variables. The $PCP_CONF variable may be used to specify an alternative configura-
tion file, as described in pcp.conf(5).
SEE ALSO
cpp(1), pmLoadASCIINameSpace(3), pmLoadNameSpace(3), pmns(5), pcp.conf(5) and pcp.env(5).
Performance Co-Pilot PMCPP(1)