On Mon, Jul 08, 2024 at 12:17:13PM +0200, Jörg Sonnenberger wrote:
> On Sunday, July 7, 2024 1:19:14?AM GMT+2 Andrew Randrianasulu wrote:
> > Another part of our unportability related to way we use /proc for getting
> > our own executable name/path. Is there more portable way to do so?
>
> The first question is always, why would you want to know that.
If this is to get at the binary resource linked into your executable,
an alternative may be to play with linker scripts and use dlsym(NULL,...)
to find them (if they are loadable and have a symbol marking their start
and end).
not really, as far as I understand code at least it used for internal forking for re-launching same probgar for background rendering:
line 128 at
also in ./cinelerra/mwindow.C for dumping (printing) details about executable.
in guicast/bctrace.C /proc used for dumping shared memory parameters.
in ./cinelerra/indexfile.C /proc/mounts used optionally for getting udf volume id (for bluray creation?)
in ./cinelerra/file.C /proc used for function get_exec_path but it probably unused right now?
in ./cinelerra/main.C it used for automatic program restart
in ./guicast/bcsignals.C procfs used for killing subprocesses (forked early, I guess).
Biggest cpu-arch dependent part in guicast/Makefile
where we set variable BOOTSTRAP for objcopy command used in bootstrap.C
right now file have cases for i386/586, amd64, arm7/8l, aarch64, ppc/ppc64
Anything else will error out while building ...