building shared library from D code to import into cython

[Laeeth Isharc via Digitalmars-d-learn]

Thanks for this.

I am aware of pyd and will take a look at source/build process.

Any thoughts on speed in 2014  of pyd vs using cython to talk to 
D directly via C/C++ interface?  I saw this old coment here:

prabhuramachandran.blogspot.co.uk/2008/09/python-vs-cython-vs-d-pyd-vs-c-swig

" predict that the D version's relative slowness might have 
something to do with Pyd's somewhat awful handling of arrays (at 
least in part). More low-level and verbose, but possibly faster 
code could be written to compensate for this if this is indeed 
the problem. However, this is not a very attractive solution. 
(Optimally, Pyd should be capable of directly pointing D arrays 
at numpy arrays, but this is not actually implemented.)"


On Friday, 10 October 2014 at 02:19:17 UTC, Ellery Newcomer wrote:
> On Wednesday, 8 October 2014 at 00:25:57 UTC, Laeeth Isharc 
> wrote:
>> Hi.
>>
>> Thanks for the quick response.
>>
>> The -defaultlib was left around from trying all kinds of 
>> combinations of dmd and gcc.  I am not used to gcc, and it 
>> will take me some time to become properly acquainted with all 
>> the options.
>>
>
> I managed to get it to compile with default dmd rpm:
>
> https://github.com/ariovistus/cythonic_d
>
> fedora 20, x86_64
>
> Are you aware of pyd? (https://bitbucket.org/ariovistus/pyd)
>
> It knows how to build shared libraries, so I recommend you play 
> with it, if only to watch how it does that. Biggest gotcha is 
> starting up druntime.