On 27 July 2012 11:47, Chris Sutcliffe wrote:
> On 27 July 2012 09:20, Chris Sutcliffe wrote:
>> On 27 July 2012 08:32, Chris Sutcliffe wrote:
>>> I managed to get it to work. I had to modify config.mk to include the
>>> actual python dlls to load dynamically (it was generated with an empty
>>> string). As time permits I'll look in to patching configure.in /
>>> configure to pick up the dll names correctly for Cygwin.
>>
>> I'm a little stumped how python_INSTSONAME is getting, can someone
>> please provide some insight?
>>
>> Looking in the /auto directory I see:
>>
>> $ grep python_INSTSONAME *
>> configure: @echo "python_INSTSONAME='$(INSTSONAME)'"
>> configure: if (no_rtl_global_needed_for("${python_INSTSONAME}",
>> "${vi_cv_path_python_pfx}"))
>> configure: PYTHON_CFLAGS="$PYTHON_CFLAGS
>> -DDYNAMIC_PYTHON_DLL=\\\"${python_INSTSONAME}\\\""
>> configure: PYTHON_CFLAGS="$PYTHON_CFLAGS
>> -DDYNAMIC_PYTHON_DLL=\\\"${python_INSTSONAME}\\\""
>>
>> is the idea that python_INSTSONAME is passed to configure?
>
> That works, but it appends a '.a' to the end of the DLL name, which is
> incorrect. Not sure where the '.a' magic is occurring in configure.
I figured out that it's pulling the import libraries (i.e.
libpython2.6.dll.a and libpython3.2m.dll.a) from the python config
dirs. How do I instruct configure to grab libpython2.6.dll and
libpython3.2m.dll from the bin directory? I can hand craft config.mk
after the fact, but would like to figure out how to get configure to
behave.
Thanks,
Chris
--
Chris Sutcliffe
http://emergedesktop.org
http://www.google.com/profiles/ir0nh34d
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
No comments:
Post a Comment