Re: Patch to build only one file

-----Mensagem Original----- De: "Gabor Hojtsy" <gabor@hojtsy.hu> Para: "Fernando Correa da Conceiçăo" <fernando.conceicao@terra.com.br>; <phpdoc@lists.php.net> Enviada em: sábado, 10 de janeiro de 2004 15:37 Assunto: Re: [PHP-DOC] Patch to build only one file > Hi Fernando! > > > I make two php scripts and a modification on Makefile.in, and with > this you can build the html for one function or a chapter, by example: > > > > make file=./en/reference/mysql/functions/mysq-query.xml > > Build the html only for this function and > > > > make file=./en/reference/mysql/reference.xml > > Build all mysql functions. > > This is for who write/translate the docs as you can see your changes > without build the entire manual, which can take one hour or more, by > example, with this i generate all mysql functions in 3 minutes. > > I need a help with it, in process I generate a .tmp file and I want to > delete it after use, but I´m good with makefiles, so I need this: > > if file != "manual.xml" then delete file. > > > > Instructions: > > 1. Apply the patch on Makefile.in and place the scripts on /scripts > > 2. ./configure > > 3. php ./scripts/geraentidades.php > > This creates a file with all entities(.ent files) that i include > later on .tmp files. You need run this this only after configure or when > a .ent file changes. > > 4. Use make as show above. > > > > Note that if you don´t use file=./.... it don´t change anything on > build process. > > Seems to be a good idea, but as far as I can see, you would be able to > integrate the logic of geraentidades.php to the compila.php script, > since you can pass on the language code when make runs the script, and > getting the entities does not take much time. Also it would be much > simpler to add external entity references to the files (as seen in > manual.xml) instead of copying all the entities one-by-one... Just the > relative paths need to be taken care of. I will do all this changes, and add the entities like the manual.xml is a very good idea!! This is why I request your answer! > > BTW it would be a better idea to write English code, since that has the > only chance of being committed :) I will do. > > Good idea, and not bad implementation anyway! > > Regards, > Goba >