Re: [Quickfix-developers] install Quickfix FIX engine on windows, use python API to build a client/buy-side

[K. F. <kfr...@gm...>]

Hello Asaf!

On Fri, Apr 28, 2017 at 4:47 AM, Asaf Ben Gal <asa...@wh...> wrote:
> ...
> By the way, I installed quickfix by downloading the "source tar" and building the "quickfix_vs12.sln" in Microsoft visual studio.
>
> The thing is that it had a syntax error in the "utility.cpp' file in line number 399 in the "bool thread_spawn( THREAD_START_ROUTINE func, void* var, thread_id& thread )" method.

I saw the same problem with quickfix-1.13.3 back in 2013.

> The original (399 line) was: "result = _beginthreadex( NULL, 0, &func, var, 0, &id );" and I deleted the "&" sign so that it would be: "result = _beginthreadex( NULL, 0, func, var, 0, &id );"
>
> and only then the build was successful...

I made the same correction and was able to build and run quickfix in a
smallish application without any obvious problems.

> Is it a known issue? Did I fix it correctly? I'm not familiar with c# so I have no idea why it worked....

(By the way, I think you mean c++ here.)

I started a thread on this list about it.  Here's a link to my original post:

   https://sourceforge.net/p/quickfix/mailman/message/30333881/

and to the entire thread:

   https://sourceforge.net/p/quickfix/mailman/quickfix-developers/thread/CAKEnbTMwYrXCU1e55ywAzXxLnVoPQfcMyxay%3DEDkNq_OHqoBvg%40mail.gmail.com/#msg30333881

In that thread Mike Gatny said:

   It works with the VS compiler (32-bit, anyway).

I don't doubt that it worked for him, but this never made any sense to me.
My reading of the original code (with "&func") is such that I can't see how
it would ever compile, even with a "tolerant" compiler.

(I should note that I was doing a presumably unsupported windows build
using mingw-w64, a windows port of gcc, rather than ms visual studio.)

It's weird.  You see exactly what I would expect on windows -- a compile
error when using "&func".  But, as far as I can tell, lots of people build and
run quickfix on windows, presumably without seeing this error.

> Thanks again,
>
> Asaf


Happy FIXing!


K. Frank