Hi Ruben (and Peter) - First, thanks to everyone for their comments. This discussion has been very informative and helpful.
Before commenting inline, below, please let me semi-hijack this section of the thread with a comment to Peter: I've downloaded (but not yet installed) CodeLite, and have been browsing the online documentation. I don't yet see a discussion of how to import / translate a visual-studio solution file. Could you point me to a section of the documentation that covers this (or maybe the right button to click on the CodeLite application)? (I've also recopied this post to the mingw-users list, because I think that was the list Peter was using.) On Sun, Jan 6, 2013 at 7:55 AM, Ruben Van Boxem <[email protected]> wrote: > 2013/1/6 JonY <[email protected]> >> >> On 1/6/2013 18:54, Kai Tietz wrote: >> >> >>>> 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.) >> >>> ... > > To get this thread back on-topic and to prove my point (even with autotools > if you didn't have a platform in mind it probably won't work out of the > box), I tried the quickfix autotools and got (the half-expected): For my education, what specific autotools command line did you type? Something like: ./configure --host=x86_64-w64-mingw32 && make ? Did you run it on linux or under msys? > > libtool: compile: x86_64-w64-mingw32-g++ -DHAVE_CONFIG_H -I. > -I/m/Development/Source/quickfix/src/C++/test -I../../.. -I.. > -I../../../UnitTest++/src -g -O2 -Wall -ansi -Wpointer-arith -Wwrite-strings > -I/libxml/include/libxml2 -O0 -g -MT DictionaryTestCase.lo -MD -MP -MF > .deps/DictionaryTestCase.Tpo -c DictionaryTestCase.cpp -DDLL_EXPORT -DPIC > -o .libs/DictionaryTestCase.o > In file included from ../Exceptions.h:27:0, > from ../Dictionary.h:31, > from DictionaryTestCase.cpp:28: > ../Utility.h:71:24: fatal error: sys/socket.h: No such file or directory > #include <sys/socket.h> > ^ > compilation terminated. Is the output of the configure step a relatively straightforward makefile (i.e., not too many layers of variables or sub-makefiles)? If so, may I ask you to email me a copy? Because the linux and windows source distributions are the same (at least as far as I can tell), I think if I have a plain-vanilla makefile, I'll be able to tweak the #ifdef's in the source or maybe the predefined preprocessor macros passed in to the compiler, and get things to work. The code isn't that bad. The only unix / windows differences that I've come across are sockets, threads, and the stdafx.h stuff, so I think I should be able to sort things out. > To Frank: I suggest writing some kind of build script or file from the VC > project files, which have a high chance of having all the Windows stuff set > right. Remember to drop stdafx.h and mind specific defines and such that > would signify the exclusion of the Unix code. Yes, that is my current plan of action, trying to leverage the CodeLite solution-file translation that Peter mentioned. > Hope this helps, Very much so. > Ruben > ... Thanks for everyone's help. 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
