On Thursday, 2 May 2019 17:28:33 CEST dt-l...@stefan-klinger.de wrote:
> Florian Hühn (2019-May-02, excerpt):
> > If you rerun
> > cmake --build './build' --target install -- -j "$(nproc)"
>
> ok. But it is necessary to install, right?
>
> > Just two thoughts about the isolation issue: Maybe consider setting
> > LD_LIBRARY_PATH as well to reduce your chances of accidentially mixing up
> > the *.so's with your productive version.
>
> How would I set this up? Is it just
>
> export LD_LIBRARY_PATH="${prefix}/lib64"
> "${prefix}/bin/darktable" --configdir "${tmpCfg}" --cachedir
> "${tmpCache}"
> > (Personally I use a dedicated VM for
> > development, so take my suggestens as ideas, not as tested procedure.)
>
> That would be overkill (meaning: I'm too lazy to go through all that
> hassle), I'd rather not do this at all.
Normally you can run applications out of the build dir from cmake, however
darktable is a bit different because it loads a lot of modules using dlopen().
The path is normally the one of system installation dir.
It would be possible to support that, if you put the bin and modules in
specific dirs, write the build dir to a config.h and then change the functions
looking for the modules to first check the build dir and then the system dir.
We could support this for e.g. debug builds.
I've worked on that some time ago but didn't have time to finish it.
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
