Am Mo., 25. März 2019 um 13:12 Uhr schrieb Kornel Benko <kor...@lyx.org>:
> > I think we are talking different things. My point is this. If I open a > > template (or another doc) from the build directory (e.g., > > ~/lyx/lyx-devel/lib/doc/), > > Sorry, but this is the source directory. > An the build directory (with autotools). Anyways, I oriented the naming of buildlyxdir at the naming of build_support() in Package.h. > > all paths should be resolved as pointing to this > > directory, even if I have an installed version of the docs in the system > > directory, and _notwithstanding_ whether I opened this file with a lyx > > binary from the build directory, the installed one (or even another > version > > of lyx. as long as the files can be opened). > > If you want to edit the source, you could set the system dir from the > command > line to point there. (for instance: lyx -sysdir ~/lyx/lyx-devel/lib) > Why should I need to have to do this? > > Consider I have made changes in the build directory, > > I NEVER make changes to the build ( == generated) directory. > Never using build-in-source. > I am talking about my autotools settings here. > > including the addition > > of new files which are not yet added to the installation. If I open this > > document with /usr/bin/lyx, I don't expect the paths to be resolved > towards > > the system directory. > > As mentioned above, you could set sysdir from the command line. > As mentioned above: Why should I need to have to do this? Jürgen
