incubator-ooo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jan iversen <>
Subject Re: svn update, simple question.
Date Thu, 25 Oct 2012 09:09:42 GMT
Thanks for the information.

Now I know what I did wrong, I did run configure again but not in a new
shell (forgot the environment variables).

I think the real hazzle is to understand the process, once you get the
initial build done and understand a bit about the build/makefiles it is
pretty clean.

I worked in another project, where the build required you to open 3 shells,
and start different commands at different stages, that was challenging
compared to this :-)

have a nice day.
jan I.

On 25 October 2012 11:03, Herbert Duerr <> wrote:

> On 24.10.2012 18:54, jan iversen wrote:
>> If I do a "svn update trunk" (I have all sources stored in directory
>> trunk", do I then need to run configure again ???
> In most cases you don't need to run configure again.
>  my system seems to be spinning, after "svn update" I cannot run "build" in
>> the single directories that all worked before "svn update".
>> Simple question, hopefully simple answer :-)
> The most simple answer is: do a clean build :-/
> A less simple answer is in the rules of thumb below:
> 1. if the file was modified you need to run "autoconf", then
> "configure", and so on. Best in a new shell because they communicate with
> environment variables
> 2. if dependencies to external libraries were updated you need to run
> "bootstrap" again
> 3. if the interfaces of some modules changed then going into
> instsetoo_native and running "build --all" is recommended. There are issues
> with that though [1] that the buildbots suffer from in their "incremental
> builds" (as opposed to their "clean builds").
> If there were not too many revisions since the last update then the chance
> that none of the points above apply is reasonable and not even the "build
> --all" is needed. It doesn't take too long though and is usually worth the
> time.
> This all shows that building AOO is still quite challenging. Making it
> easier and less error-prone is a very worthwhile goal, even if in practice
> this goal often loses against "let's add a new feature", "freshen up the
> UI" or even "fix a bug".
> [1]**wmlhc5f5zaiiyu2o<>
> Herbert

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message