To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=101883


User rene changed the following:

                What    |Old value                 |New value
================================================================================
                  Status|RESOLVED                  |REOPENED
--------------------------------------------------------------------------------
              Resolution|INVALID                   |
--------------------------------------------------------------------------------




------- Additional comments from [email protected] Wed May 13 15:12:03 +0000 
2009 -------
> the links will be create in the OO_SDK_OUT directory only. So they will be
> created for a user only when the users configured an SDK.

Yes, but that was not my point of my last issue. They simply should just work
without those manual lns.

> They are necessary for linking C++ examples.

Umm, no, that also can be fullfilled by "normal" links

> Whatever you do, you should reconsider your workflow. A user of the SDK can
> always write in the directory where he wants to generate the output.

That's not *my* workflow.

Besides that, the output is generated in the voikko build dir. Of course the
build has access there. So you want to say that it's a bug in voikko that
it doesn't set OO_SDK_OUT themselves? Because I of course cannot set it
globally so that it matches eveyones need....


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