Ruben -

Thanks for your comments.  Just to follow up a little, below ...

On Wed, Jan 9, 2013 at 1:35 AM, Ruben Van Boxem
<[email protected]> wrote:
> Op 9 jan. 2013 03:19 schreef "K. Frank" <[email protected]> het volgende:
>>
>> Hi Ruben (and Kai)!
>>
>> On Tue, Jan 8, 2013 at 1:55 PM, Ruben Van Boxem
>> <[email protected]> wrote:
>> > 2013/1/8 Kai Tietz <[email protected]>
>> >>
>> >> If you don't have them in your include folder, then you might not
>> >> using our headers.
>> >>
>> >> I have msxml.h,  msxml2.h,  msxml2did.h, and  msxmldid.h headers.  You
>> >> should have them too.
>> >
>> > I can confirm my 4.7-1-stdthread toolchain has these headers.
>>
>> Conversely, do you expect that your 4.7.0 std::thread build did  *not*
>> have these headers?  Or should I be surprised that I don't find them,
>> and that I somehow screwed up the installation?  (All I did to install
>> was unzip:
>>
>>    x86_64-w64-mingw32-gcc-4.7.0-stdthread_rubenvb.7z
>>
>> that I downloaded 9/20/2011.)
>
> Update, please, to something not from the stoneage ;-).

Stoneage?!  Never!  You show yourself disrespect!  This is one of
"The Mighty Ruben's 21-st Century Builds!"

> The headers should be there, did you check
> mingw64/x86_64-w64-mingw32/include?

My mistake.  The headers are there -- at least:

   msxml.h
   msxml2.h
   msxml2did.h
   msxmldid.h

(When I looked earlier I had mistakenly searched for "msmxl"
instead of "msxml".)  Thanks for letting me know where to look
manually.

> I don't know when these were added, if
> they haven't been present since forever, but 2011 is too old for me to care
> about it :-)

On a separate note, if I want:

   4.7.0 or later -- preferably 4.8
   std::thread enabled
   static issue with std::thread resolved
   native 64-bit windows to 64-bits windows
   strong preference for abi compatibility with my current "stoneage" build

which build would you recommend?

(Don't stop reading now.  I have a question below.)

> ...
>> ...
>> If, for practicality, I wish to avoid learning about DCOM, is there any
>> simple
>> mingw-w64 replacement for the microsoft-world:
>>
>>    #define _WIN32_DCOM
>>    #import <msxml3.dll> raw_interfaces_only named_guids
>>    using namespace MSXML2;
>>
>> I imagine that the rest of the quickfix could then accesses msxml in
>> relatively
>> standard c++ (i.e., without microsoft extensions) that should be
>> compilable
>> by mingw-w64.
>
> I imagine this is all C, not C++. Nevertheless, QuickFix should wrap this
> stuff anyway. You should be able to not case about its dependencies when
> writing code that uses it.

I agree with this.  QuickFIX has wrapped the calls to msxml, and
I think that unless I try to modify the xml stuff, it should just work,
and I shouldn't have to care.

I am hoping that all I need to do is translate the above code
fragment, e.g.:

   #import <msxml3.dll> raw_interfaces_only named_guids

into the mingw-w64 world (without learning DCOM).

Any suggestions or even educated guesses would be helpful.
Should I just #include all four msxml headers?  Include only
one "master" header file?  Something else?  Might I have to
manually add some msxml library to the link command?

I'm speculating that the microsoft #import command is reading
through the .dll to find and extract the function-prototype information
that in the mingw-w64 world is in the #include header files.  But
that's just a guess, so any help would be appreciated.

Again, I'm not asking how to use msxml.  I just need to know how
to make msxml available to code that presumably already uses it
correctly by finding the mingw-w64 equivalent of the #import line.

>
> Ruben


Thanks again.


K. Frank

------------------------------------------------------------------------------
Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery
and much more. Keep your Java skills current with LearnJavaNow -
200+ hours of step-by-step video tutorials by Java experts.
SALE $49.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122612 
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Reply via email to