I'm on the mono-a11y team, and we have three assemblies in Olive (UIAutomation*.dll). How do I decide if these assemblies should be referenced in the olive.pc file? I'd like to add them there so that, when installed, they appear in MonoDevelop's References dialog. Is this okay? Should I create a new .pc file instead?
There is no problem to include them in olive.pc. They are part of olive. Though note that olive is always a moving target and you might want to move them to somewhere else (probably mcs?) later.
> I'm on the mono-a11y team, and we have three assemblies in Olive > (UIAutomation*.dll). How do I decide if these assemblies should be > referenced in the olive.pc file? I'd like to add them there so that, > when installed, they appear in MonoDevelop's References dialog. Is > this okay? Should I create a new .pc file instead?
> I'm on the mono-a11y team, and we have three assemblies in Olive > (UIAutomation*.dll). How do I decide if these assemblies should be > referenced in the olive.pc file? I'd like to add them there so that, > when installed, they appear in MonoDevelop's References dialog. Is > this okay? Should I create a new .pc file instead?
Create a new .pc file specifically for UI Automation.
>> I'm on the mono-a11y team, and we have three assemblies in Olive >> (UIAutomation*.dll). How do I decide if these assemblies should be >> referenced in the olive.pc file? I'd like to add them there so that, >> when installed, they appear in MonoDevelop's References dialog. Is >> this okay? Should I create a new .pc file instead?
> Create a new .pc file specifically for UI Automation.
Will do, thanks. We also depend on WindowsBase from olive, but that's already in olive.pc so I think we're fine there.
>> I'm on the mono-a11y team, and we have three assemblies in Olive >> (UIAutomation*.dll). How do I decide if these assemblies should be >> referenced in the olive.pc file? I'd like to add them there so that, >> when installed, they appear in MonoDevelop's References dialog. Is >> this okay? Should I create a new .pc file instead?
> Create a new .pc file specifically for UI Automation.
Attached is a patch to add the new .pc file. I'm not entirely sure this was the right way to do it; could somebody please review before I commit?
<sanfordarmstr...@gmail.com> wrote: > On Tue, Jun 17, 2008 at 7:28 AM, Miguel de Icaza
>> Create a new .pc file specifically for UI Automation.
> Attached is a patch to add the new .pc file. I'm not entirely sure > this was the right way to do it; could somebody please review before I > commit?
Please disregard this patch, I'm working on a new one.
<sanfordarmstr...@gmail.com> wrote: > On Tue, Jun 17, 2008 at 10:16 AM, Sandy Armstrong > <sanfordarmstr...@gmail.com> wrote: >> On Tue, Jun 17, 2008 at 7:28 AM, Miguel de Icaza
>>> Create a new .pc file specifically for UI Automation.
>> Attached is a patch to add the new .pc file. I'm not entirely sure >> this was the right way to do it; could somebody please review before I >> commit?
> Please disregard this patch, I'm working on a new one.
Per an earlier discussion with Miguel in IRC, I've attached a new patch which does the following:
* Adds new a11y.make profile for assemblies that will end up in $prefix/lib/mono/a11y * Puts UIAutomation* assemblies in the a11y profile * Deploys mono-uia.pc, which references the UIAutomation* assemblies as well as WindowsBase from the 3.0 profile
Hopefully this is what you were looking for. Please let me know if any changes are required, or if I can just commit.
You do not need a separate profile. All you need is to override in your makefiles the gacutil command to use to install in the right location. This would be too heavy to add
On Wed, Jun 18, 2008 at 12:41 AM, Sandy Armstrong <
sanfordarmstr...@gmail.com> wrote: > On Tue, Jun 17, 2008 at 12:00 PM, Sandy Armstrong > <sanfordarmstr...@gmail.com> wrote: > > On Tue, Jun 17, 2008 at 10:16 AM, Sandy Armstrong > > <sanfordarmstr...@gmail.com> wrote: > >> On Tue, Jun 17, 2008 at 7:28 AM, Miguel de Icaza
> >>> Create a new .pc file specifically for UI Automation.
> >> Attached is a patch to add the new .pc file. I'm not entirely sure > >> this was the right way to do it; could somebody please review before I > >> commit?
> > Please disregard this patch, I'm working on a new one.
> Per an earlier discussion with Miguel in IRC, I've attached a new > patch which does the following:
> * Adds new a11y.make profile for assemblies that will end up in > $prefix/lib/mono/a11y > * Puts UIAutomation* assemblies in the a11y profile > * Deploys mono-uia.pc, which references the UIAutomation* assemblies > as well as WindowsBase from the 3.0 profile
> Hopefully this is what you were looking for. Please let me know if > any changes are required, or if I can just commit.
> You do not need a separate profile. All you need is to override in > your makefiles the gacutil command to use to install in the right > location. This would be too heavy to add
Ah, thanks for clarifying. Here's a new patch. I simply set the LIBRARY_PACKAGE variable in my Makefiles. I also changed it from $prefix/lib/mono/a11y to $prefix/lib/mono/accessibility, which I recall was your original suggestion. I could change it to uiautomation or something like that if you prefer.
<sanfordarmstr...@gmail.com> wrote: > On Wed, Jun 18, 2008 at 8:59 AM, Miguel de Icaza > <miguel.de.ic...@gmail.com> wrote: >> Hello,
>> You do not need a separate profile. All you need is to override in >> your makefiles the gacutil command to use to install in the right >> location. This would be too heavy to add
> Ah, thanks for clarifying. Here's a new patch. I simply set the > LIBRARY_PACKAGE variable in my Makefiles. I also changed it from > $prefix/lib/mono/a11y to $prefix/lib/mono/accessibility, which I > recall was your original suggestion. I could change it to > uiautomation or something like that if you prefer.
Everyone done with their meetings? Anyone have time to review this patch?
> On Wed, Jun 18, 2008 at 9:40 AM, Sandy Armstrong > <sanfordarmstr...@gmail.com> wrote: > > On Wed, Jun 18, 2008 at 8:59 AM, Miguel de Icaza > > <miguel.de.ic...@gmail.com> wrote: > >> Hello,
> >> You do not need a separate profile. All you need is to override in > >> your makefiles the gacutil command to use to install in the right > >> location. This would be too heavy to add
> > Ah, thanks for clarifying. Here's a new patch. I simply set the > > LIBRARY_PACKAGE variable in my Makefiles. I also changed it from > > $prefix/lib/mono/a11y to $prefix/lib/mono/accessibility, which I > > recall was your original suggestion. I could change it to > > uiautomation or something like that if you prefer.
> Everyone done with their meetings? Anyone have time to review this patch?
Miguel de Icaza wrote: > Oops, sorry; I deleted the email and the patch; Can you resend?
> On Wed, Jul 2, 2008 at 9:49 AM, Sandy Armstrong > <sanfordarmstr...@gmail.com <mailto:sanfordarmstr...@gmail.com>> wrote:
> On Wed, Jun 18, 2008 at 9:40 AM, Sandy Armstrong > <sanfordarmstr...@gmail.com <mailto:sanfordarmstr...@gmail.com>> > wrote: > > On Wed, Jun 18, 2008 at 8:59 AM, Miguel de Icaza > > <miguel.de.ic...@gmail.com <mailto:miguel.de.ic...@gmail.com>> > wrote: > >> Hello,
> >> You do not need a separate profile. All you need is to > override in > >> your makefiles the gacutil command to use to install in the right > >> location. This would be too heavy to add
> > Ah, thanks for clarifying. Here's a new patch. I simply set the > > LIBRARY_PACKAGE variable in my Makefiles. I also changed it from > > $prefix/lib/mono/a11y to $prefix/lib/mono/accessibility, which I > > recall was your original suggestion. I could change it to > > uiautomation or something like that if you prefer.
> Everyone done with their meetings? Anyone have time to review > this patch?
