atoms-ufrj / emdee Goto Github PK

i believe we have two macro options

1. touch some global system configs which require sudo:
   e.g. current approach:
   sudo make install
   cp $(LIBDIR)/libemdee.* /usr/local/lib/
   cp $(INCDIR)/emdee.* /usr/local/include/
   ldconfig

2. keep the files locally and instruct the linker of tests and jobs on how to find them at compile time and at run time
   2a) in fortran and c, to find them at compile time we can use -I$(libdir) as a linker option
   2b) to make the executable able to find them at run time we can use something like
   2b_i) $(LINK) -Wl,-rpath,'$$ORIGIN/../../lib1/so'
   i will implement it specifically for our makefile soon

   2b_ii) compile using -static

   2b_iii) in julia, as julia is not compiled/linked we will have to deal with its package management system

   2a_iii_1 ship lib to /home/user/.julia/version/EmDee/lib/libemdee.so
   Libdl.dlopen("/home/user/.julia/version/EmDee/lib/libemdee.so")
   ship wrappers in EmDee.jl so any script.jl can run "using EmDee"
   ship it to to ~/.julia/v0.4/EmDee/src

   2a_iii_2 include in julia source:
   Libdl.dlopen("EmDee-source-folder/lib/libemdee.so")

   ?
   Julia include path for USING MODULE
   abrir pasta dos packages:
   ~/.julia
   colar EmDee.jl em ~/.julia/v0.4/EmDee/src
   ?
   Julia load shared library EmDee.so
   http://docs.julialang.org/en/release-0.4/manual/modules/
   http://docs.julialang.org/en/release-0.4/stdlib/libdl/

   !
   I'm currently trying and will submmit an approach that combines Libdl.dlopen, Libdl.dlsym, and a home made macro from http://docs.julialang.org/en/release-0.5/manual/calling-c-and-fortran-code/

this decision is relevant for both the EmDee library as for the gfortran libraries, both can be linked either statically or dinamically

Obs: is there a reason to make libgfortran statically linked or should i find the right options to make it dinamically linked?