On Wed, Aug 1, 2012 at 9:41 AM, Corinna Vinschen wrote:
> I didn't even know there *is* a developers list.
>
> If you look on http://mingw-w64.sourceforge.net/, under the link "Public
> Mailing List:, there's only a pointer to the mingw-w64-public list. If
> you look on http://sourceforge.net/pro
On Wed, Aug 1, 2012 at 3:51 PM, Ozkan Sezer wrote:
>
>> you look on http://sourceforge.net/projects/mingw-w64/, under the
>> "Mailing Lists" link, there are three lists only, mingw-w64-documentation,
>> mingw-w64-ironcrate and mingw-w64-public. No trace of a developers list.
>>
>
> I think it is v
Hi Corinnna,
patch looks ok to me. See if Jacek have any objections (I wouldn't assume so).
Thanks,
Kai
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat lands
On 8/1/12, Corinna Vinschen wrote:
> On Aug 1 17:26, Ruben Van Boxem wrote:
>> Hi,
>>
>> I don't want to sound cranky or anything, but I noticed a lot of strictly
>> development emails on Cygwin work by Corinna posted to mingw-w64-public.
>>
>> I'm sure it's not strictly off-topic, but there is
>
On Aug 1 17:26, Ruben Van Boxem wrote:
> Hi,
>
> I don't want to sound cranky or anything, but I noticed a lot of strictly
> development emails on Cygwin work by Corinna posted to mingw-w64-public.
>
> I'm sure it's not strictly off-topic, but there is mingw-w64-developer(s?),
> which seems more
2012/8/1 Kai Tietz
> Hi Ruben,
>
> 2012/8/1 Ruben Van Boxem :
> > Hi,
> >
> > I don't want to sound cranky or anything, but I noticed a lot of strictly
> > development emails on Cygwin work by Corinna posted to mingw-w64-public.
> >
> > I'm sure it's not strictly off-topic, but there is
> mingw-w
Hi Ruben,
2012/8/1 Ruben Van Boxem :
> Hi,
>
> I don't want to sound cranky or anything, but I noticed a lot of strictly
> development emails on Cygwin work by Corinna posted to mingw-w64-public.
>
> I'm sure it's not strictly off-topic, but there is mingw-w64-developer(s?),
> which seems more sui
Hi,
I don't want to sound cranky or anything, but I noticed a lot of strictly
development emails on Cygwin work by Corinna posted to mingw-w64-public.
I'm sure it's not strictly off-topic, but there is mingw-w64-developer(s?),
which seems more suited and keeps my inbox clean from strict
patch->ok
Hi,
I just found that xenroll.h also defines the BSTR_xxx and VARIANT_xxx
functions using unsigned long as type, just like a couple of the just
patched IDL files. The below patch aligns the usage of ULONG in xenroll.h
with the IDL files.
Thanks,
Corinna
* xenroll.h (BSTR_UserSize): Us
On 08/01/12 15:49, Corinna Vinschen wrote:
> On Aug 1 15:27, Jacek Caban wrote:
>> Hi Corinna,
>>
>> On 08/01/12 14:57, Corinna Vinschen wrote:
>>> Hi,
>>>
>>> per our discussion in the previous thread, here's a patch which replaces
>>> all long and unsigned long with LONG and ULONG in .idl files
On Aug 1 15:27, Jacek Caban wrote:
> Hi Corinna,
>
> On 08/01/12 14:57, Corinna Vinschen wrote:
> > Hi,
> >
> > per our discussion in the previous thread, here's a patch which replaces
> > all long and unsigned long with LONG and ULONG in .idl files and their
> > dependent .h files. Hope that's
Hi Corinna,
On 08/01/12 14:57, Corinna Vinschen wrote:
> Hi,
>
> per our discussion in the previous thread, here's a patch which replaces
> all long and unsigned long with LONG and ULONG in .idl files and their
> dependent .h files. Hope that's ok.
All changes inside cpp_quotes are OK. Places ou
Greetings. I develop computer forensic tools using mingw64.
It's very important that these tools be statically linked.
Would it be possible for the mingw32-libgnurx.noarch and the
mingw64-libgnurx.noarch be expanded to include statically linked versions in
addition to the DLLs?
Thanks,
Sims
2012/8/1 Jacek Caban :
> On 08/01/12 12:22, Corinna Vinschen wrote:
>> On Aug 1 11:54, Jacek Caban wrote:
>>> On 08/01/12 11:49, Corinna Vinschen wrote:
Hi,
the below patch changes oleacc.idl to use ULONG rather than unsigned long
in all calls to the XXX_UserYYY automation func
On 08/01/12 12:22, Corinna Vinschen wrote:
> On Aug 1 11:54, Jacek Caban wrote:
>> On 08/01/12 11:49, Corinna Vinschen wrote:
>>> Hi,
>>>
>>> the below patch changes oleacc.idl to use ULONG rather than unsigned long
>>> in all calls to the XXX_UserYYY automation functions. MSDN documents the
>>>
On Aug 1 11:54, Jacek Caban wrote:
> On 08/01/12 11:49, Corinna Vinschen wrote:
> > Hi,
> >
> > the below patch changes oleacc.idl to use ULONG rather than unsigned long
> > in all calls to the XXX_UserYYY automation functions. MSDN documents the
> > BSTR and VARIANT functions to use ULONG. I co
On 08/01/12 11:49, Corinna Vinschen wrote:
> Hi,
>
> the below patch changes oleacc.idl to use ULONG rather than unsigned long
> in all calls to the XXX_UserYYY automation functions. MSDN documents the
> BSTR and VARIANT functions to use ULONG. I couldn't find documentation
> for the equivalent H
Hi,
the below patch changes oleacc.idl to use ULONG rather than unsigned long
in all calls to the XXX_UserYYY automation functions. MSDN documents the
BSTR and VARIANT functions to use ULONG. I couldn't find documentation
for the equivalent HMENU and HWND functions, but I changed them as well
on
18 matches
Mail list logo
