Re: [Tinycc-devel] tcc compilation on MSYS2

[Sergey Korshunoff]

@avih
> apparently there have been some build system changed between December and now

yes, the same is on my branch. A problem is exposed after my commit
  commit 7ed43415380ec6270e53c0ed3f42e5cb99df1f6e
  Author: seyko <address@hidden> //////////////////////////////////// bad
  Date:   Wed Mar 4 10:57:13 2015 +0300
   a libraries paths
        * x86_64-tcc: use /usr/lib64,.. instead of /usr/lib,..
        * don't set tcc_lddir="lib64" if cpu="x86"

--- a/configure
+++ b/configure
     if test x"$bindir" = x""; then
     bindir="${execprefix}/bin"
     fi
-    if test x"$tccdir" = x""; then
-    tccdir="tcc"
-    fi
     if test x"$docdir" = x""; then
     docdir="${sharedir}/doc/${tccdir}"
     fi

Then the right fix must be
-     docdir="${sharedir}/doc/${tccdir}"
+    docdir="${sharedir}/doc/tcc"

> Chris Marshall wrote: ---
> To be more specific, it should be possible to build the mingw version of tcc 
> on cygwin (I don't > know, haven't had time to try) but what I would like is 
> the linux/unix version---if it builds on
> unix, it should be buildable on cygwin---as long as you don't look under the 
> covers to find
> windows.

> gr
> Probably you could do that.  It is just that you'll find that
> such (almost true) linux/unix version of tcc will produce
> (entirely) true linux/unix programs.  And these will not
> run on windows, not even under cygwin.

I'm trying to do that, i.e MSYS2 unix. A big issue is not to define
_WIN32 which assume standalone mingw (tcc headers/libraries in
C:\Program Files\tcc) w/o MSYS2. mingw on MSYS2 can be different too
because there is all headers and libraries already present.

Executable names:
MSYS2:
  i386-tcc.exe
  x86_64-tcc.exe

Mingw on MSYS2 or standalone tcc installation:
  i386-win-tcc.exe
  x86_64-win-tcc.exe

By default target will be selected depending on msys2 shell
environment (MSYS2 or Mingw on MSYS2).