Ah ok, thanks for the info. I think I've gained more information on how
the process works. I've tested it locally and is enough to save one of
the xml file to trigger the overwriting of the existing pdf.
I think Christian is right about the problem that can arise if figures
are introduced as dependencies. Now that I know how the infrastructure
works, if there are important chanages to figures, I can trigger the
server side pdf creation by committing an updated xml file. Could that
be an acceptable solution?
Thanks for the info.
Cristian
Il 06/09/2011 08:46, Christian Stimming ha scritto:
Zitat von Geert Janssens <janssens-ge...@telenet.be>:
Which means that the pdf target has not rebuilt since Jul 2.
However, the
build rule *is*:
make html pdf
Are you sure there have been any changes to the source files since
Jul 2 ? I
don't see a need to rebuild the pdf is its sources are unchanged.
(Looking at the rules now...)
It seems the images are not marked as dependencies of the pdf files.
So if an
images is changed, this will not trigger a rebuild. Perhaps we should
list the images as dependencies to fix this ?
We could, but you can easily imagine the follow-up problem with this:
As soon as any editor changes a filename of an image or removes one,
he/she will surely forget to adapt those makefile dependency rules,
causing another break of build... but maybe that's not a problem and
it is probably a good idea to add the images as dependencies.
Regards,
Christian
_______________________________________________
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
.
_______________________________________________
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
