To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=60237
------- Additional comments from [EMAIL PROTECTED] Mon Jan 9 23:22:46 -0800 2006 ------- There's an additional problem with ooo_custom_images when building an OpenOffice.org installation set inside a StarOffice build environment, which only happens when building a CWS, not the MWS. Some pre-requisites, which hopefully explain why I think the current mechanism is flawed: CWS inside Hamburg are organized in a way that only the modules which are added to the CWS do exist on the CWS storage. All other modules are only linked to the MWS. That is, a CWS containint, say, svx but not svtools would look like drwxrwxrwx svx lrwxrwxrwx svtools.lnk -> <mws_location>/svtools Note that the linked modules differ in their naming scheme, they have the extension "lnk". As a result, building instsetoo_native on a Hamburg-hosted CWS does not work, since packimages tries to access <cws_location>/custom_images/..., where only custom_images.lnk does exist (unless this module is added, which is rarely the case). This (and other things) is the reason why there is solenv: content inside a module, which is needed in other modules, should be *delivered* into solenv. IMO, accessing module content directly inside the module is a serious breach of the current build philosophy, and should definately be avoided. (The last two patches from kendy fix this insofar that the build doesn't break anymore, but "only" issues warnings that some non-existing directories have been skipped.) --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
