Hi, On Thu, Dec 26, 2013, wynfi...@gmail.com wrote: > > What is the package you are trying to compile ? > > I eventually want to build the Linphone application. > (https://www.linphone.org/) > It's current MS Windows port is out of date, crashes spuriously, and is not > current. > I do not wish to use Skype and consider it's use of private data is not > desirable. > > However, I am starting with a simple GNU library, readline, to get the hang > of using > MinGW64 Win-Builds environment. > > > Since many applications and lbraries from the *nix platform use a configure > script, a shell is needed to run it. Does such a shell exist which uses > Microsfot pathname formats?
The difference between cygwin and msys (which is a fork of cygwin) is roughly that msys will test whether it is going to run a regular native windows application or an msys one and if it's a regular native one, it will automatically translate posix-style paths to windows ones. Cygwin is also much more comprehensive and therefore bigger; this makes some people prefer msys. I did a few changes and now I've mostly ported the msys install and environment setup scripts to cygwin. You need to download the bundle: http://win-builds.org/1.3-rc1/win-builds-bundle-1.3-rc1.zip and overwrite two of its files with these ones: http://notk.org/~adrien/win-builds-cygwin/msys-install.sh http://notk.org/~adrien/win-builds-cygwin/win-builds-switch.sh Then it's a matter of running these commands from a cygwin shell (you only need to cd into the bundle directory): ./msys-install.sh i686 ./msys-install.sh x86_64 After that you can set your environment with one of these commands: . win-builds-switch 32 . win-builds-switch 64 (note the leading ". ") This will set the YYPREFIX and PKG_CONFIG_LIBDIR environment variables on both msys and cygwin (on msys it will also change PATH). That is all for win-builds; then you need to install the rest through cygwin's setup.exe. This is a rough list and you will add or remove packages related to these as you see fit and as you need them: mingw64-i686-gcc mingw64-x86_64-gcc pkg-config After that, I'm able to build a dummy program and link it to libvorbis with: i686-w64-mingw32 $(pkg-config --libs --cflags vorbis) test.c The command above is running in a cygwin shell, i686-w64-mingw32 and pkg-config are cygwin binaries, libvorbis comes from win-builds and a windows native executable is created. I hope the above solves your issues and is clear. I will be a bit harder to reach for roughly one week as I'm going to 30c3 in Hamburg and not taking my laptop with me. :) Regards, Adrien Nader ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
