Rockbox Development > Starting Development and Compiling

Manual Building issues

<< < (4/5) > >>

GodEater:

--- Quote from: BdN3504 on August 27, 2009, 06:37:19 AM ---it's somewhat complicated and doesn't work without linux  ;D i first build a manual using "make manual". this gives me the output files which lack references etc. i then take the "rockbox-build.tex" file, open it with texnic, compile it et voilà i got the manual with references.
i got myself miktex after reading the manualhowto wiki Windows native.

--- End quote ---

Also, this is not the wiki, this is the forums.

BdN3504:

--- Quote from: bluebrother on August 27, 2009, 05:14:32 PM ---This simply means that the sources haven't been LaTeX'ed often enough to resolve the references. That's somewhat strange as the Makefile takes care about this. You should check if the LaTeX run that is actually running is the only one -- probably some error occurs which makes the make run stop after the first invocation.
--- End quote ---
hahha lol.
after i "make manual" i get an error i have to skip with "R". still manual has no references.
execute "make manual" again, works like a charm. i'll post the output of the bash in a sec.
first run
second run

bluebrother:
If you look close at the output you'll notice errors in both runs. During the first run you get an error (line 386 in the pastebin)

--- Code: ---<rockbox_interface/images/ss-id3-viewer-240x320x16.png, id=416, 180.675pt x 240
.9pt> <use rockbox_interface/images/ss-id3-viewer-240x320x16.png> [26] [27 <./r
ockbox_interface/images/ss-id3-viewer-240x320x16.png (PNG copy)>]
! Undefined control sequence.
\ActionRCPsToggleMode ->Long \ButtonPlay

--- End code ---

This causes the LaTeX call to return an error code, thus the make run stops. During the second run you get the same error again (this time in line 185 of the paste). As the first run generated the file required for actually filling up the page numbers and references the second run will contain numbers. This does not mean that those are correct -- in fact they are most likely not:

--- Code: ---LaTeX Warning: Label(s) may have changed. Rerun to get cross-references right.
--- End code ---

In any case, you have a problem with the LaTeX sources -- they are broken. You only get an output file because the error is not that fatal that it could not generate a file at all, and because LaTeX is running in nonstopmode -- which means it won't stop if an error occurs until that error is completely fatal. This is intended to make handling easier if the sources are actually broken during development.

BdN3504:
thanks for this accurate answer. so does this only happen to me? or do all of you guys own latex sources that aren't broken and somehow my ip is listed on the server hosting the svn repositry to receive faulty sources?

AlexP:
I've fixed the source now - it was only broken for the gigabeat which is why it wasn't noticed.  Update to current SVN and try again.

Note that the html output is still broken (for a completely unrelated reason), but the pdf should be fine.

Navigation

[0] Message Index

[#] Next page

[*] Previous page