Re: Changes not propagating when (re)building docs
On Tue, Jul 05, 2011 at 11:28:30AM +0200, Joseph Wakeling wrote: > ... also works. Still, it's a hefty rebuild that results -- all the > different untouched .itely files seem to be reprocessed -- is there any > way of narrowing down the amount of stuff that needs to be rebuilt? Of course there is. Read the make manual, read the source, and patches welcome. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Changes not propagating when (re)building docs
- Original Message - From: "Joseph Wakeling" To: Sent: Tuesday, July 05, 2011 10:28 AM Subject: Re: Changes not propagating when (re)building docs On 07/05/2011 11:16 AM, Joseph Wakeling wrote: So, it looks like changes made to .itely files are not being picked up as relevant to the build process. Any suggestions on how to fix this? Sorry, missed a "Known Issues" note in the contributors' manual: touch Documentation/notation.tely ... also works. Still, it's a hefty rebuild that results -- all the different untouched .itely files seem to be reprocessed -- is there any way of narrowing down the amount of stuff that needs to be rebuilt? Is this any use? http://lilypond.org/doc/v2.14/Documentation/contributor/scripts-to-ease-doc-work -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
RE: Changes not propagating when (re)building docs
Hello, )-Original Message- )From: lilypond-devel-bounces+james.lowe=datacore@gnu.org )[mailto:lilypond-devel-bounces+james.lowe=datacore@gnu.org] On )Behalf Of Joseph Wakeling )Sent: 05 July 2011 10:29 )To: lilypond-devel@gnu.org )Subject: Re: Changes not propagating when (re)building docs ) )On 07/05/2011 11:16 AM, Joseph Wakeling wrote: )> So, it looks like changes made to .itely files are not being picked up )> as relevant to the build process. )> )> Any suggestions on how to fix this? ) )Sorry, missed a "Known Issues" note in the contributors' manual: ) ) touch Documentation/notation.tely ) )... also works. Still, it's a hefty rebuild that results -- all the different )untouched .itely files seem to be reprocessed -- is there any way of )narrowing down the amount of stuff that needs to be rebuilt? ) --- [James' reply:] Joseph, being someone who makes small edits to the documentation regularly and also learning the hard way, if you are making changes to @lilypond examples it is best to use Lilypond-book in a 'test.tely' file first (then you can use texi2pdf to make a dummy PDF) this takes a few seconds and then when you are happy with your example you can cut/paste it into the real document and then make that final build. There is no way currently around just rebuilding your small bit in that single document that I am aware of. I'm happy to help off-list (if I can) if you need more explanation on this. James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Changes not propagating when (re)building docs
On 07/05/2011 11:16 AM, Joseph Wakeling wrote: > So, it looks like changes made to .itely files are not being picked up > as relevant to the build process. > > Any suggestions on how to fix this? Sorry, missed a "Known Issues" note in the contributors' manual: touch Documentation/notation.tely ... also works. Still, it's a hefty rebuild that results -- all the different untouched .itely files seem to be reprocessed -- is there any way of narrowing down the amount of stuff that needs to be rebuilt? ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Changes not propagating when (re)building docs
2011/7/5 Joseph Wakeling : > Hello all, > > I'm preparing a few patches for the notation manual (the section on > contemporary music I started ages back but didn't follow through on > properly), but have encountered a problem. > > I've built both Lilypond and the docs successfully, and now I'm editing > the file > > Documentation/notation/contemporary.itely > > Once done with changes, naturally I use > > make doc > > or > > make doc-stage-1 > > to rebuild the docs. However, my changes to contemporary.itely are not > picked up on. The only way I've found to remedy this is to entirely > delete the notation manual output: Try touching the main itely file for this manual. Documentation/notation/contemporary.itely belongs to the notation manual, so you can touch Documentation/notation.tely then 'make doc' HTH -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Changes not propagating when (re)building docs
Hello all, I'm preparing a few patches for the notation manual (the section on contemporary music I started ages back but didn't follow through on properly), but have encountered a problem. I've built both Lilypond and the docs successfully, and now I'm editing the file Documentation/notation/contemporary.itely Once done with changes, naturally I use make doc or make doc-stage-1 to rebuild the docs. However, my changes to contemporary.itely are not picked up on. The only way I've found to remedy this is to entirely delete the notation manual output: rm -r Documentation/out-www/notation* rm -r Documentation/notation/out-www and redo the make doc-stage-1 from there, which seems rather messy. To check it wasn't just contemporary.itely, I also tried playing with a few of the other files in the Documentation/notation/ directory, with the same result. So, it looks like changes made to .itely files are not being picked up as relevant to the build process. Any suggestions on how to fix this? It's not such a big deal to have to manually delete and rebuild, but it would be nice for the build system to automatically pick up on such changes. Thanks and best wishes, -- Joe ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
