Re: MS-Windows build using Posix configury

[Dani Moncayo]

>> The packages I've installed (with "mingw-get install <package>"), in
>> addition to the ones installed by default, are:
>> * msys-base
>> * mingw-developer-toolkit
>> * msys-automake
>
> What do you mean by "installed by default"?  If we want the
> instructions to be comprehensive, we need to spell out _all_ of the
> packages, including those installed by default.

By "packages installed by default", I mean the packages that get
installed if you install MinGW (with the "mingw-get-inst-20120426.exe"
installer) and accept the default options in the wizard.

Sorry, I've not found a way to get the list of installed packages
(AFAICT, the package manager currently lacks such a feature).

>> The configuration command is successful too:
>>   $ CPPFLAGS='-DGLYPH_DEBUG=1' CFLAGS='-O0 -g3'
>> ../mybranch/nt/msysconfig.sh --prefix=c:/usr --enable-checking
>> --without-all
>
> Why --without-all?  You do have the image libraries, right?

Yes, I have image libraries, but I wanted to try first a simple build,
to make sure that a botched library setup is not the culprit of any
build failure.

>>   make[2]: Entering directory `/c/emacs/build/nt'
>>   windres -O coff -o emacs.res emacs.rc
>>   gcc: error: emacs.rc: No such file or directory
>>   gcc: warning: '-x c' after last input file has no effect
>>   gcc: fatal error: no input files
>>   compilation terminated.
>>   c:\MinGW\bin\windres.exe: preprocessing failed.
>>   make[2]: *** [emacs.res] Error 1
>>   make[2]: Leaving directory `/c/emacs/build/nt'
>>   make[1]: *** [nt] Error 2
>>   make[1]: Leaving directory `/c/emacs/build'
>>   make: *** [bootstrap] Error 2
>>
>>
>> What might the problem be?
>
> It's a bug (I didn't yet try to build outside of the source tree, so I
> didn't hit it).  Change this line in nt/Makefile.in:
>
>         ${WINDRES} -O coff -o emacs.res emacs.rc
>
> to say this instead:
>
>         ${WINDRES} -O coff -o emacs.res ${srcdir}/emacs.rc
>
> Btw, you don't need to say "make bootstrap" with this setup, unless
> you want to force a bootstrap.  Just "make" will do whatever it takes
> to build Emacs, and will bootstrap if needed.

Ok, I've done the above change, and now a plain "make" ends up failing here:

  [...]
  creating src/epaths.h
  make[1]: Entering directory `/c/emacs/build'
  make[1]: Leaving directory `/c/emacs/build'
  config.status: executing gdbinit commands
  [ -r "/c/emacs/mybranch/src/config.in" ] || ( cd /c/emacs/mybranch
&& autoheader
   )
  cd nt && make all                          \
            CC='gcc  -std=gnu99' CFLAGS='-O0 -g3'
CPPFLAGS='-mtune=pentium4  -DGLY
  PH_DEBUG=1 -DUSE_CRT_DLL=1 -I /c/emacs/mybranch/nt/inc' \
            LDFLAGS='' MAKE='make'
  make[1]: Entering directory `/c/emacs/build/nt'
  windres -O coff -o emacs.res /c/emacs/mybranch/nt/emacs.rc
  gcc  -std=gnu99 -mtune=pentium4    -I. -I/c/emacs/mybranch/nt
-mtune=pentium4
   -DGLYPH_DEBUG=1 -DUSE_CRT_DLL=1 -I /c/emacs/mybranch/nt/inc -O0 -g3
/c/emacs/my
  branch/nt/runemacs.c emacs.res \
           -o runemacs.exe
  make[1]: *** No rule to make target
`/c/emacs/mybranch/nt/../src/epaths.h', need
  ed by `addpm.exe'.  Stop.
  make[1]: Leaving directory `/c/emacs/build/nt'
  make: *** [nt] Error 2



--
Dani Moncayo