You are viewing a plain text version of this content. The canonical link for it is here.
Posted to docs@httpd.apache.org by Joshua Slive <jo...@slive.ca> on 2003/01/08 19:01:29 UTC
build system out of memory
At the moment we have java OutOfMemory errors on at least some platforms
when building the docs. This is a pain, and adds to the already difficult
process of getting the docs tree setup and built. Any suggestions for
simplifying the stylesheets to get rid of this problem? Alternatively,
should we add André's -Xmx128m -mx128m workaround to the build2.cmd (at
least on win32)?
Joshua.
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org
Re: build system out of memory
Posted by André Malo <nd...@perlig.de>.
* Andr� Malo wrote:
> I've attached the diff against the current build.xml, the entire new
> build.xml
*gna* seems, I'm getting old. My fingers are much faster than my brain.
I forgot to mention, that I fixed also the dependset, to reflect the real
dependencies better.
However, the fix was not complete, since it causes under some circumstances
some html files with no xml sources to be deleted...
I've attached the intended patch and full build.xml again. Sorry for
spamming ;-)
nd
--
Wenn nur Ingenieure mit Diplom programmieren w�rden, h�tten wir
wahrscheinlich weniger schlechte Software.
Wir h�tten allerdings auch weniger gute Software.
-- Felix von Leitner in dasr
Re: build system out of memory
Posted by André Malo <nd...@perlig.de>.
* Joshua Slive wrote:
> At the moment we have java OutOfMemory errors on at least some platforms
> when building the docs. This is a pain, and adds to the already difficult
> process of getting the docs tree setup and built. Any suggestions for
> simplifying the stylesheets to get rid of this problem?
- moving the modulefilelist back to allmodules.xml should save some memory
- separating the special pages from the "usual" stylesheets may also be
helpful
(all of this was suggested by you already, I know ;-).
> Alternatively,
> should we add Andr�'s -Xmx128m -mx128m workaround to the build2.cmd (at
> least on win32)?
I think, that's a good idea, although I don't know, whether good in
general.
However, I think I have an (additional) solution that solves a lot of other
problems, too. While looking for some other hints (fop & pdf :) I found
<http://ant-contrib.sourceforge.net/ant-contrib/manual/tasks/index.html>
There is a useful <foreach> task provided. The task calls a particular
target while iterating over a fileset (for example). I've changed the
build.xml to do so and the <style> task will be executed dedicated for
_every_ source file instead for a set of files.
This means:
- build.xml becomes much simpler
- no more caching problems, and generally less memory usage
- but: it's slower at all (build en takes about 4 minutes on my machine),
but that's acceptable, I think.
I had to compile the .jar file myself, because there's no binary download
(*grmbl*, 35 MB Java SDK..).
I've attached the diff against the current build.xml, the entire new
build.xml and the ant-contrib.jar file (application/octet-stream, hoping
it's ok). put the jar file simple into the build/lib directory.
The ant-contrib stuff is licensed under Apache license, so it should be no
problem to put it into the CVS repository.
To shorten the excessive screen output ant provides an additional (so
called) logger which is chosen via command line interface. (see the
build-scripts.diff). The logger suppresses empty target outputs, the rest
is the same as usual.
nd
--
s s^saaaaaoaaaoaaaaooooaaoaaaomaaaa a alataa aaoat a a
a maoaa a laoata a oia a o a m a o alaoooat aaool aaoaa
matooololaaatoto aaa o a o ms;s;\s;s;g;y;s;:;s;y#mailto: #
\51/\134\137| http://www.perlig.de #;print;# > nd@perlig.de
Re: build system out of memory
Posted by Astrid Keßler <ke...@kess-net.de>.
>> The attched patch of build.xml should help. Someone has to commit this,
>> because I lack the neccessary commit rights.
> Ummm... Could you tell me what it does. I don't really understand the
> point.
This simply separates the generation of directive index and module
index. Both of them use sitemap.xml to collect their data. This means,
all module docs have mentioned there are read.
As I understand the build process right, first, all module docs are read
and the directive index is build. Then all module docs are read again
and the module index is build. This blasts the available memory.
The patch separates this process and force the build procedure to free
the memory after directive index and before reading the module docs for
building the module index.
Hm, nd should be able to explain it better. It's his patch to help me
with the same problem some days ago.
> [Also, check the mime type on your patches. That one got
> application/octet-stream, which is a pain to deal with.]
Oups, sorry. I should not use my newsreader to send mails.
Kess
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org
Re: build system out of memory
Posted by Joshua Slive <jo...@slive.ca>.
On Wed, 8 Jan 2003, Astrid Keßler wrote:
> > At the moment we have java OutOfMemory errors on at least some platforms
> > when building the docs. This is a pain, and adds to the already difficult
> > process of getting the docs tree setup and built. Any suggestions for
> > simplifying the stylesheets to get rid of this problem?
>
> The attched patch of build.xml should help. Someone has to commit this,
> because I lack the neccessary commit rights.
Ummm... Could you tell me what it does. I don't really understand the
point.
[Also, check the mime type on your patches. That one got
application/octet-stream, which is a pain to deal with.]
Thanks.
Joshua.
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org
Re: build system out of memory
Posted by Astrid Keßler <ke...@kess-net.de>.
> At the moment we have java OutOfMemory errors on at least some platforms
> when building the docs. This is a pain, and adds to the already difficult
> process of getting the docs tree setup and built. Any suggestions for
> simplifying the stylesheets to get rid of this problem?
The attched patch of build.xml should help. Someone has to commit this,
because I lack the neccessary commit rights.
Kess
Re: build system out of memory
Posted by Erik Abele <er...@codefaktor.de>.
I realized this behaviour at first when I added the extended character entities and had also some OutOfMemory problems on RH Linux and Win. -Xmx128m -mx128m works quite fine, so +1 on adding it to the build-sys. I would prefer to have it in build2.cmd *and* build.sh...
cheers,
erik
Joshua Slive wrote:
> At the moment we have java OutOfMemory errors on at least some platforms
> when building the docs. This is a pain, and adds to the already difficult
> process of getting the docs tree setup and built. Any suggestions for
> simplifying the stylesheets to get rid of this problem? Alternatively,
> should we add André's -Xmx128m -mx128m workaround to the build2.cmd (at
> least on win32)?
>
> Joshua.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
> For additional commands, e-mail: docs-help@httpd.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org