okay.. just looked closer at this, we hard set libesl as static, which seems strange to me.. not a good reason to do that, other than when we link that static to the individual modules... if what you are trying to do is get a mod you can link to java... try cd libs/esl && make javamod this will make a: libesljni.so
On Mar 22, 2016, at 3:02 PM, Ben Hood <0x6e6562@gmail.com> wrote:
On Mon, Mar 21, 2016 at 5:26 PM, Michael Jerris <mike@jerris.com> wrote:
all you should need is ./configure. The others shouldn't be necessary at all. a .la file is a libtool library file and has nothing to do with if its dynamic or static. The configure args you specified will also produce a dynamic, but none of those are necessary to get that result. --enable-64 is really just used for solaris where the default compiler is 32 bit on 64 bit os.
Many thanks for your response. It's good to know that the --enable-64 flag is only relevant for Solaris.
I did try to answer my own question, but there seems to be some MX DNS issues with the mailing list, so responses from yesterday got rejected.
In the meantime I had created a workaround that I could load via JNA:
g++ -fpic -shared -Wl,-all_load libesl.la -Wl,-noall_load -o libesl.dylib
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org