hey Basically, I installed MSYS (and only it, not MinGW) with the installer from MinGW.org, then i installed win-builds. See : http://win-builds.org/stable/#_from_windows_for_msys (I'm the one who provided to Adrien the first draft of the installation of win-builds in MSYS.
So, no Cygwin at all :) and about the libraries : the Enlightenment Fundation Libraries (see http://www.enlightenment.org/ ) or the autotools :) What is the package you are trying to compile ? regards Vincent On Wed, Dec 25, 2013 at 1:29 AM, <wynfi...@gmail.com> wrote: > > > Vincent Torri wrote: >> Hey >> >> Note that I have no problem to compile libraries using MSYS and Win-Builds. >> >> Vincent Torri > > That's nice Vicent. Please tell us what libraries or kinds of libraries are > you talking about? > And... are you invoking the MSYS/Win-Builds configure build chain from within > a Cygwin environment or not? Are you using provided "configure" shell > scripts with the libraries? > > What I'm am trying for find out how to do, is complile a package which was > originally developed on Linux to a Microsoft Windows platform, using the > standard toolchain provided with the Win-Builds' environment. > > Please let us know. > Thanks > > REF: >> >> On Tue, Dec 24, 2013 at 9:32 AM, Adrien Nader wrote: >> > Hi, >> > >> > On Tue, Dec 24, 2013, wrote: >> >> >> >> I need some advice on configuration options for building the GNU readline >> >> library. >> >> I am new to win-builds and mingw64 >> >> >> >> Platform is: MS Windows XP SP3. I have the latest cygwin installed and >> >> the new win-builds separately installed. >> >> >> >> When invoking the configure script which comes with GNU readline source I >> >> do the following: >> >> >> >> ---- >> >> wb=/cgydrive/c/win-builds-w32 >> >> PATH=$wb/bin:.:$wb/local/bin:/bin:/usr/local/bin:$wds:$s >> >> PKG_CONFIG_LIBDIR=/cygdrive/c/win-builds-32/lib/pkgconfig >> > >> > I don't think you can use the compilers provided by win-builds directly >> > under cygwin. As you've already seen, they expect windows-style paths >> > while cygwin will hand them posix-style ones. >> > >> > I haven't checked yet but you should be able to use the cross-compilers >> > provided by cygwin as "mingw64-i686-gcc(-g++)" or with "x86_64 instead >> > of "i686". This means you wouldn't prepend $wb/bin to your PATH and >> > probably not put $wb/local/bin either. >> > >> > The restriction is that the compilers from win-builds and from cygwin >> > must have compatible configurations, especially for C++. This mostly >> > means sjlj exception on 32b and SEH ones on 64b; which are the default >> > settings. >> > >> > Your current pkg-config and libdir settings seem good. To sum up, you >> > need the cygwin compiler (installed and default value for PATH) and the >> > win-builds binaries (set PKG_CONFIG_LIBDIR and --libdir). >> > >> >> ./configure --host=i686-w64-mingw32 --prefix=$wb/local >> >> --libexecdir=$wb/sbin --libdir=$wb/lib --includedir=$wb/include >> > >> > You probably don't need to set all these paths (in particular >> > libexecdir); configure should set most of them properly by itself. >> > >> > Start with only --host, --prefix and --libdir. Add --includedir if some >> > includes are not found while they're in this directory. >> > >> >> I am not sure if the "--host=i686-w64-mingw32" is valide for the >> >> win-builds distribution. >> > >> > It is the right triplet for 32 bits. >> > >> >> The configure script is finding and using the Cygwin environment, which I >> >> think is not want should be done. >> > >> > I guess it tries to use the win-builds-provided GCC but fails to do so >> > because of paths and fallbacks to the cygwin one. >> > >> >> I am attaching the full output the configure script as a file. >> > >> > If you continue to have issues, could you send me the config.log file? >> > Don't send it on the mailing-list since it is usually a fairly big file >> > which makes up for a fair amount of data when multiplied by the number >> > of list subscribers. >> > >> > 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 >> > _______________________________________________ > #EOM > > ------------------------------------------------------------------------------ > 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 ------------------------------------------------------------------------------ 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
