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
gtkdoc-mktmpl
gtkdoc-mktmpl(1) General Commands Manual gtkdoc-mktmpl(1)NAME
gtkdoc-mktmpl -- GTK DocBook documentation generator.
SYNOPSIS
gtkdoc-mktmpl [ See below ]
DESCRIPTION
gtkdoc-mktmpl This creates or updates the template files which contain the manually-edited documentation. (A template is a simple text form
which is filled in with the description of a function, macro, enum, or struct. For functions and macros it also contains fields for
describing the parameters.)
This script reads in the existing templates, found in tmpl/*.sgml, moves these files to tmpl/*.sgml.bak, and then recreates the .sgml files
according to the structure given in the file MODULE-sections.txt.
Any new templates added, or new function parameters, are marked with FIXME so you can do a grep to see which parts need updating.
Any templates which are no longer used (i.e. they are remove from MODULE-sections.txt) are placed in the file tmpl/MODULE-unused.txt. If
they are included again later they are automatically copied back into position. If you are certain that these templates will never be used
again you can delete them from MODULE-unused.txt.
Any parameters to functions which are no longer used are separated from the rest of the parameters with the line <!-- # Unused Parameters #
-->. It may be that the parameter name has just been changed, in which case you can copy the description to the parameter with the new
name. You can delete the unused parameter descriptions when no longer needed.
EXAMPLE
See /usr/share/doc/gtk-doc-tools/examples, for a makefile.am and a configure.in example file.
AUTHOR
This manual page was written by Christian Marillat marillat@debian.org for the Debian GNU/Linux system (but may be used by others).
gtkdoc-mktmpl(1)