all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Engster <deng@randomsample.de>
To: "Vincent Belaïche" <vincent.b.1@hotmail.fr>
Cc: Eli Zaretskii <eliz@gnu.org>,
	"cedet-semantic@lists.sourceforge.net"
	<cedet-semantic@lists.sourceforge.net>,
	emacs-devel <emacs-devel@gnu.org>
Subject: Re: [cedet-semantic] Latest CEDET on BZR does not compile with emacs 24.1
Date: Sat, 06 Oct 2012 12:25:30 +0200	[thread overview]
Message-ID: <87pq4vc2xx.fsf@randomsample.de> (raw)
In-Reply-To: <DUB102-W26D04E7B09AF89E828C68684850@phx.gbl> ("Vincent \=\?iso-8859-1\?Q\?Bela\=EFche\=22's\?\= message of "Wed, 3 Oct 2012 22:02:37 +0200")

Vincent Belaïche writes:
> I am not going to re-write all the CEDET Makefiles just to use an
> MSWindows make engine. I've read from David that those Makefiles are
> generated by EDE, so if ever there was something to do, it would be
> better to upgrade EDE to generates those MSWindows makefile, or
> anything working well under MSWindows without the need for a Unixy
> shell (e.g. ant build.xml files).

Yes, that would be the way to go. You can generate pretty much any kind
of build script using EDE. In fact, if you look into our Elisp build
script cedet-build.el, you'll see that it also calls EDE to build the
targets without using Make. (It calls `project-compile-target' on the
target, which is an object; those methods are defined in
ede/proj-elisp.el and in semantic/ede-grammar.el for the
byte-compilation and parser generation, resp.).

> Anyhow, CEDET can be built with some lisp only script that will be
> soon fixed, so even this thing is not needed.

I think I fixed it now. Please check out latest CEDET from bzr and try

emacs -Q -l cedet-build.el -f cedet-build

Please let me know if you see any errors.

-David



  parent reply	other threads:[~2012-10-06 10:25 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <80627pfvx8.fsf@gmail.com>
     [not found] ` <DUB102-W64E66C3E35B19D545EE372849D0@phx.gbl>
     [not found]   ` <87k3vhesof.fsf@randomsample.de>
     [not found]     ` <DUB102-W11A887FEC4D1B295EE9797849C0@phx.gbl>
     [not found]       ` <877grgdmcd.fsf@randomsample.de>
     [not found]         ` <DUB102-W3A224ABBF13767707549184830@phx.gbl>
     [not found]           ` <87mx0bcioh.fsf@randomsample.de>
     [not found]             ` <DUB102-W9B28CE0238E27638C391684800@phx.gbl>
     [not found]               ` <87sj9yb4kw.fsf@randomsample.de>
2012-10-02 20:31                 ` Latest CEDET on BZR does not compile with emacs 24.1 Vincent Belaïche
2012-10-02 21:10                   ` [cedet-semantic] " Eli Zaretskii
2012-10-03 20:02                     ` Vincent Belaïche
2012-10-03 20:28                       ` Eli Zaretskii
2012-10-05  5:18                         ` Vincent Belaïche
2012-10-05  8:10                           ` [cedet-semantic] " Eli Zaretskii
2012-10-06 21:41                             ` Vincent Belaïche
2012-10-07  7:06                               ` Eli Zaretskii
2012-10-07 12:29                                 ` Vincent Belaïche
2012-10-07 14:28                                   ` Eli Zaretskii
2012-10-07  7:52                         ` Vincent Belaïche
2012-10-07  8:42                           ` Eli Zaretskii
2012-10-07 11:49                             ` Vincent Belaïche
2012-10-07 14:18                               ` Eli Zaretskii
2012-10-07 16:37                                 ` Vincent Belaïche
2012-10-07 17:07                                   ` Eli Zaretskii
2012-10-07 19:36                                     ` Vincent Belaïche
2012-10-06 10:25                       ` David Engster [this message]
2012-10-06 19:47                         ` Vincent Belaïche
2012-10-06 19:56                           ` David Engster
2012-10-06 20:11                             ` Vincent Belaïche
2012-10-02 21:57                   ` David Engster

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pq4vc2xx.fsf@randomsample.de \
    --to=deng@randomsample.de \
    --cc=cedet-semantic@lists.sourceforge.net \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=vincent.b.1@hotmail.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.