> On Aug 7, 2019, at 13:05, Richard Kimberly Heck <[email protected]> wrote:
> 
>> On 8/4/19 11:25 AM, Kornel Benko wrote:
>> Am Sonntag, 4. August 2019, 07:40:48 CEST schrieb Joel Kulesza:
>>> On Sun, Aug 4, 2019 at 1:47 AM Kornel Benko <[email protected]> wrote:
>>> 
>>>> Am Sonntag, 4. August 2019, 09:34:53 CEST schrieb Kornel Benko:
>>>> 
>>>>> I don't see it here.
>>>>> 1.) What is your cmake version? (my is 'cmake version
>>>> 3.15.20190726-g8ce18')
>>>> 
>>> 3.15.1
>>> 
>>> 
>>>>> 2.) What is the path of this dir?
>>>>>      Searching for include in the build gives here nothing.
>>>>>      $ find . -name include
>>> I've attached two logs.  The first (cmake_use.txt) is me using cmake.  I'm
>>> not passing any parameters.  Furthermore, this isn't a cmake issue but a
>>> LyX issue.  The second log shows me building directly with LyX and without
>>> cmake altogether.  However, in both cases, I get an empty `include`
>>> directory (shown with `ls -alR`).
>>> 
>>> Please read "cmake_use.txt" first, the other log is a continuation of it.
>>> 
>>> 
>>>> Retested with your CMakeLists.txt I get
>>>>        $ cmake ..
>>>>        $ make
>>>>        $ ls -l
>>>> 
>>> Look one directory higher—what do you see?
>> I see it too now.
>> If using '-dbg files' param for lyx, lyx shows:
>>    support/FileName.cpp (732): creating path 
>> '/usr2/kornel/tmp/doc1/cmd_line_test/doc/include'.
>> This path is created because lyx searches first this path for the file 
>> 'inclusion.tex'.
>> 
>> I confess, it is not sooo nice behaviour.
> 
> It does find the included file, at least, right?

Yes. It finds the file and produces a correct PDF. 

> Certainly LyX should not create this directory, though.

Thanks for confirming. With your and Kornel’s feedback, I’ll enter an issue in 
the tracker (when I return from travel). I took a quick look at this based on 
Kornel’s debugging insight, and the fix isn’t obvious (it is further up the 
call stack).  I’ll take a deeper look, but if an expert has any tips I’m happy 
to pursue them. 

Thanks,

Joel

Reply via email to