On Wed, 2 Oct 2013, Phil Dibowitz wrote: >> +Building concordance with MinGW is fairly straight forward (you will need to >> +specify the include and library paths for libconcord as below if you did not >> +install it to the MinGW sysroot): >> + mingw32-configure CPPFLAGS="-I../libconcord" >> LDFLAGS="-L../libconcord/.libs" >> + mingw32-make > > Is there no "make install" or "make installer" or "make msi" or something?
There isn't a way to build an installer - at the moment at least. But we could add one. I was toying with that a bit. >> - int err; >> #ifdef WIN32 > > Don't you mean _WIN32 ? Well, WIN32 works in some cases, but it appears that _WIN32 is more standard. I thought I changed most of them over to _WIN32, but do you think we should do a global replace? ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk _______________________________________________ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel