END OF AN ERA, FRACTALFORUMS.COM IS CONTINUED ON FRACTALFORUMS.ORG

I use MinGW (32-bit) environment (with gcc compiler). To compile the program there are needed GTK2+ and libjpeg development libraries. The program is already prepared to compile for Win32. With VisualStudio 2010 will be difficult because it's not so compatible with GNU standards.

Thank you very much for your inputs guys,

NOTE: I'm only interested in building for x64.


Well, I don't mind difficult, as long as it is not impossible!?


Could you be more specific as which versions are needed? GTK2.? (seem to have two branches)

http://www.gtk.org/download/win64.php

There is several libjpeg out there and I'm not sure which one is needed.

It would be helpful if you could provide the thirdparty libraires as a separate download or maybe a "how to" document.



I'm still surprised that Visual Studio is considered like a black sheep and more often ditched by the open source community.



Alright, thanks for the hint, I'll do that.

It's simple: GNU autotools and GNU make and gcc offer a single build environment that requires only minimal adjustments for compatibility with Windows.

Visual Studio uses a syntactically somewhat different make utility called nmake, and you cannot even build 64 bit binaries if you do not buy a commercial Visual Studio 2010 version.

The only cross-platform build approach that I know that will handle Visual C++ as well is cmake. But once you've started a project based on autotools, it is hard to switch to cmake.

when i was still using Windows and owned a full install of MS's VisualStudio
I found that 90%+ of the software i was building was gnu ported to windows

with building in VS it was necessary to build the project from scratch
import the cpp code and the required headers from an existing project
then build the lib's that are required ,the same way
but build those first
the same as i would if i wrote the whole thing from scratch


it took me a few weeks to build GTK2 and all the prerequisites

in contrast

Mingw / msys
from the terminal ( no GUI )
one day to install mingw , configure it
15 min. to run a "hello world" and debug it

then 30 min to install the needed software to build "The Gimp " ( the gtk2 & source was already installed with a few mouse clicks )
and 30 min build time

now there is some "fun" converting a mingw .so and .la to a Windows .dll
normally it is easy with mingw's "dlltool"

for a GUI there is "bloodshed's " DevC++
DevC++ can also act a a gui for installing prebuilt( *.dll & *.exe) code ( or source and/or dev *.h headers) in mingw


now if you ARE building a lot of MS's "share code" and .net code
then use VS !!!

the two ( VS and MinGW ) can ?? with CARE .Can be installed side by side
BUT !!!!!
mingw can NOT use the VS's dev files
and VS  CAN NOT use MinGW code

the headers are NOT COMPATIBLE

the only issue is when M4 messes up
wrapping ones brain around the m4 macros is well like
having a " Pan Galactic Gargle Blaster"