Re: [Mingw-users] [Mingw-w64-public] Thoughts on how to build a linux / visual studio project (QuickFIX) with mingw

[Peter R. <p.r...@sh...>]

On 06/01/13 17:42, K. Frank wrote:

...mega-snip
> I have installed CodeLite. I see brief hints in the documentation, and 
> suggestive entries in CodeLite's gui menus that this should be 
> possible, but I haven't figured out how to do it yet. (Peter, if 
> you're around, I've re-copied this post to the mingw list. My sticking 
> point is that I seem to be able to import a msvc solutions file into a 
> CodeLite workspace, and I seem to be able to export a makefile from a 
> CodeLite project, but I haven't been able to get the workspace (or at 
> least the solutions file in it) linked to the project, so the makefile 
> I export is trivial. I do think I created the project in the 
> workspace, but what do I know ... ? Any further suggestions would be 
> most welcome.)

Hmmm.... I see what you mean. I can't see how to import the files into 
CodeLite either.  (That said I don't actually use CodeLite - I have 
periodically looked at it to see if it has developed to the point where 
I would use it instead of CodeBlocks. So my 'knowledge' comes from the 
published list of features and a brief 'play' rather than direct 
experience.)

Plan B: CodeBlocks imports MSVS files - I have tested this (although the 
import seems a bit flaky). But I can see  a whole list of 10 
(sub-)projects including the unit test stuff, examples, etc., together 
with the associated source files. When I try building (an arbitrary) 
file I get an error that derives from the first conditional compilation:

#ifdef _MSC_VER
#include "stdafx.h"
#else
#include "config.h"
#endif

because there is no config.h file. So I guess that leads you straight 
back to configure...

But at least CodeBlocks imports the MSVS file! The downside is that 
CodeBlocks does not export a makefile - AFAIU the CodeBlocks makefile 
plugin is broken. But if you need to generate config.h then the IDE 
route looks to be of no help.

P.