[jira] Commented: (AXIS2C-1040) Use of AXIS2_EXPORT instead of AXIS2_EXTERN in a few places causes errors in static build

["Bill Mitchell (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AXIS2C-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574045#action_12574045 ] 

Bill Mitchell commented on AXIS2C-1040:
---------------------------------------

Looking at the exports from the Windows DLLs, I suspect that the AXIS2_EXPORT declaration is required for the dynamic link.  The likely fix is to ensure that the AXIS2_EXPORT declaration is present only in the non-AXIS2_STATIC_DEPLOY case by including it within the #ifndef.  Such ifndef declarations are already present in http_transport_sender.c; the AXIS2_EXPORT there just lies outside the ifndef.  

> Use of AXIS2_EXPORT instead of AXIS2_EXTERN in a few places causes errors in static build
> -----------------------------------------------------------------------------------------
>
>                 Key: AXIS2C-1040
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-1040
>             Project: Axis2-C
>          Issue Type: Bug
>          Components: util
>            Reporter: Frank Huebbers
>
> I have seen a few places where the typedef AXIS2_EXPORT is used instead of AXIS2_EXTERN. Doing a simple search, I have seen this in the following fiels:
> - axis2_msg_recv.h
> - msg_recv.c
> - raw_xml_in_out_msg_recv.c
> - svr_callback.c
> - mod_addr.c
> - http_transport_sender.c
> - http_receiver.c
> - http_svr_thread.c
> - tcp_transport_sender.c
> - tcp_svr_thread.c
> - tcp_receiver.c
> Note that the definitions are correct in the header files.
> Frank

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org