building XFree86 from cvs

Michael Harnois mharnois@cpinternet.com
Tue Aug 20 08:07:00 GMT 2002


I have now searched my log ... the problem applies to lndir, rman, makestrs,
revpath, bitmap, bmtoa, atobm, proxymngr, xclipboard, xcutsel, xdm,
xdmshell, sessreg, chooser, xfindproxy, xinit, and xsm.

Michael D. Harnois
2L, University of St. Thomas School of Law
Minneapolis, Minnesota

-----Original Message-----
From: cygwin-xfree-owner@cygwin.com [mailto:cygwin-xfree-owner@cygwin.com]On
Behalf Of Harold Hunt
Sent: Tuesday, August 20, 2002 07:48
To: cygwin-xfree@cygwin.com
Subject: RE: building XFree86 from cvs

If that is the case then the Imakefile for xterm needs to be fixed because
some non-Cygwin programmer that has an empty ProgramTargetName macro
accidentally wrapped each target name in PROGRAMS with ProgramTargetName.
On their non-Cygwin platform this makes no difference, but on Cygwin this
makes a huge difference because our ProgramTargetName appends .exe to the
target name.  Thus, someone simply needs to remove the ProgramTargetName
wrappings from xterm's Imakefile and submit that as a patch.

Harold

> -----Original Message-----
> From: cygwin-xfree-owner@cygwin.com
> [mailto:cygwin-xfree-owner@cygwin.com]On Behalf Of Alexander Gottwald
> Sent: Tuesday, August 20, 2002 5:25 AM
> To: cygwin-xfree@cygwin.com
> Subject: RE: building XFree86 from cvs
>
>
> On Mon, 19 Aug 2002, Harold L Hunt wrote:
>
> > Do you understand what PROGS_EXE is for?  Do you understand why
> we cannot use
> > PROGRAMS?
>
> No.
> PROGS_EXE is simply all strings from PROGRAMS with .exe added. But
> the .exe is already added before ComplexTarget is called.
>
> So if eg. compiling xterm, PROGRAMS contains xterm.exe and PROGS_EXE the
> contains xterm.exe.exe
>
> bye
>       ago
> --
>  Alexander.Gottwald@informatik.tu-chemnitz.de
>  http://www.gotti.org           ICQ: 126018723
>



More information about the Cygwin-xfree mailing list