Re: [Banshee-List] [banshee] Allow debugging from MonoDevelop
- From: "Andrés G. Aragoneses" <knocte gmail com>
- To: banshee-list gnome org
- Subject: Re: [Banshee-List] [banshee] Allow debugging from MonoDevelop
- Date: Sun, 14 Feb 2010 14:20:42 +0100
El 14/02/10 09:36, Bertrand Lorentz escribió:
> On Sat, 2010-02-13 at 18:49 -0800, Gabriel Burt wrote:
>> On Sat, Feb 13, 2010 at 2:51 PM, Bertrand Lorentz
>> <blorentz src gnome org> wrote:
>>> commit e16f4e63d8f508c85d9f2cc3ee333a6247b1793d
>>> Author: Bertrand Lorentz <bertrand lorentz gmail com>
>>> Date: Sat Feb 13 13:16:39 2010 +0100
>>>
>>> Allow debugging from MonoDevelop
>>>
>>> Remove all custom commands from all projects options, and disable the
>>> makefile integration for the "Execute" target. This allows MonoDevelop
>>> to do its debugging thing with mdb. Fixes bgo#573731.
>>>
>>> Word of caution : From now on, when starting Banshee from MonoDevelop
>>> with "Run" or "Debug", the parameters are "--debug --uninstalled", so
>>> your default database file will be used. I didn't find a way to pass the
>>> value of the BANSHEE_DEV_OPTIONS env var as a parameter, which is what
>>> "make run" does.
>>
>> I actually have my BANSHEE_DEV_OPTIONS in my .bashrc; maybe we could
>> have Banshee itself look for that env var and add it to the
>> ApplicationContext.CommandLine?
>
> That would be a possibility, but it shouldn't look for
> BANSHEE_DEV_OPTIONS when I'm using Banshee "normally" (ie not testing).
> Maybe add something like a --get-from-env-var command line parameter ?
Or just wrap it in an "#if DEBUG" block?
Andrés
--
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]