# Wrapping or pipping a compiled fortran code?

**URL:** <https://discourse.julialang.org/t/wrapping-or-pipping-a-compiled-fortran-code/60300>\
**Category:** New to Julia\
**Tags:** fortran\
**Created:** [April 30, 2021, 11:16am UTC](https://discourse.julialang.org/t/wrapping-or-pipping-a-compiled-fortran-code/60300 "2021-04-30T11:16:25Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![lmiq](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/lmiq/32/18314_2.png) [@lmiq](https://discourse.julialang.org/u/lmiq)\
**Post date:** [April 30, 2021, 9:50pm UTC](https://discourse.julialang.org/t/wrapping-or-pipping-a-compiled-fortran-code/60300/13 "2021-04-30T21:50:55Z")

</div>

I find those instructions hard to understand, particularly to someone without experience with C.

I have once posted one example here: [Calling a Fortran routine from a library which uses LAPACK - #5 by lmiq](https://discourse.julialang.org/t/calling-a-fortran-routine-from-a-library-which-uses-lapack/49124/5) (but I arrived to succeed in those by finding several examples around, not reading the docs).

To do the same with that code, you need first to convert the program into a subroutine, but the way that is structured doesn’t help.

Probably the first thing to ask is how fast you need that to be. Maybe parsing the output is good enough.

---

_[View the full topic](https://discourse.julialang.org/t/wrapping-or-pipping-a-compiled-fortran-code/60300)._
