To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=51391 Issue #:|51391 Summary:|instsetooo_native: building modifies source-files |(Image.bmp) Component:|Installation Version:|680m112 Platform:|All URL:| OS/Version:|Linux Status:|NEW Status whiteboard:| Keywords:| Resolution:| Issue type:|DEFECT Priority:|P3 Subcomponent:|code Assigned to:|of Reported by:|cloph
------- Additional comments from [EMAIL PROTECTED] Wed Jun 29 18:28:46 -0700 2005 ------- Building instsetooo_native modifies sourcefiles instead of working with copies in the builddirectories. Scenario: I build OOo in a shadow-tree (created with lndir). The main purpose of this is to always have a pristine, unmodified checkout and a working copy that can be patched and from which a build is created. The only module that breaks this system is instsetooo_native. Instead of modifying files in a subdirectory unxlngiX.pro it modifies files directly in the "repository". These two lines cause the trouble (util/makefile.mk: +$(COPY) $(PRJ)$/res$/nologoinstall.bmp $(MSIOFFICETEMPLATEDIR)$/Binary$/Image.bmp +$(COPY) $(PRJ)$/res$/nologoinstall.bmp $(MSILANGPACKTEMPLATEDIR)$/Binary$/Image.bmp The makefile should work in a work-dir, not in the sources. A workaround that would solve my problem in particular would be to first remove the Image.bmp and then copy the "nologoinstall.bmp". This way the original sources would not be tampered. --------------------------------------------------------------------- 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]