Skip to content

Conversation

@jhunold
Copy link
Contributor

@jhunold jhunold commented Jan 4, 2014

Found while cleaning up my git svn mirror after the conversion. The patch switches Boost.Python to the common BOOST_SYMBOL_* macros from Boost.Config. This includes some minor cleanups for gcc which does not like visibility attributes on forward declarations. Testest with gcc and msvc-9.0

@hotgloupi
Copy link

This patch sounds great !

The only thing I don't know is about exception visibility, I always expose them on windows, and that's why I use in my projects a special macros that expand to correct visibility on any platform but windows.

@stefanseefeld stefanseefeld force-pushed the develop branch 2 times, most recently from 8ccdcff to 3ace4a0 Compare October 8, 2016 17:34
@stefanseefeld stefanseefeld merged commit 0224f54 into boostorg:develop Feb 13, 2017
@jhunold jhunold deleted the visibility branch February 13, 2017 17:08

namespace boost { namespace python
{
struct BOOST_PYTHON_DECL_FORWARD instance_holder;

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is the offending line that is a cause of #131

formiaczek added a commit to formiaczek/python that referenced this pull request Aug 22, 2017
If a global visibility is set to 'hidden', importing modules that define classes without either 'noimport' or 'init' causes 
errors like:
`ImportError: dynamic module does not define init function`

This seems to be due to some, probably unintended changes from boostorg#1.
marv added a commit to marv/python that referenced this pull request Sep 20, 2017
This was properly an oversight when switching to the BOOST_SYMBOL_*
symbols from Boost.Config in commit 0224f54 (see boostorg#1)

Since Boost.Config is already doing the differentiation between
different platforms and compilers we can simplify this bit and just
use BOOST_SYMBOL_EXPORT
stefanseefeld pushed a commit that referenced this pull request Oct 25, 2017
This was properly an oversight when switching to the BOOST_SYMBOL_*
symbols from Boost.Config in commit 0224f54 (see #1)

Since Boost.Config is already doing the differentiation between
different platforms and compilers we can simplify this bit and just
use BOOST_SYMBOL_EXPORT
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants