Re: [Quickfix-developers] Problem building python extension on windows.

[<or...@qu...>]

Hi Fredrik,

We actually have never produced a build for the python library under
windows.  This is why there is no included project file for it.  The
initial assumption was that most python users would be under some sort
of unix, so effort wasn't really put into getting it to work on windows.
 I know that some developers got the ruby version to work in windows, so
I don't see why the same cannot be done for python.

I do not believe the SWIG generated code is the problem.  SWIG should be
generating portable code.  Based on the compiler errors you posted, it
looks like some of the types defined in Microsoft's SDKs are clashing
with types in QuickFIX (INT, CHAR etc). It looks like the reason they
are clashing is due to the using namespace FIX declaration.  I doubt
there is a good reason this declaration needs to be there, we will just
have to specify the namespace when needed.

--oren

> -------- Original Message --------
> Subject: [Quickfix-developers] Problem building python extension on
> windows.
> From: fredrik kant <fre...@gm...>
> Date: Thu, February 18, 2010 3:48 am
> To: qui...@li...
> 
> 
> QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html<hr>Hi!
> I struggle to build quickfix as an extension module on windows (It was some
> time ago since I done this kind of work...).
> In the windows source I downloaded, *
> qui...@li...* , I see in the QuickFixPython.cpp
> a include statement, "config.h"  which I can't found anywere in the download
> and changed it to config_windows.h (which was found under /src) in a attemp
> to perhaps solve the problem.
> 
> 
> My environment:
> - windows 7, 32-bit
> - visual studio 2008
> - my own compiled version of  python 2.6.
> 
> Anyway, I was able to build both quickfix and Python2.6 out of the box but
> when I try building QuickfixPython a lot of errors can be seen.
> >>>
> QuickfixPython.cpp(24796) : error C2872: 'INT' : ambiguous symbol
>         could be 'C:\Program Files\\Microsoft
> SDKs\Windows\v6.0A\include\windef.
> h(172) : int INT'
>         or       'c:\quickfix-win\quickfix\src\c++\FieldTypes.h(509) :
> FIX::INT'
> >>>
> >>>
> QuickfixPython.cpp(24199) : error C2872: 'CHAR' : ambiguous symbol
>         could be 'C:\Program Files\\Microsoft
> SDKs\Windows\v6.0A\include\winnt.h
> (276) : char CHAR'
>         or       'c:\quickfix-win\quickfix\src\c++\FieldTypes.h(507) :
> FIX::CHAR
> <<<
> etc.
> 
> I haven't investigated this futher and haven't used SWIG before and hope
> that it is perhaps a simple solution to this.
> 
> 
> I tested using:
> - the ordinary distutils way
> - using CodeBlock
> - using Visual Studio (I really sucks when it comes to setup this kind of
> things).
> 
> I also have cygwin(I also downloaded the unix source) and MinGW installed.
> 
> Is there a simple solution to this problem? Perhaps just generating a new
> wrapper using SWIG on windows?
> -- 
> Fredrik Kant
> 
> -- 
> Fredrik Kant
> 
> Kant Consulting AB
> Mobile: +46 70 787 06 01
> www.kantconsulting.se<hr>------------------------------------------------------------------------------
> Download Intel&reg; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs 
> proactively, and fine-tune applications for parallel performance. 
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev<hr>_______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers