From: kev c <kev...@ya...> - 2007-12-13 19:37:53
|
How do you do this. Sorry for the dumb question. I couldnt really find any documentation. I would like to try building some programs on linux for windows. Kev ____________________________________________________________________________________ Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs |
From: Dan K. <dan...@gm...> - 2015-12-17 16:38:18
|
Hi all, I would like to build gcc 4.8.1 to run on Linux x64 and target mingw. In order to upgrade the compiler we use to build (some of) the win32 binaries at http://www.sqlite.org/download.html . Currently we're using 4.5.2. Is it possible to do this using the [make package] command from the gcc-4.8.1-4-mingw32-src.tar.lzma tarball? Or does that only work for native builds? Thanks, Dan Kennedy. |
From: Dave K. <dav...@ar...> - 2007-12-13 19:51:20
|
On 13 December 2007 19:38, kev c wrote: > How do you do this. Sorry for the dumb question. I > couldnt really find any documentation. I would like to > try building some programs on linux for windows. The simplest way I know is to go to http://www.profv.de/mingw_cross_env/ and use the script there to build yourself a full cross-environment, including binutils, compiler, libraries and headers. NB. that I've only tried it on cygwin rather than linux, but it really did make the whole job trivially easy. cheers, DaveK -- Can't think of a witty .sigline today.... |
From: Keith M. <kei...@us...> - 2007-12-13 20:13:25
|
On Thu, 2007-12-13 at 19:50 +0000, Dave Korn wrote: > > How do you do this. Sorry for the dumb question. I > > couldnt really find any documentation. I would like to > > try building some programs on linux for windows. > > The simplest way I know is to go to > > http://www.profv.de/mingw_cross_env/ What is wrong with the cross-compiler build scripts which we ourselves provide? Use our scripts, and we'll support you: http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=12644&release_id=17892 Use somebody else's, and you'll likely find you are on your own. Regards, Keith. |
From: kev c <kev...@ya...> - 2007-12-13 20:43:16
|
--- Keith Marshall <kei...@us...> wrote: > On Thu, 2007-12-13 at 19:50 +0000, Dave Korn wrote: > > > How do you do this. Sorry for the dumb question. > I > > > couldnt really find any documentation. I would > like to > > > try building some programs on linux for windows. > > > > The simplest way I know is to go to > > > > http://www.profv.de/mingw_cross_env/ > > What is wrong with the cross-compiler build scripts > which we ourselves > provide? Use our scripts, and we'll support you: > http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=12644&release_id=17892 > > Use somebody else's, and you'll likely find you are > on your own. > > Regards, > Keith. > I have the tools, I think. I have things like /usr/bin/i586-mingw32msvc-gcc I just dont know how to use them. Is the configuration script hopefully supposed to let you specify mingw32 somehow. I found this http://gcc.gnu.org/onlinedocs/gcc-4.2.2/gcc/Target-Options.html#Target-Options Does that mean that I should use target=i586-mingw32msvc in my case. I am confused between target and host, though. > > ------------------------------------------------------------------------- > SF.Net email is sponsored by: > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services > for just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > _______________________________________________ > MinGW-users mailing list > Min...@li... > > You may change your MinGW Account Options or > unsubscribe at: > https://lists.sourceforge.net/lists/listinfo/mingw-users > ____________________________________________________________________________________ Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs |
From: NightStrike <nig...@gm...> - 2007-12-13 21:09:53
|
On 12/13/07, kev c <kev...@ya...> wrote: > > --- Keith Marshall > <kei...@us...> wrote: > > > On Thu, 2007-12-13 at 19:50 +0000, Dave Korn wrote: > > > > How do you do this. Sorry for the dumb question. > > I > > > > couldnt really find any documentation. I would > > like to > > > > try building some programs on linux for windows. > > > > > > The simplest way I know is to go to > > > > > > http://www.profv.de/mingw_cross_env/ > > > > What is wrong with the cross-compiler build scripts > > which we ourselves > > provide? Use our scripts, and we'll support you: > > > http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=12644&release_id=17892 > > > > Use somebody else's, and you'll likely find you are > > on your own. > > > > Regards, > > Keith. > > > I have the tools, I think. I have things like > /usr/bin/i586-mingw32msvc-gcc I just dont know how to > use them. > > Is the configuration script hopefully supposed to let > you specify mingw32 somehow. I found this > > http://gcc.gnu.org/onlinedocs/gcc-4.2.2/gcc/Target-Options.html#Target-Options > > Does that mean that I should use > target=i586-mingw32msvc in my case. > > I am confused between target and host, though. host is the computer type that will run the compiler. target is the computer type that will run the programs the compiler makes. |
From: Keith M. <kei...@us...> - 2007-12-13 21:35:56
|
On Thu, 2007-12-13 at 12:43 -0800, kev c wrote: > I have the tools, I think. I have things like > /usr/bin/i586-mingw32msvc-gcc I just dont know how to > use them. Ok. That is *not* our implementation of the tools. If it works for you, well and good; if not, you'll have ask the packager for help. > Is the configuration script hopefully supposed to let > you specify mingw32 somehow. I found this > > http://gcc.gnu.org/onlinedocs/gcc-4.2.2/gcc/Target-Options.html#Target-Options > > Does that mean that I should use > target=i586-mingw32msvc in my case. That's specific to building the compiler itself; you don't use `target' in any other context. > I am confused between target and host, though. Many people are. Any autotooled configure script uses `build' to identify the platform running the build tools, `host' to identify the platform on which the built application will be run, and `target' to identify the platform for which the built application will itself generate code; (thus `target' only has meaning when *building* code generators such as compilers). Cross-compile mode is activated when build != host, causing configure to look for ${host_alias}-gcc and friends, (where ${host_alias} is the value you specify for the `host' argument, so in your case `--host=i586-mingw32msvc' -- an oxymoron if ever I saw one; in the case of *our* tools, it would be simply `--host=i586mingw32'). Regards, Keith. |
From: Dave K. <dav...@ar...> - 2007-12-14 10:11:55
|
On 13 December 2007 20:14, Keith Marshall wrote: > On Thu, 2007-12-13 at 19:50 +0000, Dave Korn wrote: >>> How do you do this. Sorry for the dumb question. I >>> couldnt really find any documentation. I would like to >>> try building some programs on linux for windows. >> >> The simplest way I know is to go to >> >> http://www.profv.de/mingw_cross_env/ > > What is wrong with the cross-compiler build scripts which we ourselves > provide? Only my lack of knowledge of their existence! :) cheers, DaveK -- Can't think of a witty .sigline today.... |
From: kev c <kev...@ya...> - 2007-12-20 19:38:46
|
I am useing the build script now it is wonderful. But I was wondering about the target spec why would you want to use some thing like i686-pc-mingw32 instead of just i386-mingw32. ____________________________________________________________________________________ Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs |
From: Earnie B. <ea...@us...> - 2007-12-20 21:59:57
|
Quoting kev c <kev...@ya...>: > I am useing the build script now it is wonderful. But > I was wondering about the target spec why would you > want to use some thing like i686-pc-mingw32 instead of > just i386-mingw32. > Because the string has meaning. See autoconf documentation for more detail. Earnie |
From: kev c <kev...@ya...> - 2007-12-20 23:22:47
|
--- Earnie Boyd <ea...@us...> wrote: > > Quoting kev c <kev...@ya...>: > > > I am useing the build script now it is wonderful. > But > > I was wondering about the target spec why would > you > > want to use some thing like i686-pc-mingw32 > instead of > > just i386-mingw32. > > > > Because the string has meaning. See autoconf > documentation for more detail. > What exact meaning does the string have. The autoconf documentation doesnt say much about it. It didnt really answer my question. > Earnie > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio > 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > MinGW-users mailing list > Min...@li... > > You may change your MinGW Account Options or > unsubscribe at: > https://lists.sourceforge.net/lists/listinfo/mingw-users > ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ |
From: Greg C. <gch...@sb...> - 2007-12-21 01:33:05
|
On 2007-12-20 23:22Z, kev c wrote: > --- Earnie Boyd <ea...@us...> wrote: > >> >> Quoting kev c <kev...@ya...>: >> >> > I am useing the build script now it is wonderful. >> But >> > I was wondering about the target spec why would >> you >> > want to use some thing like i686-pc-mingw32 >> instead of >> > just i386-mingw32. >> > >> >> Because the string has meaning. See autoconf >> documentation for more detail. >> > What exact meaning does the string have. The autoconf > documentation doesnt say much about it. It didnt > really answer my question. Then consult the autobook. I'm sure it explains each field in a configuration name. [snip quoted sourceforge pseudo-sig-block] |
From: Keith M. <kei...@us...> - 2007-12-29 22:08:10
|
On Fri, 2007-12-21 at 01:32 +0000, Greg Chicares wrote: > On 2007-12-20 23:22Z, kev c wrote: > > --- Earnie Boyd <ea...@us...> wrote: > > > >> > >> Quoting kev c <kev...@ya...>: > >> > >> > I am useing the build script now it is wonderful. > >> > But I was wondering about the target spec why would > >> > you want to use some thing like i686-pc-mingw32 > >> > instead of just i386-mingw32. > >> > >> Because the string has meaning. See autoconf > >> documentation for more detail. > >> > > What exact meaning does the string have. The autoconf > > documentation doesnt say much about it. It didnt > > really answer my question. > > Then consult the autobook. I'm sure it explains each field > in a configuration name. The meaning is explained in the README file, which accompanies *our* build script package; for convenience, it is:-- CPU-VENDOR-OSTYPE And yes, the pc *does* have meaning, as the VENDOR tag; however, it does not have any *significant* meaning, and is therefore quite redundant. That is why our build scripts default to omitting it, and naming the cross-compiler suite as i386-mingw32-*. (I call mine i586-mingw32-*, and many users will choose i686-mingw32-*). It is important that you have at least a valid CPU tag, and the OSTYPE *must* be at least mingw32, (many Linux distributors call it mingw32msvc, which IMO is absolutely hideous, if not confusing, for to me it implies some relationship to the Microsnot compiler, which just doesn't exist), but the VENDOR tag serves no real purpose, and may be safely omitted. Regards, Keith. |
From: Dave K. <dav...@ar...> - 2008-07-29 17:15:56
|
Keith Marshall wrote on 13 December 2007 20:14: [ Yeh, it was a while ago. So I have more info now, because I've actually been trying the mingw.org scripts for the first time. ] > On Thu, 2007-12-13 at 19:50 +0000, Dave Korn wrote: >>> How do you do this. Sorry for the dumb question. I >>> couldnt really find any documentation. I would like to >>> try building some programs on linux for windows. >> >> The simplest way I know is to go to >> >> http://www.profv.de/mingw_cross_env/ > > What is wrong with the cross-compiler build scripts which we ourselves > provide? What, like apart from it not working? ;-) > Use somebody else's, and you'll likely find you are on your own. I'll file a bug, but just in case this rings a bell with anyone: the build failed when trying to configure w32api with a file-not-found error. ------------------<snip>------------------ make[2]: Nothing to be done for `install'. make[2]: Leaving directory `/home/dk/mingw/tmp/mingw-3.4.5/build-gcc/libiberty/testsuite' make[1]: Leaving directory `/home/dk/mingw/tmp/mingw-3.4.5/build-gcc/libiberty' x86-mingw32-build.sh: stage 1: build w32api ... x86-mingw32-build.sh: line 139: ../config.guess: No such file or directory x86-mingw32-build.sh: line 139: ../configure: No such file or directory x86-mingw32-build.sh: unrecoverable error configuring w32api ------------------<snip>------------------ and this turns out because something went wrong with the temp build dir structure, which made this code here rather unhappy: ------------------<snip>------------------ 137 case $COMPONENT in mingw-runtime | w32api) 138 setbuilddir ${COMPONENT}-* 139 $RUN ../configure --prefix="$INSTALL_DIR" --host="$TARGET" \ 140 --build=${BUILD_PLATFORM=`../config.guess`} || die $? \ 141 "$unrecoverable configuring $COMPONENT" ------------------<snip>------------------ Now, I guess that line 138 is trying to use a wildcard to cd into whatever is the component directory without having to care about the trailing version-number suffix, but it doesn't work nicely for me because looking in the build temp dir: [dk@quattro x86-mingw32-build.sh-0.0-20061107-1]$ ls -la ../tmp/mingw-3.4.5/ total 32 drwxr-xr-x 8 dk eng 4096 Jul 29 16:57 . drwxr-xr-x 3 dk eng 4096 Jul 29 16:52 .. drwx------ 18 dk eng 4096 Jul 29 16:55 binutils-2.17.50-20060716-1-src drwxr-xr-x 5 dk eng 4096 Jul 29 16:58 build-gcc drwxr-xr-x 10 dk eng 4096 Dec 12 2005 gcc-3.4.5-20060117-1 drwxr-xr-x 5 dk eng 4096 Aug 30 2006 mingw-runtime-3.10 drwxr-xr-x 4 dk eng 4096 Jul 29 17:00 w32api-* drwxr-xr-x 4 dk eng 4096 Apr 14 2006 w32api-3.7 [dk@quattro x86-mingw32-build.sh-0.0-20061107-1]$ .... it looks like the directory actually got created! Anyway, if anyone's already discovered this one, please let us know how you fixed it. I tried googling this but couldn't find anything similar, so in the meanwhile I'll get on with filing a bug in the tracker. cheers, DaveK -- Can't think of a witty .sigline today.... |
From: Dave K. <dav...@ar...> - 2008-07-29 17:36:54
|
Dave Korn wrote on 29 July 2008 18:16: > x86-mingw32-build.sh: stage 1: build w32api ... > x86-mingw32-build.sh: line 139: ../config.guess: No such file or directory > x86-mingw32-build.sh: line 139: ../configure: No such file or directory > x86-mingw32-build.sh: unrecoverable error configuring w32api > Anyway, if anyone's already discovered this one, please let us know how > you fixed it. I tried googling this but couldn't find anything similar, > so in the meanwhile I'll get on with filing a bug in the tracker. Done: https://sourceforge.net/tracker/index.php?func=detail&aid=2031691&group_id=2 435&atid=102435 (aka http://tinyurl.com/5fbrq6 to avoid wrapping) cheers, DaveK -- Can't think of a witty .sigline today.... |
From: Pieter T. <pie...@in...> - 2007-12-14 09:46:58
|
kev c wrote: > How do you do this. Sorry for the dumb question. I > couldnt really find any documentation. I would like to > try building some programs on linux for windows. > > Kev > > > Well as mentioned there are some scripts on the mingw site. I've recently built a i686-pc-mingw32 cross compiler on Debian Etch (AMD64) from FSF gcc sources (4.2.2) The FSF sources may not contain some win32-specific patches that are found in the mingw-site gcc sources; cehck this list's archives for discussions on this. Very short summary: (ask me if you need more details) What I did was: grab binutils-2.18 and gcc-4.2.2 from ftp.gnu.org, and grab w32api and mingw-runtime sources from mingw site. Native compiler is gcc 4.1.2. 1. build cross binutils and install in $prefix 2. add cross-binutils bin directory to $PATH 3. copy w32api and mingw-runtime headers into $prefix/$target/include ($target being i686-pc-mingw32 in my case) 4. build C-only cross-gcc and install in $prefix 5. compile w32api then mingw-runtime using compiler created in 4, install in $prefix/$target 6. compile cross-gcc (I used --enable-sjlj-exceptions --enable-threads --enable-languages=c,c++) I have used this compiler to cross-compile gtk 2.12.3 and its dependencies, and I have successfully run the resulting gtkdemo.exe on my windows machine All in all, it really depends what languages you need to support. C and C++ should work like described above. For Fortran, you need MPFR and GMP libraries. You can cross-compile these, but they may also be needed on your build platform (Debian Etch versiopns are not recent enough) so I had no luck there. For Ada: at some stage I got an error in some gnatmake command which was including both the ada includes on the build system (/usr/...) and Ada includes from the gcc source tree. After "fixing" (?) this, I got myself another error though. The FSF GCC manual states that to compile GNAT, it's best to start with a native compiler. So I attempted to build native gcc (with ada support) 4.2.2 on my Debian system, but probably bootstrapped it the wrong way. So building my native compiler failed, and I gave up on my attempt to build a i686-pc-mingw32 gnat cross compiler after that. Java: you should probably build without AWT (i.e. --enable-libgcj --disable-java-awt), but I haven't tested this so far. Pieter |