There is daps -m MAIN.myblub.xml ... which can be used instead ofdaps -d DC-myblub ....
Conceptually, the MAIN parameter and ROOTID are the centerpieces of a DC file -- the reason to introduce DC files was originally mostly to cache those two values [1].
However, I guess nothing stops you from using e.g. the daps -m ... syntax in a Makefile or so..?
Not sure what your exact use case is here, though.
hth
Stefan
[1] This is history told by someone who was not there at the inception of DAPS, of course.
Last edit: Stefan Knorr 2017-10-25
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The absolute minimum on input DAPS needs is a MAIN file. Therefore it is sufficient to rum daps -m <MAIN>. In case you need to specify additional parameters such as a rootid or a stylesheet directory, you can use the respective command line parameters to set them.
These additional parameters are usually the same for every build. That's why you can specify a DC-file that defines these parameters, so you do not have to specify them on every run of DAPS. A DC-file is a config file for a book/set/article. If needed, you can have several DC-files for a book, each specifying a different set of parameters (e.g. different stylesheets).
You can override all parameters of a DC-file with the respective command line switches - except for the MAIN file (up to now I had no usecase for this, so I did not implement it).
And btw - -d and -m are mutually exclusive...
Cheers, Frank
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
View and moderate all "DAPS General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion, old (read-only)"
Hi,
is there a command line switch to specify / override the MAIN value of DC file?
Regards,
Martin
I don't think so...
There is
daps -m MAIN.myblub.xml ...which can be used instead ofdaps -d DC-myblub ....Conceptually, the MAIN parameter and ROOTID are the centerpieces of a DC file -- the reason to introduce DC files was originally mostly to cache those two values [1].
However, I guess nothing stops you from using e.g. the
daps -m ...syntax in a Makefile or so..?Not sure what your exact use case is here, though.
hth
Stefan
[1] This is history told by someone who was not there at the inception of DAPS, of course.
Last edit: Stefan Knorr 2017-10-25
View and moderate all "DAPS General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion, old (read-only)"
Well, I can use -m to define my xml file. But I have to set relative path. No more questions at this point.
Hi,
just some additional information:
The absolute minimum on input DAPS needs is a MAIN file. Therefore it is sufficient to rum
daps -m <MAIN>. In case you need to specify additional parameters such as a rootid or a stylesheet directory, you can use the respective command line parameters to set them.These additional parameters are usually the same for every build. That's why you can specify a DC-file that defines these parameters, so you do not have to specify them on every run of DAPS. A DC-file is a config file for a book/set/article. If needed, you can have several DC-files for a book, each specifying a different set of parameters (e.g. different stylesheets).
You can override all parameters of a DC-file with the respective command line switches - except for the MAIN file (up to now I had no usecase for this, so I did not implement it).
And btw - -d and -m are mutually exclusive...
Cheers, Frank