Re: [anjuta-list] How to recover after crash

[Igor Korot <ikorot01 gmail com>]

Sebastien,

On Sun, Jun 25, 2017 at 3:44 PM, Sébastien Granjoux <seb sfo free fr> wrote:
> Hi,
>
> Le 25/06/2017 à 21:36, Igor Korot a écrit :
> > > Anjuta doesn't build anything, so if it works without Anjuta in should
> > > work
> > > within. You can check what is the build directory by default Anjuta use a
> > > directory named Debug. If you run from the command line in this
> > > directory:
> > >          ../autogen.sh && make && make install
> > > You should get the same thing than in Anjuta.
> >
> >
> > I understand Anjuta doesn't build anything, but something inside the IDE
> > changed
> > and it doesn't work correctly.
> >
> > Is it possible that some stuff inside Anjuta changed and now it tries
> > to build in some other directory?
>
>
> Anjuta keeps almost nothing about your project so that's an idea. Which
> command do you run to build your project? Have you tried the commands above?

In the Terminal I just do:

cd ~/my_proj/Debug && make

In Anjuta I select "Build->Build Project".

> > But then even if it is - how come all subprojects kept all
> > their C++ and linker properties?
>
>
> Because, anjuta doesn't save any project properties.

So what is kept?
Or Anjuta simply reads the Makefiles and wraps them in a GUI
dialogs?

> > How can I do that?
>
>
> Select File->New->Project based on existing source.

I want to do that as the last resort.
Is it possible for you to recreate the issue? Something like:

1. Make Anjuta non-responsive.
2. Try to close it by clicking on "X".
3. Click "Force to close application".
4. After successful closing start the Anjuta.
Try to build the project.

My project contain of 1 binary executable and 12 dynamically linked libraries.
There are some cross-dependencies, but I think just 3 libraries will be enogh.


If Anjuta will be able to build after the "Force to exit" then there
was something wrong
with my system at the time of the crash.

Thank you.

> Regards,
>
> Sébastien