On Tuesday, 22 October 2019 at 07:23:46 UTC, Daniel Kozak wrote:
On Tue, Oct 22, 2019 at 8:00 AM Prokop Hapala via
Digitalmars-d-learn <digitalmars-d-learn@puremagic.com> wrote:
I'm examining the possibility to move from Python+C/C++ to D or
Python+D. I read
(https://wiki.dlang.org/Programming_in_D_for_Python_Programmers)
and
(https://jackstouffer.com/blog/nd_slice.html), where is
mentioned
PyD, Mir-algorithm, all seems very promising. But I did not
test
it yet.
>...
You should try to use https://github.com/BindBC/bindbc-opengl
and
https://github.com/BindBC/bindbc-sdl. There seems to be an
issue with
derelict packages (mainly with the gl3 one)
And as far as I know derelict should be replaced by bindbc
anyway in future.
And if you plan to have *.so libs you should add "targetType" :
"dynamicLibrary", to you dub.json
OK, thanks. That is useful to know. But just to not turn the
topic elsewhere I should make clear that:
1) I'm not speaking about OpenGL and SDL specifically (that was
just small example which I tried first)
2) I'm more concerned about how to D compiler links dependencies
when it compiles simple .d program (with lot of dependencies).
I think if I can make it link everything dynamically, It would
considerably reduce both size of binary target (whether it is
executable or .so) and compilation speed (since it would not
re-compile dependencies).
What I want is to recompile and run quite large programs/projects
composed composed of many little sub-programs/sub-libraries from
Python+D in fast cycles (<< 1 second), because that would make
debugging workflow much more pleasant and efficient (in
comparison to Python+C/C++ or Julia).
