Colleagues, Sorry for the very lengthy subject line, but I'm seeing unexpected/undesired behavior that I wonder if (a) anyone else has experienced and/or (b) anyone else has a way to prevent.
I am using CMake to drive a command-line call to LyX to build a document from a directory that is different than the LyX file (an "out-of-source" build). The LyX document has relative paths for files included. During the build process, LyX is creating empty directories, in a relative sense, for the included file(s). This is ultimately polluting my source directory. I'm seeing this with both LyX 2.3.2 and 2.3.3 on macOS 10.13 and 10.14. A concrete MWE is attached. In the example, the steps to reproduce are: 1. Untar/zip. 2. Navigate to the `doc` subdirectory. 3. Make a new `build` subdirectory and enter it. 4. Configure using cmake (i.e., `cmake ..`). 5. Build (i.e., `make`). 6. In the `build` directory, there should now be `base_doc.pdf,` as desired. However, in the parent `doc` directory, there will be an empty `include` directory. I presume this is a bug. If that is agreed, I'll file this into the tracker. Whether it is or not, does anyone see a way to prevent this behavior? Thanks, Joel
cmd_line_test.tar.gz
Description: GNU Zip compressed data
