On 10/02/2013 09:36 AM, Scott Talbert wrote: > 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.
OK... but my point is that there's not much guidance for a user after "make" - do all the resulting DLLs have to be in the same directory as the EXE? Do they have to go in to C:\WIN32\System? You have 5-ish files, what now? At the end of the Linux instructions you can just run a binary... that's not true here. > 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? Yeah, probably. -- Phil Dibowitz p...@ipom.com Open Source software and tech docs Insanity Palace of Metallica http://www.phildev.net/ http://www.ipom.com/ "Be who you are and say what you feel, because those who mind don't matter and those who matter don't mind." - Dr. Seuss
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ 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