https://bugs.kde.org/show_bug.cgi?id=482983
--- Comment #10 from frmdstryr <frmdst...@protonmail.com> ---
(In reply to frmdstryr from comment #9)
> (In reply to frmdstryr from comment #8)
> > (In reply to Igor Kushnir from comment #7)
> > > I cannot reproduce the infinite loop when I add a bogus dependency to the
> > > simple meson project created from a KDevelop template
> > > (Standard=>Terminal=>Meson C++):
> > > ```
> > > + bb=dependency('missingd', version:'>=5.0')
> > > executable('kdev-meson-cpp-test-project',
> > > 'main.cpp',
> > > include_directories : incdir
> > > + , dependencies : bb
> > > ```
> > >
> > > The configuration job fails once and is not restarted:
> > > ```
> > > Run-time dependency missingd found: NO (tried pkgconfig and cmake)
> > >
> > > meson.build:15:3: ERROR: Dependency "missingd" not found, tried pkgconfig
> > > and cmake
> > >
> > > A full log can be found at
> > > /path/to/kdev-meson-cpp-test-project/build/meson-logs/meson-log.txt
> > > *** Failure: Exit code 1 ***
> > > ```
> > >
> > > Is some additional configuration of the project or KDevelop needed?
> >
> > Does the build/meson-info/meson-info.json file exist? It occurred for a
> > project (https://github.com/horizon-eda/horizon) that was already imported
> > and built but then I updated a library version that meson could not find.
>
> I also cannot reproduce with the template project, let me see what else it
> required for this to happen.
Ok, it was more complicated to reproduce:
1. Create the project using the meson template
2. Build the project
3. Add a line in meson.build to introduce an error like a non-existent library
or missing version
4. Run prune
5. Run build or configure again and the loop should start
There may be an better/easier way to fix it since it seems like a race
condition because there is a watch on create and dirty it so the job appears to
be running twice in parallel.
--
You are receiving this mail because:
You are watching all bug changes.
