mingw environment finally complete

[revelator]

[revelator]

[revelator]

hum hum stumbled upon what must be the weirdest bug ever.

remember libgcj has been broken in newer mingw builds (gcc 4 onward) ?

well guess what if you compile it with a real triple like i686-pc-mingw32 instead of just mingw32 it works

now i could understand it if it was actually screwing up the internal paths somehow but in this case it crashes the runtime with an unknown error

i do suspect it having to do with the paths being wrong with the mingw hack (they really ought to get rid of that crap).

lastly a small question.

i intend to build the 64 bit version of the compiler if theres enough interrest. both packages will be seperate from eachother since multilibs dont work on win32 without a cygwin shell in path (lack of symlink support).

i will distribute the packages with there respective libraries 64 or 32 bit as standalone compilers.

can probably get away with using the same codeblocks for both but mixing the compilers wont work so they need each a seperate folder.

any thoughts ?

[revelator]

minimal versions uploaded to site.

get these if you dont want the full shebang

[revelator]

[revelator]

[revelator]

since i ported a lot of linux libraries to win32 i would like to know if i should provide any packages containing these ?.

also i can provide ms compatible import libraries if you dont like gcc.

a small list of libraries include

libsound (sound library linux based)
libxml2 (xml library)
libxslt (xml utility library has plugin support)
libexif (image format library)
libgd (bit like devil multi purpose image handling)
libglut (opengl utility library)
libgstreamer (streaming library)
libjack (another sound library)
libmng (image library mostly used for websites)
openjpeg (a more upto speed jpeg library using c++)
jasper (like the above but in c)
openexr (hd format image library in c++)

also id like any feedback on how my compiler behaves if any of you tried it out.

as noted the 4.5.0 gcc makes huge object files if theres any inline code and potentially breaks on large projects like wxwidgets monolithic builds cause the linker runs out of virtual space. i havent seen any bad behaviour in normal projects yet though.