On 02/10/2014 05:05 PM, Adam Jiang wrote:
Actually, the problem could be resolved by
AM_CFLAGS = -DPKGDATA=$(pkgdata)
just like the manual described. Paths of all files in $(pkgdata) could be
referred with PKGDATA + basename.
AM_CFLAGS => automake
You are off-topic for this list
__
Actually, the problem could be resolved by
AM_CFLAGS = -DPKGDATA=$(pkgdata)
just like the manual described. Paths of all files in $(pkgdata) could be
referred with PKGDATA + basename.
Thank you.
2014-02-10 22:54 GMT+09:00 Eric Blake :
> On 02/09/2014 05:17 AM, Adam Jiang wrote:
> > Autoconf c
On 02/09/2014 05:17 AM, Adam Jiang wrote:
> Autoconf could help to generate configure script which accepts an option
> called --prefix in general. In this way, users could specific a path where
> programs/data installed.
ALL configure scripts generated by autoconf accept --prefix.
It sounds like
On 02/09/2014 10:17 PM, Adam Jiang wrote:
Autoconf could help to generate configure script which accepts an option
called --prefix in general. In this way, users could specific a path where
programs/data installed.
In my program, I'd like to refer the location where data files are
installed. In
On 02/09/2014 01:17 PM, Adam Jiang wrote:
Autoconf could help to generate configure script which accepts an option
called --prefix in general. In this way, users could specific a path where
programs/data installed.
In my program, I'd like to refer the location where data files are
installed. In
Autoconf could help to generate configure script which accepts an option
called --prefix in general. In this way, users could specific a path where
programs/data installed.
In my program, I'd like to refer the location where data files are
installed. In plain Makefile, it could be done like
gcc -