Hello Ruben and All! On Sat, Jan 5, 2013 at 5:36 AM, Ruben Van Boxem <[email protected]> wrote: > 2013/1/4 K. Frank <[email protected]> > >> Hi Lists! >> >> What are people's thoughts on porting a linux / visual studio >> project to mingw and / or mingw-w64? >> >> I had asked earlier whether anyone had built QuickFIX with mingw >> and / or mingw-w64. I conclude from the relative silence that mingw >> is not directly supported by the QuickFIX project, and that no one >> has really tried or succeeded in building QuickFIX with mingw. >> ... >> 3) Try to run the linux configure script -- maybe with msys -- to >> get a mingw32-make-compatible makefile, or at least a makefile >> than can be used as a starting point. My concern here is that >> doing so would put the configure script into "linux mode" and >> would trigger the use of various linux-specific code (e.g., posix >> sockets). > > If it's a decent configure script, passing --host=i686-w64-mingw32 or > --host=x86_64-w64-mingw32 should work just fine. If there's a configure > script present, try using that. It cannot be used to get a mingw32-make > compatible makefile.
Please let me respond both to Ruben's and earlier comments: Initially I would like to just get QuickFIX built and play around with it. I may or may not end up having a long-term interest in it. So for the time being I do not think that I would want to invest the effort into adding mingw support to the autotools build process (unless it were already almost there). Also, it probably wouldn't make much sense in adding formal mingw support to QuickFIX unless the QuickFIX project were interested in upstreaming the changes. Based on the relative lack of response to my inquiry on the QuickFIX list and the fact that I've only seen a small handful of questions over the past five years about whether QuickFIX can be built with mingw, I'm guessing that there would be little interest in the QuickFIX community for supporting mingw. To respond to Ruben's and Eli's comments: I don't currently have msys or a unix emulator set up. So the suggestion to try out the configure script "just to see" involves a little more work than just trying it out. To Ruben's comment: Is there some way I can check whether the configure script claims to support mingw? Should I expect the character string for the host (e.g., "i686-w64-mingw32") to reside somewhere in the script itself? Is there some "database" file of supported hosts used by the scripts that I could search for variations of "mingw"? I'd like to have some expectation that the configure script supports mingw before I go hunt down a linux system or unix emulator. As for Peter's suggestion, I will check out CodeLite. If it doesn't look too painful, I'll try translating the solutions file into a makefile. I'm thinking (perhaps wrongly) that if I start with the unix configure script, I'll be more likely to get bumped over into unix-style, pthreads and posix sockets land, where if I start on the visual studio side, I might be more likely to end up with windows threading and winsock. (Just a hope.) >> ... >> So, I'm not asking for a recipe to build QuickFIX in particular. >> Rather, I'm hoping for some wisdom on how to port a relatively >> clean, cross-platform (joint linux / visual studio) project to mingw, >> and on what tricky points I might encounter when doing so. >> >> Thanks for any advice. >> >> K. Frank Thanks to All for your comments. I'll report back if I learn anything useful. 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. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122912 _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
