From: ayatakesi <ayanokoji.takesi@gmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: 66507-done@debbugs.gnu.org
Subject: bug#66507: 30.0.50; Cannot build some modules without adding LOCAL_EXPORT_CFLAGS=-isystem ... on Android port.
Date: Mon, 16 Oct 2023 02:35:32 +0900 [thread overview]
Message-ID: <ryxsf6biyaj.fsf@gmail.com> (raw)
In-Reply-To: <CAN7Wbib6DGLZxiCwfyn=w6sPa4A-9qDgq8V0ni-7pVPNfyoA0A@mail.gmail.com> (Takesi Ayanokoji's message of "Fri, 13 Oct 2023 15:40:27 +0900")
Hello, again
I tried LOCAL_EXPORT_C_INCLUDE_DIRS, and worked fine
except core/libpackagelistparser.
When I build libpackagelistparser, make failed with
/home/runner/work/my-emacs/my-emacs/my_sub_modules/core/libpackagelistparser//packagelistparser.c:30:10: fatal error: 'utils/Log.h' file not found
#include <utils/Log.h>
^~~~~~~~~~~~~
I cloned core package from Google, and I specify such bellow
directory structure:
core
|-libpackagelistparser
Android.mk
|-utils
|-include
Log.h
in Android.mk:
LOCAL_EXPORT_C_INCLUDE_DIRS += $(LOCAL_PATH)/../include
But LOCAL_EXPORT_C_INCLUDE_DIRS and LOCAL_EXPORT_C_INCLUDES
did not work except LOCAL_EXPORT_CFLAGS.
Takesi Ayanokoji <ayanokoji.takesi@gmail.com> writes:
> Hello,
>
> I will try LOCAL_EXPORT_C_INCLUDE_DIRS instead.
>
> Thanks,
>
> 2023年10月13日(金) 午後2:02 Po Lu <luangruo@yahoo.com>:
>
> Takesi Ayanokoji <ayanokoji.takesi@gmail.com> writes:
>
> > Hello Po- san.
> >
> > Unfortunately it doesn't seem to be mentioned in the
> java/INSTALL.
>
> I've now repaired these ommissions; that being said, I
> opted to
> recommend modifications to the Makefiles different from
> those you
> mentioned, for include paths are customarily exported
> through the
> variable LOCAL_EXPROT_C_INCLUDE_DIRS, not variables
> meant for exporting
> CFLAGS.
prev parent reply other threads:[~2023-10-15 17:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 21:17 bug#66507: 30.0.50; Cannot build some modules without adding LOCAL_EXPORT_CFLAGS=-isystem ... on Android port Takesi Ayanokoji
2023-10-13 1:06 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-13 4:30 ` Takesi Ayanokoji
2023-10-13 5:01 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-13 6:40 ` Takesi Ayanokoji
2023-10-15 17:35 ` ayatakesi [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ryxsf6biyaj.fsf@gmail.com \
--to=ayanokoji.takesi@gmail.com \
--cc=66507-done@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).