Hello Sergio! On Sun, Jan 6, 2013 at 2:04 PM, Info <[email protected]> wrote: >> I am taking the liberty of copying this to the QuickFIX, mingw, >> and mingw64 lists. > > No worries. I hope they're interested! > >> Do I understand your comment correctly that you have built QuickFIX with >> mingw? > > QuickFIX builds fine under MinGW!
Excellent! Now if I can only learn how to do it. >> If so, could you let me know how you did it? > > The same way as you would build any other app: configure --prefix=/mingw > ..... then: make then: make install I have a couple of questions about this: According to Ruben's post in a sister thread on the mingw-w64-public list: http://sourceforge.net/mailarchive/message.php?msg_id=30313744 it seems that the configure / make approach doesn't work out of the box. Also, looking at the source code it seems that it won't / can't work (see various comments in the thread), at least not without modifying the source. What, specifically did you do to get it to work? Obviously, if I type "configure" in a plain-vanilla windows command prompt, nothing will happen, because windows doesn't have a configure command and doesn't recognize unix shell scripts. So, did you cross-compile under linux? Did you run configure under msys? Something else? When you built QuickFIX under mingw, from where did you get the source? I got my source directly from www.quickfixengine.org, see: http://www.quickfixengine.org/download Did you have to modify the source at all to get it to compile with mingw? > Can you advise a 'proper' way of testing it once we have the binaries? "Once we have the binaries?" I thought you already had the binaries, because you've built QuickFIX with mingw. Or did you mean something else? As for testing, the source distribution I downloaded (see above) comes with both c++ unit tests that I suppose are build targets in the unix-style makefile and/or the visual-studio solution file. There are also ruby-driven (so for this piece there is a ruby dependency, and you have to install ruby) acceptance tests. So my speculation is that one proceeds as follows: 1) build QuickFIX -- no error? good. 2) run unit tests -- tests pass? better. 3) run acceptance tests -- test pass? best! To me it seems sensible that the proper way of testing is to run the test suites that come with the distribution. > Cheers. > > Sergio. Thanks for following up;. K. Frank ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnmore_123012 _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
