Ok, well I did figure out the discrepancy between these extensions and previous
extensions that have been built that required setting RTLD_GLOBAL. What I'm
doing for these extensions is instead of building in all of the original C++
code AND the Py++ generated code into the extension, I'm only
On 01/31/2012 12:41 AM, Michael Wild wrote:
On 01/30/2012 07:28 PM, Jim Bosch wrote:
On 01/30/2012 12:11 PM, Michael Wild wrote:
That's what I've been referring to as "auxiliary" functions. If
possible, I'd like to avoid them because I don't fancy writing hundreds
of those... I could live with
On 01/27/2012 06:43 PM, Adam Preble wrote:
I have opted to have my C++ main call an autoexec.py script by default when
compiled to support the interpreter. Ultimately, I will want to run some
Python code w/o user intervention to do it. I have come up with this
somewhat naive implementation:
ht
Hi, everyone!
On my Mac OS X 10.7.2, I had to edit the bootstrap-generated project-config.jam
file so that it contained the following directive:
using python
: 3.2
: /Library/Frameworks/Python.framework/Versions/3.2/bin/python3.2
: /Library/Frameworks/Python.framework/Versions/3.2/inc
On 01/31/2012 05:56 PM, Jim Bosch wrote:
> On 01/31/2012 12:41 AM, Michael Wild wrote:
>> On 01/30/2012 07:28 PM, Jim Bosch wrote:
>>> On 01/30/2012 12:11 PM, Michael Wild wrote:
That's what I've been referring to as "auxiliary" functions. If
possible, I'd like to avoid them because I don
On 01/31/2012 02:52 PM, Michael Wild wrote:
You might be able to address that by having two make_helper functions,
using enable_if/disable_if to select one when the return type is const
and the other when it isn't. The one invoked for const returns would
just call make_function directly to make
