Hi >> init_libapl(argv[0],0); >> >> with or without init gives >> >> Executable ./APs/APserver not found.
> Yes. APserver is a helper binary for old-style shared APL variables (⎕SVO and > friends). The > APserver is forked by APL, but APL cannot know where the APServer binary is > located in the > file system. > APL then assumes that the APserver is located either in the same directory as > itself, or in > a subdir called APs of that directory. we have been working with libapl and not apl > You can probably fix this in a number of ways: > 1. set UserPreferences::uprefs.user_do_svars and system_do_svars to false but in libapl.cc it already has uprefs.user_do_svars = false; uprefs.system_do_svars = false; > 3. Install "normal (non-libapl) APL which should also install APserver in the > right place. i have /usr/local/bin/APserver installed in the 'right place' (from compiling apl and make install) but it doesn't find it (strace shows libapl only looking for APserver in ./APs/APserver) not in /usr/local/bin/ having ./APs/APserver works but then i would have to have it in all dirs i want to work in which isn't a good solution since i want APserver enabled in apl but disabled in libapl my solution is to have 2 preferences so i had to edit the UserPreferences.cc preferences locations and hard code the different location for the apl and libaple preference locations and have for libapl in it's preference # SharedVars Enabled (default) SharedVars Disabled and have for apl in it's preference SharedVars Enabled (defaul⎕t) # SharedVars Disabled ---
