To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=102337
                 Issue #|102337
                 Summary|dependencies updated too late
               Component|tools
                 Version|DEV300m49
                Platform|All
                     URL|
              OS/Version|All
                  Status|NEW
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|solenv
             Assigned to|hjs
             Reported by|sb





------- Additional comments from [email protected] Thu May 28 15:13:23 +0000 
2009 -------
In some module where .cxx files are compiled and a shared library is built from
them, do the following:

1  Create a fresh (internal) header foo.hxx that contains a fresh function
declaration "void foo();" (but no definition).
2  In one of the .cxx files, add "#include "foo.hxx" and a call to foo().
3  Build the module, which will fail when linking the shared library, due to the
missing definition of foo().  (And because of the linking failure, the
dependency from the .cxx file to foo.hxx is not updated, because that step would
come afterwards, as Ause says.)
4  Fix foo.hxx to also include an (inline) definition of foo, by changing it to
"void foo {}".
5  Build again:  Linking will fail again as the .cxx will not be recompiled due
to the missing dependency.

---------------------------------------------------------------------
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]

Reply via email to