From: Torsten S. <TSc...@gm...> - 2008-02-06 20:23:42
|
Dear list! I am trying to follow the howtos: http://www.mingw.org/MinGWiki/index.php/MSYSBuildEnvironment http://www.mingw.org/MinGWiki/index.php/Build%20MSYS Unfortunately, I don't get very far. > Now you can enter the MSYS Build Environment by simply doing > MSYSTEM=MSYS start /msys Calling this, after having done the preparations described, a Windows Command Windows (CMD.EXE) opens. Are these howtos still applicable? Am I missing the obvious? Regards, Torsten |
From: Cesar S. <ces...@gm...> - 2008-02-09 10:56:55
|
Torsten Schlabach wrote: > Dear list! > > I am trying to follow the howtos: > > http://www.mingw.org/MinGWiki/index.php/MSYSBuildEnvironment > http://www.mingw.org/MinGWiki/index.php/Build%20MSYS > > Unfortunately, I don't get very far. > >> Now you can enter the MSYS Build Environment by simply doing >> MSYSTEM=MSYS start /msys > > Calling this, after having done the preparations described, a Windows Command Windows (CMD.EXE) opens. > > Are these howtos still applicable? Am I missing the obvious? > > Regards, > Torsten > Use the msysdvlpr command to enter the MSYS Build Environment. I updated the howto accordingly. The former method didn't work for me as well, with the msys.bat file shipped in MSYS 1.0.10. It couldn't find rxvt.exe nor sh.exe. The CVS version has a fix for this. If you want, you can get it here: http://mingw.cvs.sourceforge.net/*checkout*/mingw/msys/dvlpr/bin/msys.bat Regards, Cesar |
From: Torsten S. <tsc...@gm...> - 2008-02-09 23:20:32
|
Dear Cesar, thanks for your help. Unfortunately, there are still issues. > Use the msysdvlpr command to enter the MSYS Build Environment. I don't have that. This script is contained in msysDVLPR-1.0.0-alpha-1.tar.gz which I am supposed to unpack to /msys. But /msys/bin will only be on the PATH when I am already in the MSYS build environment. Kind of a chicken and egg problem. But I was able to enter the MSYS build environment using the patched version of start.bat. I have passed some other issues and was able to do a successful configure + make in my /msys directory. But where do I go from here? What have I built now? How can I install this? I mean, do I know have some new .exe file which I can use to setup my MSYS-snapshot environment? Regards, Torsten Cesar Strauss schrieb: > Torsten Schlabach wrote: > >>Dear list! >> >>I am trying to follow the howtos: >> >>http://www.mingw.org/MinGWiki/index.php/MSYSBuildEnvironment >>http://www.mingw.org/MinGWiki/index.php/Build%20MSYS >> >>Unfortunately, I don't get very far. >> >> >>>Now you can enter the MSYS Build Environment by simply doing >>>MSYSTEM=MSYS start /msys >> >>Calling this, after having done the preparations described, a Windows Command Windows (CMD.EXE) opens. >> >>Are these howtos still applicable? Am I missing the obvious? >> >>Regards, >>Torsten >> > > > Use the msysdvlpr command to enter the MSYS Build Environment. I updated > the howto accordingly. > > The former method didn't work for me as well, with the msys.bat file > shipped in MSYS 1.0.10. It couldn't find rxvt.exe nor sh.exe. The CVS > version has a fix for this. If you want, you can get it here: > http://mingw.cvs.sourceforge.net/*checkout*/mingw/msys/dvlpr/bin/msys.bat > > Regards, > Cesar > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Mingw-msys mailing list > Min...@li... > https://lists.sourceforge.net/lists/listinfo/mingw-msys |
From: Keith M. <kei...@us...> - 2008-02-14 11:21:52
|
On Saturday 09 February 2008 23:20, Torsten Schlabach wrote: > > Use the msysdvlpr command to enter the MSYS Build Environment. > > I don't have that. This script is contained in > msysDVLPR-1.0.0-alpha-1.tar.gz which I am supposed to unpack to > /msys. But /msys/bin will only be on the PATH when I am already in > the MSYS build environment. Kind of a chicken and egg problem. No, that is not correct. You *must* first have installed MSYS, and be running it. You unpack msysDVLPR-1.0.0-alpha-1.tar.gz into the root of your existing MSYS tree, and your MSYS /bin directory will already be in the PATH, by virtue of you running MSYS. > I have passed some other issues and was able to do a successful > configure + make in my /msys directory. > > But where do I go from here? What have I built now? How can I install > this? I mean, do I know have some new .exe file which I can use to > setup my MSYS-snapshot environment? Perhaps if you explained your objective, we could offer better advice. Since you appear not to know what msysDVLPR is for -- it is exclusively for building and developing MSYS itself, *not* for general applications development -- then it is probable that you don't need it at all. If it *is* your intention to build components for MSYS itself -- all of which are dependent on msys-1.0.dll -- then what it provides you with is a specialised version of GCC and its associated tools, for building such components. Regards, Keith. |
From: Torsten S. <TSc...@gm...> - 2008-02-14 14:44:41
|
Dear Keith, > Perhaps if you explained your objective, we could offer better advice. Indeed, let's try: My objective is simple. I would like build this peace of software here on Windows: http://svn.openmoko.org/trunk/src/host/dfu-util/ (Description: http://wiki.openmoko.org/wiki/Dfu-util) This requires a more recent version of autotools than I can install using the .exe installers from the current version of MinGW + MSYS. I can spot the versions I need on SF in the Technology Preview releases, but I don't know how to get them installed. I tried downloading the .tar.bz2 files but that didn't do it. I am not sure, maybe I just have a dependency issue, i.e. automake >= 2.6 needs libxyz => X.Y, whatever. Therefore I thought compiling from source will help. I think I was suffering from the misconception that MSYS was something like a "Linux on Windows" system, i.e. it was comparable with a Linux distro. But I think I understood that basically MSYS is a shell (some kind of bash + terminal replacement) in order to be able to execute shell scripts which are often part of the build process of GNU / Linux flavor sources. This leaves me with the question: Does MSYS / MinGW have some kind of package management system like apt+dpkg or yum/YaST+rpm or the like? I found a reference to the Cygwin Setup tool which is talking about repositories, but my impression when using the MinGW installer or the MSYS installer is that they can only install what's built-in right now. I hope my objective did become clear. The easiest way of phrasing it would be: I need a MSYS+MinGW setup with recent autotools. Regards, Torsten -------- Original-Nachricht -------- > Datum: Thu, 14 Feb 2008 11:21:33 +0000 > Von: Keith Marshall <kei...@us...> > An: min...@li... > Betreff: Re: [Mingw-msys] Trying to build MSYS according to the Howto > On Saturday 09 February 2008 23:20, Torsten Schlabach wrote: > > > Use the msysdvlpr command to enter the MSYS Build Environment. > > > > I don't have that. This script is contained in > > msysDVLPR-1.0.0-alpha-1.tar.gz which I am supposed to unpack to > > /msys. But /msys/bin will only be on the PATH when I am already in > > the MSYS build environment. Kind of a chicken and egg problem. > > No, that is not correct. You *must* first have installed MSYS, and be > running it. You unpack msysDVLPR-1.0.0-alpha-1.tar.gz into the root of > your existing MSYS tree, and your MSYS /bin directory will already be > in the PATH, by virtue of you running MSYS. > > > I have passed some other issues and was able to do a successful > > configure + make in my /msys directory. > > > > But where do I go from here? What have I built now? How can I install > > this? I mean, do I know have some new .exe file which I can use to > > setup my MSYS-snapshot environment? > > Perhaps if you explained your objective, we could offer better advice. > Since you appear not to know what msysDVLPR is for -- it is exclusively > for building and developing MSYS itself, *not* for general applications > development -- then it is probable that you don't need it at all. If > it *is* your intention to build components for MSYS itself -- all of > which are dependent on msys-1.0.dll -- then what it provides you with > is a specialised version of GCC and its associated tools, for building > such components. > > Regards, > Keith. > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Mingw-msys mailing list > Min...@li... > https://lists.sourceforge.net/lists/listinfo/mingw-msys |
From: Johannes S. <Joh...@gm...> - 2008-02-14 15:03:55
|
Hi, On Thu, 14 Feb 2008, Torsten Schlabach wrote: > I think I was suffering from the misconception that MSYS was something > like a "Linux on Windows" system, i.e. it was comparable with a Linux > distro. You might want to use Cygwin instead. MingW is meant to compile programs as native Win32 programs, not as POSIX programs. With Cygwin, you get a POSIX emulation layer, which makes it trivial to "port" POSIX programs, at the cost of some runtime speed. Hth, Dscho |
From: Torsten S. <tsc...@gm...> - 2008-02-19 15:09:14
|
Johannes Schindelin wrote: > You might want to use Cygwin instead. MingW is meant to compile programs > as native Win32 programs, No, I don't want to use Cygwin. I want to produce a native Windows binary (myapp.exe) which any Windows user can download and run, without having to install Cygwin first. But in order to do that, I need an installation of MinGW + MSYS with a somewhat recent autotools; basically a version which I can see is available here: http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=67879 I just don't know how to install them as developers had waived the installer. Regards, Torsten |
From: Bruce S. <Bru...@nc...> - 2008-02-19 15:22:23
|
I got caught by this, too. You need to go to http://sourceforge.net/project/showfiles.php?group_id=2435 and then click on MSYS Supplementary Tools in the left column in order to find and download and install the current release of the developer's toolkit (currently msysDTK-1.0.1.exe). Scroll down past the "Technology Preview" stuff to the "Current Release" section. After installing msysDTK-1.0.1.exe, you need to download and install from the same source the following updates: msys-autoconf-2.59.2.59.tar.bz2 msys-automake-1.8.2.tar.bz2 msys-libtool-1.5.tar.bz2 Run MSYS, and cd to the folder where you have downloaded these .bz2 files and execute tar -xjf msys-autoconf-2.59.2.59.tar.bz2 tar -xjf msys-automake-1.8.2.tar.bz2 tar -xjf msys-libtool-1.5.tar.bz2 This will produce a bunch of folders (bin, lib, and so on). Copy these folders to c:\msys\1.0. Note that Windows merges on copy, so you can simply drag all the folders to c:\msys\1.0. Bruce Sherwood Torsten Schlabach wrote: > Johannes Schindelin wrote: >> You might want to use Cygwin instead. MingW is meant to compile programs >> as native Win32 programs, > > No, I don't want to use Cygwin. I want to produce a native Windows > binary (myapp.exe) which any Windows user can download and run, without > having to install Cygwin first. > > But in order to do that, I need an installation of MinGW + MSYS with a > somewhat recent autotools; basically a version which I can see is > available here: > > http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=67879 > > I just don't know how to install them as developers had waived the > installer. > > Regards, > Torsten > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Mingw-msys mailing list > Min...@li... > https://lists.sourceforge.net/lists/listinfo/mingw-msys |
From: Brian D. <br...@de...> - 2008-02-19 15:45:06
|
Torsten Schlabach wrote: > I just don't know how to install them as developers had waived the > installer. They're just tarballs. They extract into the root directory, e.g. tar jx -C / -f filename.tar.bz2. Note that with the autotools there are two "flavors": A) The MSYS-linked ones, which are to be used when *building* MSYS apps: autoconf-2.61-MSYS-1.0.11.tar.bz2 automake-1.10-MSYS-1.0.11.tar.bz2 libtool1.5-1.5.25a-20070701-MSYS-1.0.11.tar.bz2 libiconv-1.11-MSYS-1.0.11.tar.bz2 gettext-0.16.1-MSYS-1.0.11.tar.bz2 gettext-devel-0.16.1-MSYS-1.0.11.tar.bz2 These are the analogs to what you'd find in the old msysDVLPR bundle. These install in /usr. B) The "native" versions which install in /usr/local and are intended to be used when *building* MinGW apps: autoconf-4-1-bin.tar.bz2 autoconf2.1-2.13-3-bin.tar.bz2 autoconf2.5-2.61-1-bin.tar.bz2 automake-3-1-bin.tar.bz2 automake1.9-1.9.6-2-bin.tar.bz2 automake1.10-1.10-1-bin.tar.bz2 libtool1.5-1.5.25a-1-bin.tar.bz2 libtool1.5-1.5.25a-1-dll.tar.bz2 libiconv-1.11-1-bin.tar.bz2 libiconv-1.11-1-dll.tar.bz2 gettext-0.16.1-1-bin.tar.bz2 gettext-0.16.1-1-dll.tar.bz2 These come with wrapper scripts that do version detection, which allows for multiple versions to be installed side by side (i.e. all of the above work together.) References: http://sourceforge.net/project/shownotes.php?release_id=540763&group_id=2435 http://article.gmane.org/gmane.comp.gnu.mingw.user/23921 Brian |