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


User tono changed the following:

                What    |Old value                 |New value
================================================================================
                      CC|''                        |'tono'
--------------------------------------------------------------------------------




------- Additional comments from [email protected] Sun Oct 18 03:53:06 +0000 
2009 -------
The import library on Windows platform is being renamed from ineon.lib to 
neon.lib at delivery time. Is it essential to do so or can we modify 
solenv/inc/libs.mk instead of renaming the library?

Conventionally the name of the import libraries are different from the shared 
target names. I do not know the reason why but it made mingw port simple.

Mingw port really does not use the .lib style import libraries and create empty 
dummy files just for clearing the dependencies. And if the core name of the 
import libraries are different from the shared target, the linker can safely 
use dll-direct-linking without troubles. If the core name of the import 
librbarary is the same as the dll, the empty dummy file will be used for 
linking and will cause problem.

Currently the cws tkr27 is broken on MinGW but it will be safely buildable if 
we stop renaming ineon.lib at delivery time and set NEON3RDLIB to ineon.lib for 
Windows MSVC build in solenv/inc/libs.mk.


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