Content-Type: multipart/alternative; boundary="_a96d4553-a815-470a-8c41-390c59f560ab_" --_a96d4553-a815-470a-8c41-390c59f560ab_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable > Date: Tue=2C 2 Oct 2012 23:10:31 +0200 > From: eliz@gnu.org > Subject: Re: [cedet-semantic] Latest CEDET on BZR does not compile with e= macs 24.1 > To: vincent.b.1@hotmail.fr > CC: cedet-semantic@lists.sourceforge.net=3B deng@randomsample.de=3B emacs= -devel@gnu.org >=20 > > From: Vincent Bela=EFche > > CC: "cedet-semantic@lists.sourceforge.net" > > =2C emacs-devel [... SNIP ...]>=20 > I suggest not to use MSYS at all. =20 Is that a general recommendation --- i.e. do not build EMACS with MSYS --- = or is that a recommendation for CEDET only. It happens that I could not com= pile EMACS with MSYS for some time --- is the MSYS port abandoned ? > If the original CEDET Makefile's > cannot be changed to not require a Unixy shell=2C=20 The only MSWindows port of GNUMake which I know is the MSYS one. Cygwin is = not really a Windows port=2C it is rather some Unixy environment emulation = under MSWindows. I tried the Makefile with dmake and here is what it does: C:\Programme\GNU\installation\cedet-install\cedet>dmake EMACS=3Dc:\Programm= e\GNU\emacs-24.1\bin\emacs.exe=20 dmake EMACS=3Dc:\Programme\GNU\emacs-24.1\bin\emacs.exe=20 dmake.exe: makefile: line 46: Error: -- Missing targets or attributes in= rule i.e. it seems that dmake is less advanced than GNU Make and does not suppor= t addsufix function.=20 > write a separate > Windows specific Makefile with equivalent commands=2C and be done with > that. =20 I am afraid that the trick which I did is tremendously simpler to do and to= maintain than what I understood that you are suggesting. I am not going to= re-write all the CEDET Makefiles just to use an MSWindows make engine. I'v= e read from David that those Makefiles are generated by EDE=2C so if ever = there was something to do=2C it would be better to upgrade EDE to generates= those MSWindows makefile=2C or anything working well under MSWindows witho= ut the need for a Unixy shell (e.g. ant build.xml files). Anyhow=2C CEDET c= an be built with some lisp only script that will be soon fixed=2C so even t= his thing is not needed. > As a bonus=2C latest native ports of GNU Make support all the > functions that you needed to replace. You can even replace Sed > commands with equivalent GNU Make functions=2C if you want. > Thank you for the advice=2C I totally agree with this one=2C Makefile inter= nal text & path manipulation should be done as much as possible platform in= dependent.I attached a corrected `platform.mak' which does not use sed but = only GNU make functions. You are right=2C sed is a little old fashioned and= not always available. > MSYS is for configuring and building packages that use Autoconf and > other autotools. It is not really appropriate for arbitrary Windows > jobs. It can be done=2C of course=2C as your patch demonstrates=2C but i= t > will be fragile=2C and requires MSYS to be installed=2C which is a large > set of packages. >=20 Well=2C I have already MSYS installed=2C so I did not need any extra instal= lation=2C while using Cygwin was the opposite in my case=2C that would have= meant installing a large package. Kind regards=2C Vincent. = --_a96d4553-a815-470a-8c41-390c59f560ab_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

>=3B Date: Tue=2C 2 Oct 2012 23:10:31 +0200
>=3B From: = eliz@gnu.org
>=3B Subject: Re: [cedet-semantic] Latest CEDET on BZR do= es not compile with emacs 24.1
>=3B To: vincent.b.1@hotmail.fr
>= =3B CC: cedet-semantic@lists.sourceforge.net=3B deng@randomsample.de=3B ema= cs-devel@gnu.org
>=3B
>=3B >=3B From: Vincent Bela=EFche <= =3Bvincent.b.1@hotmail.fr>=3B
>=3B >=3B CC: "cedet-semantic@lists.= sourceforge.net"
>=3B >=3B <=3Bcedet-semantic@lists.sourceforge.n= et>=3B=2C emacs-devel <=3Bemacs-devel@gnu.org>=3B

<= /div>
[... SNIP ...]
>=3B =3B
>=3B I suggest not t= o use MSYS at all.

Is that a general recommendat= ion --- i.e. do not build EMACS with MSYS --- or is that a recommendation f= or CEDET only. It happens that I could not compile EMACS with MSYS for some= time --- is the MSYS port abandoned ?

>=3B If t= he original CEDET Makefile's
>=3B cannot be changed to not require a U= nixy shell=2C

The only MSWindows port of GNUMake = which I know is the MSYS one. Cygwin is not really a Windows port=2C it is = rather some Unixy environment emulation under MSWindows.

I tried the Makefile with dmake and here is what it does:
=
C:\Programme\GNU\installation\cedet-install\cedet>=3Bdmake= EMACS=3Dc:\Programme\GNU\emacs-24.1\bin\emacs.exe
dmake EMACS=3Dc:\Pro= gramme\GNU\emacs-24.1\bin\emacs.exe
dmake.exe: makefile: line 46: Er= ror: -- Missing targets or attributes in rule

= i.e. it seems that dmake is less advanced than GNU Make and does not suppor= t addsufix function. =3B

>=3B write a separa= te
>=3B Windows specific Makefile with equivalent commands=2C and be d= one with
>=3B that.

I am afraid that the tr= ick which I did is tremendously simpler to do and to maintain than what I u= nderstood that you are suggesting. I am not going to re-write all the CEDET= Makefiles just to use an MSWindows make engine. I've =3B read from Dav= id that those Makefiles are generated by EDE=2C so if ever there was someth= ing to do=2C it would be better to upgrade EDE to generates those MSWindows= makefile=2C or anything working well under MSWindows without the need for = a Unixy shell (e.g. ant build.xml files). Anyhow=2C CEDET can be built with= some lisp only script that will be soon fixed=2C so even this thing is not= needed.

>=3B As a bonus=2C latest native ports = of GNU Make support all the
>=3B functions that you needed to replace.= You can even replace Sed
>=3B commands with equivalent GNU Make func= tions=2C if you want.
>=3B

Thank you for the = advice=2C I totally agree with this one=2C Makefile internal text &=3B p= ath manipulation should be done as much as possible platform independent.
I attached a corrected `platform.mak' which does not use sed but o= nly GNU make functions. You are right=2C sed is a little old fashioned and = not always available.

>=3B MSYS is for configuring and buil= ding packages that use Autoconf and
>=3B other autotools. It is not r= eally appropriate for arbitrary Windows
>=3B jobs. It can be done=2C = of course=2C as your patch demonstrates=2C but it
>=3B will be fragile= =2C and requires MSYS to be installed=2C which is a large
>=3B set of = packages.
>=3B

Well=2C I have already MSYS i= nstalled=2C so I did not need any extra installation=2C while using Cygwin = was the opposite in my case=2C that would have meant installing a large pac= kage.

Kind regards=2C
=3B  =3BVincent.
= --_a96d4553-a815-470a-8c41-390c59f560ab_--