Going Native with FFI

Slides of my Talk given at RubyConf Colombia 2019

Transcript

1. GOING NATIVE WITH FFI Juan C. Ruiz
2. ❏ Former software engineer @ MagmaLabs ❏ Remote work advocate ❏ RubyMe Q2 mentor ❏ I ❤ Open source @JuanCrg90
3. @JuanCrg90 Heroes' Causeway Arch Leon Guanajuato Photo By @marianozka
4. @JuanCrg90
5. @JuanCrg90
6. What are the options that we have to manage native code on Ruby? @JuanCrg90
7. MKMF @JuanCrg90
8. @JuanCrg90 mkmf.rb is used by Ruby C extensions to generate a Makefile which will correctly compile and link the C extension to Ruby and a third-party library.
9. library.h library.c @JuanCrg90
10. my_ruby_ext.c @JuanCrg90
11. extconf.rb @JuanCrg90
12. @JuanCrg90
13. @JuanCrg90
14. Pros: - We can use C functions in our Ruby Code - We take advantage of the existing ruby.h library to create the extension Cons: - We need to add extra C code to create the bindings - This solution only works in MRI @JuanCrg90
15. FFI @JuanCrg90
16. A foreign function interface (FFI) is a mechanism by which a program written in one programming language can call routines or make use of services written in another. @JuanCrg90
17. @JuanCrg90
18. Pros: - We don’t need to add additional C code - An FFI extension is multi-platform and multi-implementation Cons: - Complex macros are difficult to maintain - Same for callback functions @JuanCrg90
19. PGM IMAGES @JuanCrg90
20. @JuanCrg90
21. @JuanCrg90
22. @JuanCrg90
23. @JuanCrg90
24. @JuanCrg90
25. @JuanCrg90
26. @JuanCrg90
27. @JuanCrg90
28. @JuanCrg90
29. @JuanCrg90
30. @JuanCrg90
31. @JuanCrg90
32. Conclusion @JuanCrg90
33. - https://github.com/JuanCrg90/my_ruby_ext - https://github.com/JuanCrg90/pgm_ffi @JuanCrg90
34. THANKS @JuanCrg90