[
https://issues.apache.org/jira/browse/AXIS2C-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Lazarski resolved AXIS2C-1142.
-------------------------------------
Resolution: Won't Fix
Closing as Won't Fix.
This circular dependency affects Windows DLL
builds but works correctly on Linux/Unix with shared library lazy
symbol resolution. The project currently focuses on Linux and Android
platforms. Windows users can work around this by using static linking
- see docs/HTTP2_ANDROID.md for the weak symbol registry pattern that
eliminates dynamic library dependencies entirely. If a Windows
contributor wants to implement the attached patch or an alternative
solution, we welcome reopening this issue.
> Circular dependency between engine and http_common libraries
> ------------------------------------------------------------
>
> Key: AXIS2C-1142
> URL: https://issues.apache.org/jira/browse/AXIS2C-1142
> Project: Axis2-C
> Issue Type: Bug
> Components: core/engine, core/transport
> Affects Versions: 1.4.0
> Environment: CentOS 4.6 (linux), GCC 3.4.6/4.2.3
> Reporter: Steve Nairn
> Priority: Minor
> Labels: patch
> Attachments: http_common.patch
>
>
> Following discussion on the Axis2/C dev list, there is a circular dependency
> between libaxis2_engine and libaxis2_http_common.
> The http_common library contains references to a large number of symbols that
> are resolved by the engine library. Unfortunately the engine library contains
> references to axis2_http_accept_record_free and axis2_http_header_free, that
> are resolved by the http_common library. Therefore there is a circular
> dependency between the libraries.
> The circular dependency makes it very difficult to build these libraries on
> platforms that do not allow shared libraries to contain unresolved symbols
> (for example, Windows DLLs).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
