making a portable binary on windows

**patrik08** · 27th May 2006, 21:21

<<<If you can get the mingw source and build configuration, you should be able to create static mingw libs.>>>>

Yes i can build libs but the code from mingw is so large....... wahts file take????

OK MingW impossibel!.....

You think Borland Compiler is Better to make portable exe .....? or Other Window compiler....

**rickbsgu** · 28th May 2006, 01:35

Originally Posted by patrik08

<<<If you can get the mingw source and build configuration, you should be able to create static mingw libs.>>>>

Yes i can build libs but the code from mingw is so large....... wahts file take????

OK MingW impossibel!.....

It would be a matter of reconfiguring the make file/project to create static libs. They might provide a configuration to do that. I haven't gotten into mingw, so can't tell you.

You think Borland Compiler is Better to make portable exe .....? or Other Window compiler....

Not sure what you mean by 'portable'. If the systems are configured identically, one exe should work on all, but you may have to pull over the extra pieces, like dlls, etc., if the .exe is not fully resolved on its own.

Back in the old days, we used to have hot debates about Borland vs. Microsoft. In the end, we wound up with the Microsoft compiler, because we knew that's what the OS was built with, what Windows was built with, and we wouldn't have any compatibility issues, especially with kits like MFC. And MS was naturally ahead of the curve on anything Windows.

Since you're using mingw, it shouldn't matter, frankly. (I presume you're not using the cygwin mingw, which brings in whole other issues.)

I'm using the MS compiler, because I still have to use MS toolkits.

rickb