> Just fix MSYS Autotooling for the whole thing and use libxml2!
>
> ;-)
Indeed...it's a new year and your hard-working dev system has earned a much
needed upgrade ;)
Here's another way of quickly getting an msys + mingw-w64 environment. First,
download and extract these MSYS files, say to `C
Just fix MSYS Autotooling for the whole thing and use libxml2!
;-)
On Thu, Jan 10, 2013 at 12:09 PM, pavel wrote:
> Hi Frank,
>
> I think you should definitively use msxml2.h. I use msxml quite often in
> my applications, but I have my own generated include file, which
> contains the CLSIDs, IID
Hi Frank,
I think you should definitively use msxml2.h. I use msxml quite often in
my applications, but I have my own generated include file, which
contains the CLSIDs, IIDs and interface definitions. If I look at
msxml2.h, I can see that CLSID_DOMDocument is declared as extern and I
have no idea
Hi Pavel!
Thanks for your help.
On Thu, Jan 10, 2013 at 3:56 AM, pavel wrote:
> Hi Frank,
>
> I went again through your posts and if I understand well, you are trying
> to adapt some code written for MS VC++ to MinGW, is that correct?
Yes, precisely.
> In this case, you would probably need to
Hi Frank,
I went again through your posts and if I understand well, you are trying
to adapt some code written for MS VC++ to MinGW, is that correct?
In this case, you would probably need to rewrite a small portion of the
code, unless you will get for libxml2 in the end.
I know nothing about Quic
