Hi Peter,
no, the make all target builds libapl if ./configure'd
to do so:
1. ./configure
--with-libapl
2. make all
3. sudo make install
Step 3. is kind of optional: in copies the libraries to the
installati
Hi Dirk:
Please tell me what OS you were using?
thanks….
Peter
> On May 20, 2018, at 4:59 PM, Dirk Laurie wrote:
> I did this three years ago, using SVN 570 of GNU APL. In an ideal
> world, I would have checked after every SVN update that my application
> still works. In the real world, I have
Yes thanks for your patience Jürgen —
I do understand the procedure and the steps you outlined.
Have been through much of the autotools manuals as well as libtool.
There’s something I do not yet fully understand but I will persevere.
I want to make a very trivial case to see if my hypothesis is c
Hi Peter,
a simple C program, say libapl_test.c would be this:
#include
"libapl.h"
int
main(int argc, char * argv[])
{
init_libapl(argv[0], 0);
return apl_exec("⎕←2 3⍴⍳6");
}
Hi Jürgen:
Well that trivial program confirms my hypothesis which is that I am the first
person to try using libapl on macOS.
I have been doing similar things to your program using both the command line
(Terminal)
and also within Xcode (Apple’s GUI Developer tool). From my experiments I had
co
Hi Peter,
I don't know what a MH_BUNDLE vs. a MH_DYLIB is but meybe this
helps:
https://github.com/yallop/ocaml-ctypes-inverted-stubs-example/issues/4
/// Jürgen
On 06/13/2018 09:26 PM, Peter Teeson
wrote:
You need a dylib to link against at compile time.
Passing `-dynamiclib` to the compiler should to the trick to generate a dylib.
We need something like:
g++ -dynamiclib -o libapl.dylib all_the_o_files.o ...
A bundle is what a so file is, which in general is generated by the compiler
when `-bu
