Op 9 jan. 2013 03:19 schreef "K. Frank" het volgende:
>
> Hi Ruben (and Kai)!
>
> On Tue, Jan 8, 2013 at 1:55 PM, Ruben Van Boxem
> wrote:
> > 2013/1/8 Kai Tietz
> >>
> >> If you don't have them in your include folder, then you might not
> >> using our headers.
> >>
> >> I have msxml.h, msxml2.
Op 9 jan. 2013 03:30 schreef "Jim Michaels" het
volgende:
>
> Tue 01/08/2013 18:24:42.89||E:\prj\tbmailsplit\tbmailsplit-2.15|>grep -i
error 32\err* 64\err* \cd\otbmailsplit.txt
> 32\errgw32tbmailsplit:tbmailsplit.cpp:80:21: fatal error: FileAPI.h: No
such file or directory
> 64\errgw64tbmailsplit
Tue 01/08/2013 18:24:42.89||E:\prj\tbmailsplit\tbmailsplit-2.15|>grep -i error
32\err* 64\err* \cd\otbmailsplit.txt
32\errgw32tbmailsplit:tbmailsplit.cpp:80:21: fatal error: FileAPI.h: No such
file or directory
64\errgw64tbmailsplit:tbmailsplit.cpp:80:21: fatal error: FileAPI.h: No such
file or
Hi Ruben (and Kai)!
On Tue, Jan 8, 2013 at 1:55 PM, Ruben Van Boxem
wrote:
> 2013/1/8 Kai Tietz
>>
>> 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.
>
>
2013/1/8 Kai Tietz
> 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.
Ruben
> The code-snipl
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.
The code-sniplet you've shown is a ource using VC's private extensions
in #C(++). Gcc doesn't support #C(++).
About how
Pavel -
Thanks for your reply.
On Tue, Jan 8, 2013 at 1:12 PM, pavel wrote:
> On Tue, 2013-01-08 at 10:24 -0500, K. Frank wrote:
>
>> Great. If I end up needing libxml2, I'll plan to build it myself.
>>
>> Do you happen to know if I should expect the build to be
>> totally straightforward (with
Kai -
Thanks for your response.
On Tue, Jan 8, 2013 at 10:57 AM, Kai Tietz wrote:
> 2013/1/8 K. Frank :
>> Ah, okay. I will see if I can get the msxml version of quickfix to build.
>> Would you happen to know if a stock windows 7 would come with
>> msxml (or how I can check), or whether I would
On Tue, 2013-01-08 at 10:24 -0500, K. Frank wrote:
> Great. If I end up needing libxml2, I'll plan to build it myself.
>
> Do you happen to know if I should expect the build to be
> totally straightforward (with mingw-w64)? Any gotcha's or
> dependencies I should be expecting?
I have cross-com
2013/1/8 K. Frank :
> Ah, okay. I will see if I can get the msxml version of quickfix to build.
> Would you happen to know if a stock windows 7 would come with
> msxml (or how I can check), or whether I would need visual studio
> or a separate msxml download? Also, I think I searched the mingw-w
Hi Jon!
On Tue, Jan 8, 2013 at 9:23 AM, JonY wrote:
> On 1/8/2013 21:30, K. Frank wrote:
>> Hello List!
>>
>> I'm under the impression that libxml2 works (can be made to work)
>> with mingw-w64, but that it does not come with mingw-w64 out of
>> the box.
>>
>> Is this correct?
>
> That is right,
On 1/8/2013 21:30, K. Frank wrote:
> Hello List!
>
> I'm under the impression that libxml2 works (can be made to work)
> with mingw-w64, but that it does not come with mingw-w64 out of
> the box.
>
> Is this correct?
>
That is right, libxml2 is unrelated to mingw-w64, so there is no bundle
for
Hello List!
I'm under the impression that libxml2 works (can be made to work)
with mingw-w64, but that it does not come with mingw-w64 out of
the box.
Is this correct?
If so, what is the best / easiest way to get libxml2 going with the
mingw-w64 version I have (one of Ruben's std::thread-enabled
2013/1/8 Joshua Boyce
> On Sun, Dec 30, 2012 at 3:39 AM, Ruben Van Boxem > wrote:
>
>> Hi,
>>
>> A new LLVM/Clang has been released, with even better C++11 support.
>> Sadly, no important Windows specific things were fixed or added since the
>> previous release (that I know of), so you're still
On Sun, Dec 30, 2012 at 3:39 AM, Ruben Van Boxem
wrote:
> Hi,
>
> A new LLVM/Clang has been released, with even better C++11 support. Sadly,
> no important Windows specific things were fixed or added since the previous
> release (that I know of), so you're still limited to GCC 4.6.3's libstdc++.
>
15 matches
Mail list logo
