emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: RFC: Cross compiling Emacs with qemu-user


From: Stefan Monnier
Subject: Re: RFC: Cross compiling Emacs with qemu-user
Date: Tue, 12 Dec 2017 15:34:20 -0500
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux)

> * In principle, would this be something Emacs would want to support?

I';ll let Eli and John chime in, but I don't see any reason why not.

> * What would need to be done to make the patch below acceptable?

Good question.  Some comments below.

>  EMACS = ${top_builddir}/src/emacs
> -emacs = EMACSLOADPATH= "${EMACS}" -batch --no-site-file --no-site-lisp
> +emacs = EMACSLOADPATH= ${EMACS} -batch --no-site-file --no-site-lisp

I'm not sure if Emacs can be built currently in a directory whose full
name includes spaces, but it's something that *should* work.  The above
would break it AFAICT, so we need some other solution.

> +AC_ARG_WITH([emulator],[AS_HELP_STRING([--with-emulator=EMULATOR],
> +    [Emulator to use when executing target binaries])],
> +    EMULATOR="$withval"
> +    AC_SUBST(EMULATOR))

It'd be good to make the doc slightly more precise (i.e. clarify that
it specifies an actual *command* rather than just which kind of
emulator we want to use).

> -RUN_TEMACS = ./temacs
> +RUN_TEMACS = temacs

Why did you need to get rid of the "./"?  It's needed to tell the shell
not to search through $PATH but in the cwd instead.

> -     $(MAKE) -C ../admin/unidata all EMACS="../$(bootstrap_exe)"
> +     $(MAKE) -C ../admin/unidata all EMACS="$(EMULATOR) $(bootstrap_exe)"

Hmm... how will $(EMULATOR) know to look in ../ ?


        Stefan




reply via email to

[Prev in Thread] Current Thread [Next in Thread]