31
Applications / Re: LarsenCommander - new test version
« on: June 08, 2023, 11:19:04 am »Thank you Andi.Yes I was confused by this more than once too. There's included the lcmd_text.cmd (and te.cmd) which calls
I updated my local svn and built it. Thought I had a problem with the executable at first, I tried to test the built lcmd.exe in the directory it was built in and it threw errors but I figured out it was reading the lcmd.rc for building it and the executable needs its own lcmd.rc file. Once I worked that out, it seems to be working well.
Code: [Select]
start lcmd.exe -rcFile ..\..\lcmd.rc -rcSearchPath ..\..\src\glib;..\.. -iniFile lcmd.ini -logFilter test -logFile lcmd.log %1 %2 %3 ...
Quote
One thing that I would like I would like to see (maybe I can work it out) is to have lcmd.exe look for gl16os2.dll in its own directory first before looking at libpath, this would allow it to run without gl16os2.dll having to be in libpath.I've ';.;' in libpath after the %unixroot% directories.
Code: [Select]
LIBPATH=p:\usr\local\lib;p:\usr\lib;p:\dll;.;P:\.....
So that's no problem for me. Isn't that the usual setup? I mean having ;.; in the libpath (best at the end or after unixroot dirs. Isn't it the standard behavior for OS/2 programs to search their dlls in libpath? Or start it by an object set to run in the programs directory?Are you asking for some 'special' code in LCMD which loads the dll from the programs directory regardless of libpath setting? Are there some example programs for such?