Re: svn update, simple question.
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 configure.in 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] http://markmail.org/thread/wmlhc5f5zaiiyu2o Herbert
Re: svn update, simple question.
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 h...@apache.org 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 configure.in 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] http://markmail.org/thread/**wmlhc5f5zaiiyu2ohttp://markmail.org/thread/wmlhc5f5zaiiyu2o Herbert
Re: svn update, simple question.
Hi Jan, On 25.10.2012 11:09, jan iversen wrote: Now I know what I did wrong, I did run configure again but not in a new shell (forgot the environment variables). Good. Do you happen to know which environment variables were the problem in this case? It would be great to have a mechanism that avoided this source of confusion but cleaning up such environment variables. AFAIK most of them are supposed to be unset in the script written by the bootstrap step. 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 :-) Wow, that tops the complexity of the AOO build experience quite a bit. For an open-source project I'm afraid we're still way too challenging, especially since the project was disrupted in the transition from the classic OOo build system to a gnumake based system. Herbert
Re: svn update, simple question.
On 25 October 2012 13:03, Herbert Duerr h...@apache.org wrote: Hi Jan, On 25.10.2012 11:09, jan iversen wrote: Now I know what I did wrong, I did run configure again but not in a new shell (forgot the environment variables). Good. Do you happen to know which environment variables were the problem in this case? It would be great to have a mechanism that avoided this source of confusion but cleaning up such environment variables. AFAIK most of them are supposed to be unset in the script written by the bootstrap step. Yes at least I know one CC, I had for experimental use changed it to a different compiler, and configure used it for the Linux script. I will check next time to see if there are others. 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 :-) Wow, that tops the complexity of the AOO build experience quite a bit. For an open-source project I'm afraid we're still way too challenging, especially since the project was disrupted in the transition from the classic OOo build system to a gnumake based system. Herbert
svn update, simple question.
Hi. If I do a svn update trunk (I have all sources stored in directory trunk, do I then 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 :-) jan.
