[ 
https://issues.apache.org/jira/browse/THRIFT-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12905512#action_12905512
 ] 

Ivan Murashko commented on THRIFT-705:
--------------------------------------

I also have the same problem when trying to use the thrift with my autoconf 
based solution. I resolved it by removing references to config.h from all 
header files and put them into each cpp ones. May be there is a more better 
solution because the content of the config.h file is for internal usage and 
should not be published in the interface.

BTW: I can put the patch if somebody is interested in it

> Installed C++ header files depend on "config.h" which may have conflicting 
> macros with the (autoconf based) C++ project using Thrift.
> -------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: THRIFT-705
>                 URL: https://issues.apache.org/jira/browse/THRIFT-705
>             Project: Thrift
>          Issue Type: Bug
>          Components: C++ - Library
>         Environment: Any Thrift compatible C++ compiler environment.
>            Reporter: Teemu Koponen
>         Attachments: config-h-patch.diff
>
>
> The public, installed Thrift C++ header files depend on an autoconf generated 
> system specific  'config.h' header file. Unfortunately, having this header 
> file as a part of the library headers is generally troublesome.  For example, 
> see:
> http://sources.redhat.com/autobook/autobook/autobook_96.html
> Attached is a patch that relies on an alternative, simpler approach based on 
> AX_PREFIX_CONFIG_H, which adds a package prefix to both config.h file name 
> and to the macros defined within:
> http://www.nongnu.org/autoconf-archive/ax_prefix_config_h.html
> The resulting thrift-config.h can be installed and included safely from C++ 
> applications having their own config.h.

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

Reply via email to