On 4/17/2012 19:37, MARTIN Pierre wrote:
> Dear least readers,
> On my discovery journey for mingw-w64, i have learnt that no MSYS build was automated. The solution is for me to either get a user build (i currently use SeZero's one, and it is working for me with MSYS) or to build the whole thing myself.
> On the other hand, i have learnt that Cygwin offers a repository with a pre-built mingw-w64 toolchain, which also did work for me (At least for building the few third-party software i required to link against). However, i am now aware of modern Cygwin path problems, and i feel like it can be a risk to have a production mingw-w64 on top of it.
Not really a risk, use the Cygwin provided toolchain, your build should
go well. Typically, you don't run any executables produced by the cross
> So, and as i like to have regular updates to my software, i am asking myself the following question: what would stop me from having a Cygwin installation with regularly updated mingw-w64, and on the side a MSYS installation having the Cygwin binary / libraries paths in the $PATH variables of the MSYS environment?
Do not mix MSYS and Cygwin, if you take the Cygwin route, make sure you
use the Cygwin provided toolchains through Cygwin setup.
> Would it be a good idea to do that? Or do you directly recommend to use Cygwin and workaround the paths problems when they appear? What do you guys use / prefer, and why please?
If your project builds some code generator/preprocessors (eg flex/bison
preprocessors), you should make it use the --build triplet compiler, not
the --host ones, since you'll need to run them at build time.
You should not need to deal with any PATH problems if you are using the
mingw-w64 install provided through Cygwin setup.