osmo-gsm-manuals in project repos: I see no .pdf
Hi Oliver, so I merged the stuff to add the manuals to the individual git repositories, since you said that it works. But when I do --enable-manuals I don't see any PDF files generated. Also a manual 'make pdf' says "nothing to be done". (I probably should have tried it before merging after all) So what am I doing wrong? Alternatively, can you fix it please? ~N
Worked for me™ I'll look into it right away. On 11/27/18 7:13 PM, Neels Hofmeyr wrote:
Hi Oliver,
so I merged the stuff to add the manuals to the individual git repositories, since you said that it works. But when I do --enable-manuals I don't see any PDF files generated. Also a manual 'make pdf' says "nothing to be done".
(I probably should have tried it before merging after all)
So what am I doing wrong? Alternatively, can you fix it please?
~N
-- - Oliver Smith <osmith@sysmocom.de> https://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte
Oh, you were probably looking for them in the root directory, right? They get placed in doc/manuals/: $ cd osmo-bsc $ ./configure --enable-manuals $ make $ find -name '*.pdf' ./doc/manuals/osmobsc-vty-reference.pdf ./doc/manuals/osmux-reference.pdf ./doc/manuals/osmobsc-usermanual.pdf ./doc/manuals/aoip-mgw-options.pdf $ cd ../osmo-msc $ ./configure --enable-manuals $ make $ find -name '*.pdf' ./doc/manuals/osmomsc-usermanual.pdf ./doc/manuals/osmomsc-vty-reference.pdf Sorry for the confusion and thanks for merging the patches. I see that you have even adjusted the commit message everywhere. Oliver On 11/28/18 10:05 AM, Oliver Smith wrote:
Worked for me™
I'll look into it right away.
On 11/27/18 7:13 PM, Neels Hofmeyr wrote:
Hi Oliver,
so I merged the stuff to add the manuals to the individual git repositories, since you said that it works. But when I do --enable-manuals I don't see any PDF files generated. Also a manual 'make pdf' says "nothing to be done".
(I probably should have tried it before merging after all)
So what am I doing wrong? Alternatively, can you fix it please?
~N
-- - Oliver Smith <osmith@sysmocom.de> https://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte
I ran into something similar a while back and it turned out not to be the merge itself, but how the manuals are actually wired into the build system. A couple of things worth checking: 1. --enable-manuals usually just enables the rules, but the toolchain for generating PDFs has to be present (dblatex, xsltproc, latex, etc., depending on how your project does it). If any of those are missing, make will happily say there’s nothing to do. 2. In some setups only HTML gets built by default; PDF targets are conditional. Try make clean and then make manuals or make doc-pdf if such a target exists. For example, check website: https://brainrot-clicker.io 3. Check whether the manuals are now in a subdirectory like doc/ or manual/ in each repo — they might be building to a different output path than before. 4. Finally, after the merge, verify that the Makefile.am / CMakeLists actually includes the manuals directory. Sometimes the repo move breaks relative paths, so the build system literally doesn’t “see” any sources to generate PDFs from.
participants (3)
-
killaterro＠gmail.com -
Neels Hofmeyr -
Oliver Smith