Confused...

Hello all.
I'm still getting "Are you sure you want to debug a program not using the
Debug configuration?". Of course I could just say "Do not show again",
but that defeats the purpose of warnings, doesn't it?

In the Anjuta manual, I finds this:
(http://library.gnome.org/devel/anjuta-manual/stable/build-configure.html.en)

+++++++++++
+ The build directory
+
+ This is the build directory name. In the Default configuration, it is
+ the same directory as the source directory but autotools supports
+ building in a different directory.
+
+ Each configuration must have a different build directory and if one
+ configuration uses the source directory, you cannot have other
+ configurations at the same time. You need to run Build ▸ Remove
+ Configuration on the configuration using the source directory before
+ adding a new configuration.
+++++++++++

So, basically, (I understand) it says: by default (out-of-the-box) it uses
the source directory, and you cannot use the other options, because if
one uses the source directories, the others won't work.



Now, running "Remove configuration" produces an error here:

+ Error: source directory already configured; run "make distclean" there
+ first.

But, the manual for "Remove configuration" tells me:

+ ... choose Build ▸ Remove Configuration. It run make
+ distclean and deletes more files than Clean Project. In other words, it
+ leaves the project as though it has just been extracted from a
+ distribution tarball...

Just to be sure, I tried to run "make distclean" in the source dir, but
the error remains.

I'm confused...

Could it be that the new directories (the ones to build Debug for
example) have to be at the same level as $prefix/src (say $project/debug)?



------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Anjuta-list mailing list
Anjuta-list@...
https://lists.sourceforge.net/lists/listinfo/anjuta-list

[Johannes Schmid-4]

Hi!

> So, basically, (I understand) it says: by default (out-of-the-box) it uses
> the source directory, and you cannot use the other options, because if
> one uses the source directories, the others won't work.

No, that just means you cannot build the Debug configuration in the src/
directory at the same time you use it for the Default configuration. As
the debug configuration is usually build in Debug/ that shouldn't be a
problem.

> Could it be that the new directories (the ones to build Debug for
> example) have to be at the same level as $prefix/src (say $project/debug)?

I think it should be a subdirectory of the project directory. I never
tried to use a different one.

Regards,
Johannes


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Anjuta-list mailing list
Anjuta-list@...
https://lists.sourceforge.net/lists/listinfo/anjuta-list

[Sébastien Granjoux]

Hi John,

John Coppens a écrit :
> I'm still getting "Are you sure you want to debug a program not using the
> Debug configuration?". Of course I could just say "Do not show again",
> but that defeats the purpose of warnings, doesn't it?

Yes.

> So, basically, (I understand) it says: by default (out-of-the-box) it uses
> the source directory, and you cannot use the other options, because if
> one uses the source directories, the others won't work.

I think I have changed the project wizard, so now out-of-the-box, it
should use the Debug configuration. Anyway, the remaining is right, if
you configure your project in the source directory, you cannot configure
it later in another directory.

> Now, running "Remove configuration" produces an error here:
> + Error: source directory already configured; run "make distclean" there
> + first.

You need to run make distclean in the source directory or select the
Default configuration (check that the directory is set to the source
directory) and select remove configuration.

> Just to be sure, I tried to run "make distclean" in the source dir, but
> the error remains.

Which error "source directory already configured" or the debugger warning ?

> Could it be that the new directories (the ones to build Debug for
> example) have to be at the same level as $prefix/src (say $project/debug)?

For each configuration (except the default one), Anjuta creates a
directory in the project directory. So you will have something like

project
    configure.in
    Makefile.am
    ....
    + src
       Makefile.am
       main.c
       ...
    + Debug
       Makefile
       ...
       + src
          Makefile
          ...

So project is the source directory and Debug is the build directory. I
haven't tried to put the build directory outside the source directory.

Regards,

Sébastien

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Anjuta-list mailing list
Anjuta-list@...
https://lists.sourceforge.net/lists/listinfo/anjuta-list

On Tue, 13 Oct 2009 19:35:39 +0200
Sébastien Granjoux <seb.sfo@...> wrote:

> > So, basically, (I understand) it says: by default (out-of-the-box) it
> > uses the source directory, and you cannot use the other options,
> > because if one uses the source directories, the others won't work.
>
> I think I have changed the project wizard, so now out-of-the-box, it
> should use the Debug configuration. Anyway, the remaining is right, if
> you configure your project in the source directory, you cannot
> configure it later in another directory.

What I meant, is that out-of-the-box, there _is_ a configuration
(Default) that conflicts with the others (according to the text).

> > Now, running "Remove configuration" produces an error here:
> > + Error: source directory already configured; run "make distclean"
> > there
> > + first.
>
> You need to run make distclean in the source directory or select the
> Default configuration (check that the directory is set to the source
> directory) and select remove configuration.
> > Just to be sure, I tried to run "make distclean" in the source dir,
> > but the error remains.
>
> Which error "source directory already configured" or the debugger
> warning ?

Sorry, I had made a debug directory under ...project/src/ because this
was easier to get to some data files, each time I restarted my program. I
now moved the debug dir to ...project/debug, and _that_ problem went away.

> > Could it be that the new directories (the ones to build Debug for
> > example) have to be at the same level as $prefix/src (say
> > $project/debug)?
>
> For each configuration (except the default one), Anjuta creates a
> directory in the project directory. So you will have something like
>
> project
>     configure.in
>     Makefile.am
>     ....
>     + src
>        Makefile.am
>        main.c
>        ...
>     + Debug
>        Makefile
>        ...
>        + src
>           Makefile
>           ...

May I suggest to add this to the manual, along with a warning? I believe
most of my problems where caused by putting the Debug directory inside
src.

John

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Anjuta-list mailing list
Anjuta-list@...
https://lists.sourceforge.net/lists/listinfo/anjuta-list

On Tue, 13 Oct 2009 19:27:12 +0200
Johannes Schmid <jhs@...> wrote:

> Hi!
>
> > So, basically, (I understand) it says: by default (out-of-the-box) it
> > uses the source directory, and you cannot use the other options,
> > because if one uses the source directories, the others won't work.
>
> No, that just means you cannot build the Debug configuration in the src/
> directory at the same time you use it for the Default configuration. As
> the debug configuration is usually build in Debug/ that shouldn't be a
> problem.

So, making a Work/ dir alongside Debug/ and Optimized/ would avoid the
necessity to "Remove configuration"?

> > Could it be that the new directories (the ones to build Debug for
> > example) have to be at the same level as $prefix/src (say
> > $project/debug)?
>
> I think it should be a subdirectory of the project directory. I never
> tried to use a different one.

I believe all my problems came from putting the Debug/ inside the src/
dir.

Now I have a problems which I can't seem to find the cause of:

- I can configure (as Debug)
- Build (src) and Build (project) run fine
- Configure project runs ok (with or w/o regenerate)
- I can do a make inside Debug from a terminal window

- BUT, If I start a debug session, I get:

> Building in directory: .../myproject/debug/debug

which fails, probably because of the extra /debug. But I can't find where
the extra debug is added. It's not in the Build directory (only one
debug/), or in the project.

John

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Anjuta-list mailing list
Anjuta-list@...
https://lists.sourceforge.net/lists/listinfo/anjuta-list

[Sébastien Granjoux]

Hi John,

John Coppens a écrit :
> So, making a Work/ dir alongside Debug/ and Optimized/ would avoid the
> necessity to "Remove configuration"?

Yes.

But it is still possible to configure the project in the source
directory, outside Anjuta or even inside by choosing the source
directory as the build directory.

Moreover, building the program inside the source directory is the most
common way to do it. It is possible that some project doesn't support to
be built outside the source directory in a Debug directory.

An important goal of Anjuta is to allow using standard tools, so this
remove configuration has to be supported. Even if I'm agree that it
makes things more difficult.

> I believe all my problems came from putting the Debug/ inside the src/
> dir.

Ok.

> Now I have a problems which I can't seem to find the cause of:
> - I can configure (as Debug)
> - Build (src) and Build (project) run fine
> - Configure project runs ok (with or w/o regenerate)
> - I can do a make inside Debug from a terminal window
> - BUT, If I start a debug session, I get:
>> Building in directory: .../myproject/debug/debug
>
> which fails, probably because of the extra /debug. But I can't find where
> the extra debug is added. It's not in the Build directory (only one
> debug/), or in the project.

I think it comes from the chosen debug executable. It is defined in
Run->Program parameters. You have to select which program you want to
debug. I have tried to use useful default value, but when you change the
configuration, the executable is not the same and this value is not updated.

Regards,

Sébastien

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Anjuta-list mailing list
Anjuta-list@...
https://lists.sourceforge.net/lists/listinfo/anjuta-list

On Tue, 13 Oct 2009 20:50:58 +0200
Sébastien Granjoux <seb.sfo@...> wrote:

> > which fails, probably because of the extra /debug. But I can't find
> > where the extra debug is added. It's not in the Build directory (only
> > one debug/), or in the project.
>
> I think it comes from the chosen debug executable. It is defined in
> Run->Program parameters. You have to select which program you want to
> debug. I have tried to use useful default value, but when you change
> the configuration, the executable is not the same and this value is not
> updated.

Yes! Thanks Sébastien.

Still have the Warning though. This part of the debug-manager code is
strange:
                /* Check if debug configuration is used */
                cfg_list = ianjuta_builder_list_configuration (builder, NULL);
                found = g_list_find_custom(cfg_list, IANJUTA_BUILDER_CONFIGURATION_DEBUG, (GCompareFunc)strcmp);
                if (found != NULL)
                {
                        if (ianjuta_builder_get_uri_configuration (builder, target, NULL) != (const gchar *)found)
                        {                                                                                        
                                if (!show_check_debug_dialog (this)) return FALSE;                                
                        }
                }

There is a cast (const gchar *)found ... is this correct? found is a GList. Shouldn't this be found->data ?

John

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Anjuta-list mailing list
Anjuta-list@...
https://lists.sourceforge.net/lists/listinfo/anjuta-list

On Tue, 13 Oct 2009 22:30:29 +0200
Sébastien Granjoux <seb.sfo@...> wrote:

> Yes, that's strange. Have you tried to change the code and see if it
> works better ?
>

Just changing that line does not seem to make any difference. I am
compiling a -O0 version to debug that part of the code.

John

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Anjuta-list mailing list
Anjuta-list@...
https://lists.sourceforge.net/lists/listinfo/anjuta-list

On Tue, 13 Oct 2009 18:28:18 -0300
John Coppens <john@...> wrote:

> Just changing that line does not seem to make any difference. I am
> compiling a -O0 version to debug that part of the code.

Sorry - this seems to be stretching my capabilities. And I don't know
enough of how the plugins work either. Very little of what I see in the
debugger makes sense...

I'm afraid I can't dedicate more time today. Will try again when I can.

John

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Anjuta-list mailing list
Anjuta-list@...
https://lists.sourceforge.net/lists/listinfo/anjuta-list

[Sébastien Granjoux]

Hi John,

John Coppens a écrit :
> Sorry - this seems to be stretching my capabilities. And I don't know
> enough of how the plugins work either. Very little of what I see in the
> debugger makes sense...
> I'm afraid I can't dedicate more time today. Will try again when I can.

Ok, it doesn't matter than much. I need to look at this anyway.

Regards,

Sébastien

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Anjuta-list mailing list
Anjuta-list@...
https://lists.sourceforge.net/lists/listinfo/anjuta-list

[Sébastien Granjoux]

Hi John,

John Coppens a écrit :
> I'm afraid I can't dedicate more time today. Will try again when I can.

I have looked at that part of the code. It seems ok after fixing the
problem with data field. It doesn't work here because I access my
project using a symbolic links (my projects are in /home/seb/Projects
which is a symbolic link to /mnt/prog). The project root directory is
/mnt/prog/Project/foo while the target is named /home/seb/Projects/foo.
But I think such case is quite uncommon and it doesn't bother me enough
to fix it for the moment.

Else, if you are not in this case it should work. The corresponding code
with more comments is:

/* Return a GList of non translated configuration name normally
  * NULL, Debug, Profiling, Optimized
  * The name should be used as id only and are allocated inside
  * the builder plugin, they shouldn't be freed */
cfg_list = ianjuta_builder_list_configuration (builder, NULL);

/* Look for a configuration named Debug, which is supposed to
  * be the debugging configuration. Checking the configuration
  * name */
found = g_list_find_custom(cfg_list,
IANJUTA_BUILDER_CONFIGURATION_DEBUG, (GCompareFunc)strcmp);

if (found != NULL)
{
        /* Try to find in which build tree is the given target. For
         * doing this, it enumerates all possible configuration and
    * check if the start of the URI correspond to the build
         * directory of the configuration, return the untranslated
         * name. It fails here for me, because the target URI use
         * the symbolic name while the project URI use the real
         * name. */
         if (ianjuta_builder_get_uri_configuration (builder, target,
NULL) != (const gchar *)found->data)
         {
                /* Show the warning dialog */
          if (!show_check_debug_dialog (this)) return FALSE;
        }
}

Best Regards,

Sébastien

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Anjuta-list mailing list
Anjuta-list@...
https://lists.sourceforge.net/lists/listinfo/anjuta-list

On Wed, 14 Oct 2009 21:17:55 +0200
Sébastien Granjoux <seb.sfo@...> wrote:

> Else, if you are not in this case it should work. The corresponding
> code with more comments is:

Thanks for adding the comments, Sébastien. After today, I will have a
little time to look more.

The debug configuration in my case _is_ called 'Debug', so that should
work. I guess it's the next line that fails:

if (ianjuta_builder_get_uri_configuration (builder, target,
NULL) != (const gchar *)found->data)

In my case, I don't use any symlinks, so I have to look deeper.

John

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Anjuta-list mailing list
Anjuta-list@...
https://lists.sourceforge.net/lists/listinfo/anjuta-list

On Wed, 14 Oct 2009 21:17:55 +0200
Sébastien Granjoux <seb.sfo@...> wrote:

>          if (ianjuta_builder_get_uri_configuration (builder, target,
> NULL) != (const gchar *)found->data)

Wow... This is comparing the (char *), not the actual string. Shouldn't
this be a strcmp? Will check that later.

John

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Anjuta-list mailing list
Anjuta-list@...
https://lists.sourceforge.net/lists/listinfo/anjuta-list

[Sébastien Granjoux]

Hi John,

John Coppens a écrit :
>>          if (ianjuta_builder_get_uri_configuration (builder, target,
>> NULL) != (const gchar *)found->data)
>
> Wow... This is comparing the (char *), not the actual string. Shouldn't
> this be a strcmp? Will check that later.

No, it's normal. The configuration name is used as an id here. It is a
string allocated inside the builder plugin will represent the configuration.

Regards,

Sébastien

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Anjuta-list mailing list
Anjuta-list@...
https://lists.sourceforge.net/lists/listinfo/anjuta-list

[Sébastien Granjoux]

Hi John,

John Coppens a écrit :
> Wow... This is comparing the (char *), not the actual string. Shouldn't
> this be a strcmp? Will check that later.

I have checked again this piece of code and I have found another error.
I think it should work fine now. I have committed the fix in both the
development and and the gnome 2.28 branch. Could you check that it's
working now ?

Regards,

Sébastien

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Anjuta-list mailing list
Anjuta-list@...
https://lists.sourceforge.net/lists/listinfo/anjuta-list

On Sun, 18 Oct 2009 15:55:46 +0200
Sébastien Granjoux <seb.sfo@...> wrote:

> > Wow... This is comparing the (char *), not the actual string.
> > Shouldn't this be a strcmp? Will check that later.
>
> I have checked again this piece of code and I have found another error.
> I think it should work fine now. I have committed the fix in both the
> development and and the gnome 2.28 branch. Could you check that it's
> working now ?

I'm downloading now.

Thanks,
John

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Anjuta-list mailing list
Anjuta-list@...
https://lists.sourceforge.net/lists/listinfo/anjuta-list

On Sun, 18 Oct 2009 15:55:46 +0200
Sébastien Granjoux <seb.sfo@...> wrote:

> Hi John,
>
> John Coppens a écrit :
> > Wow... This is comparing the (char *), not the actual string.
> > Shouldn't this be a strcmp? Will check that later.
>
> I have checked again this piece of code and I have found another error.
> I think it should work fine now. I have committed the fix in both the
> development and and the gnome 2.28 branch. Could you check that it's
> working now ?

YES! This is the first time ever I could start a debug session without
first closing the warning window.

On the other hand, if I select 'Default', clean, configure and recompile,
the warning doesn't appear either when I start a debug session. That
doesn't seem right, does it? (I checked, the -O0 version doesn't exist
anymore)

Thanks!
John

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Anjuta-list mailing list
Anjuta-list@...
https://lists.sourceforge.net/lists/listinfo/anjuta-list

[Sébastien Granjoux]

Hi John,

John Coppens a écrit :
> On the other hand, if I select 'Default', clean, configure and recompile,
> the warning doesn't appear either when I start a debug session. That
> doesn't seem right, does it? (I checked, the -O0 version doesn't exist
> anymore)

I think it is normal. You debug the program which is selected in
Run->Program parameter.

By default this is set with the first target and saved with all your
configuration settings. But it means that if afterward, you change the
configuration without changing this value, you will still debug the
program of your first configuration.

Regards,

Sébastien

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Anjuta-list mailing list
Anjuta-list@...
https://lists.sourceforge.net/lists/listinfo/anjuta-list

On Mon, 19 Oct 2009 19:15:33 +0200
Sébastien Granjoux <seb.sfo@...> wrote:

> I think it is normal. You debug the program which is selected in
> Run->Program parameter.
>
> By default this is set with the first target and saved with all your
> configuration settings. But it means that if afterward, you change the
> configuration without changing this value, you will still debug the
> program of your first configuration.

Ok... That makes sense. Though the entire Debug/Default switching feels a
little uncomfortable. Why not have a completely separate setup for each
of the modes? (separate Run file definition, etc). That way, when clicking
the run button would run the debug version in Debug mode, etc. Also, the
compile button would compile the correct version, and there would be no
need for separate 'Execute' and 'Run debug' options in the menu. And
there would be no doubt about which version is running.

That's just an opinion! I'm glad the warning disappeared...

Thanks,
John

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Anjuta-list mailing list
Anjuta-list@...
https://lists.sourceforge.net/lists/listinfo/anjuta-list

[Sébastien Granjoux]

Hi John,

John Coppens a écrit :
> Ok... That makes sense. Though the entire Debug/Default switching feels a
> little uncomfortable. Why not have a completely separate setup for each
> of the modes?

Because, both functions are done in different parts of Anjuta, so it's
easier to implement it like this.


> (separate Run file definition, etc). That way, when clicking
> the run button would run the debug version in Debug mode, etc.

This is possible but it needs additional code.


> Also, the compile button would compile the correct version,

Normally, the compile button should always compile the selected
configuration, else it is a bug.


> and there would be no
> need for separate 'Execute' and 'Run debug' options in the menu.

You mean that if you select the Debug version, Execute should run the
program with the debugger ?

I have thought about this. But sometimes it is useful to debug the non
debug version, in case you have a bug with doesn't appear in the debug
version. Moreover the Debug/Non Debug check is not perfect, by example
you cannot have 2 debug versions, so it can be useful to debug a "non
Debug" (for Anjuta) version.

Anyway, I think it's probably better to support easily the most common
cases even if a few uncommon cases are dropped. I'm not against changes
here.

I'm trying to do something, I know it can be improved, in order to get
some feedback. If I don't get any, it's probably not perfect but not
used very often neither so I could probably spend my time on something
else. If I get some return, it is useful to improve.


> That's just an opinion! I'm glad the warning disappeared...

Thanks, we are interested by your opinion. Anjuta is a free software, it
is living due to the contribution of everybody and it is not only code,
bug reports, new design ideas or documentations are important too.

Regards,

Sébastien

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Anjuta-list mailing list
Anjuta-list@...
https://lists.sourceforge.net/lists/listinfo/anjuta-list