An analogy from the compilation scene -- normally you would have lines in your Makefile like:
you would not have the *.c as targets because you would have created them with an editor (with the exception of things like lex/yacc generated files, in which case you would have entered the requisite base files for them).
If you really need something to create the *.txt files, then I suggest that you create an initialization script that touches a.txt, b.txt, etc. -- which is exactly what I did: it made the initial content of the [abcd].txt files to be "0" so that a) they existed, b) had a value with which the demonstration equivalent of myscript could work.
If your solution performs satisfactorily, then use it; if not, then you might consider the suggestion above.
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)
Hi All
I need to parse the target
something like:
ifeq '$@' 'first'
echo 1 $@
endif
ifeq '$@' 'second'
echo 2 $@
endif
The thing is to be able compare the target string to any string and then do the commands
Thanks a lot
ziv (0 Replies)
Greetings!
I'm fairly new to the unix world and I hope someone here can help me with my question. I'm using a Makefile to run a few programs and the final output is several .eps files. However I need them to be .pdf files, so I want to use epstopdf to convert the files.
Since I'm already... (6 Replies)
Hi All
I am creating a makefile and I want to do a clean section.
In the clean section I would like to check if the file exists and then delete it.
I always have an error 'unexpected end of file'
What's wrong in it?
Thanks
msntn
firstCpp: first.cpp
g++ -o first first.cpp
clean:
... (1 Reply)
Hi,
As part of our project, we need to load historical data for a year before our system is live. We have the data feed files that we need to load. However, I need to make sure that the file structure (number of fields separated by a comma) on the field is same for all the files of the same... (1 Reply)
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)
I am trying to create executables for the following files
Currently, I am making 9 different directories for for each. I would like to make 1 directory but everytime I try it does not work.
CROSS_COMPILE?=
# CROSS_COMPILE used to = arm-arago-linux-gnueabi... (1 Reply)
Hello,
I want to merge multiple files (under hundreds folders) side by side. File name are the same but folder are different.
like
folder1/same_name.txt
folder2/same_name.txt
folder3/same_name.txt
......Normally it can be done as
paste /different_path*/same_name.txt > merged_file.txtbut... (2 Replies)
Hi,
I have a question related to makefile. I'm new to makefile and I'm in the process of writing a makefile for my RBT build. I have multiple source files and when I compile them I will get multiple object files (one object file for each source file). I'm having problem in creating a target for... (1 Reply)
Discussion started by: Anand Venkatesa
1 Replies
LEARN ABOUT DEBIAN
caspar-typesetting
caspar-typesetting(7) MISCELLANEOUS caspar-typesetting(7)
NAME
caspar-typesetting - Makefile snippets for common typesetting tasks
SYNOPSIS
In a Makefile, write
include caspar/mk/docbook.mk
or
include caspar/mk/pod.mk
.
DESCRIPTION
The caspar docbook.mk and pod.mk files are Makefile snippets for common typesetting tasks, like typesetting LaTeX (see [3]), DocBook XML,
DocBook SGML (see [2]) and POD (see [1]) documents. You just have to type make, instead of stuff like jade -t tex -d caspar/print.dsl
/usr/share/sgml/declaration/xml.dcl foobar.dbx.
USAGE
In a directory where you maintain .dbx (Docbook XML) or .tex (LaTeX) files, do
$ echo include caspar/mk/docbook.mk > Makefile
$ vi karenina.dbx
$ make karenina.view
$ make karenina.print
$ vi svejk.tex
$ make svejk.view
$ make svejk.print
$ make
$ make clean
Other targets: filename.ps, filename.pdf, filename.2ps, filename.html, filename.printbig, filename.dvi.
Variables you might like to set in your Makefile: XMLDCL (default is /usr/share/sgml/declaration/xml.dcl; if you're not on a Debian
GNU/Linux system, you'll likely have to adjust this), HTML_DSL, PRINT_DSL.
In a directory where you maintain .pod files, do
$ echo include caspar/mk/pod.mk > Makefile
$ vi lire.pod
$ perldoc ./lire.pod
$ make lire.pdf
$ make
$ less lire.overstrike-txt
$ make clean
Other targets: filename.ps, filename.html, filename.txt, ... (Similar to the ones supplied by docbook.mk).
EXAMPLES
Some examples: Overriding the caspar-supplied DSSSL files: Create your own print.dls and html.dsl, in the same directory as your Docbook XML
files. Your Makefile should read:
PRINT_DSL = print.dsl
HTML_DSL = html.dsl
include caspar/mk/docbook.mk
Overriding the standard html-to-text convertor:
$ W3M=lynx make svejk.txt
.
FILES
caspar/mk/docbook.mk, caspar/mk/pod.mk
ENVIRONMENT
For docbook.mk: files: XMLDCL, HTML_DSL, PRINT_DSL; utilities: JADE, PDFJADETEX, PDFLATEX, JADETEX, LATEX, W3M, DVIPS, PSNUP, LPR, GV; set-
tings: JADE_MAXERRORS. These variables can get adjusted in Makefile, as well as in the shell environment.
pod.mk Uses no environment variables.
AUTHOR
Joost van Baal-Ili
SEE ALSO
caspar(7) [1] perlpod(1) about Perl's Plain Old Documentation format
[2] DocBook: The Definitive Guide on http://docbook.org/,
[3] The LaTeX Project Homepage on http://www.latex-project.org/.
Some comments on advanced usage are in the files docbook.mk and pod.mk itself.
caspar-typesetting 20120508 8 mai 2012 caspar-typesetting(7)