Akim Demaille wrote:
> | > Hm... I guess I'm not understanding the pun :-?
> |
> | Sorry. FAQ: Frequently Asked Questions
> | er -FAQ: Frequent Autoconf Questions
> |
> | So, I changed "Frequent Questions about Autoconf"
> | to "Frequent Autoconf Questions" to go along with
> | the "FAQ"
I tried to summarize the answers to this *very* FAQ. If people see
other things to put in the FAQ, please...
Index: ChangeLog
from Akim Demaille <[EMAIL PROTECTED]>
* doc/autoconf.texi (Questions): Rename as...
(FAQ): this.
(Defining Directories): New.
Index: doc/aut
Alexandre Duret-Lutz wrote:
> I've stopped hard-coding absolute paths in my package because it
> hinders relocation of binary packages.
>
> Instead, at configure-time (not everybody will like this) I turn
> each pathname into a path relative to $(prefix), and guess
> $(prefix) at run-time.
>
> S
> "GD" == Guido Draheim <[EMAIL PROTECTED]> writes:
GD> Es schrieb Viktor Pavlenko:
>>
>> Hello,
>>
>> I would like my program to know where it has been installed, in
>> particular, the location of $datadir. Looks like a natural way
>> to do it is to have a #defi
>>> "Earnie" == Earnie Boyd <[EMAIL PROTECTED]> writes:
Earnie> Alexandre Duret-Lutz wrote:
>>
>> for an example.
>>
>> (Obviously there are situation wheres computing relative paths is not
>> always possible -- think A:\foo C:\bar -- but I can live with that.)
Earnie> Why should this p
Alexandre Duret-Lutz wrote:
>
> for an example.
>
> (Obviously there are situation wheres computing relative paths is not
> always possible -- think A:\foo C:\bar -- but I can live with that.)
Why should this present problems?
Earnie.
>>> "Viktor" == Viktor Pavlenko <[EMAIL PROTECTED]> writes:
[...]
Viktor> I tried the following in configure.in:
Viktor> AC_DEFINE_UNQUOTED(MYPROG_DATA_DIR,$datadir,[myprog data directory])
Viktor> but it doesn't work ($prefix/share is inserted and not expanded). I
Viktor> would appreciate
> From: Viktor Pavlenko <[EMAIL PROTECTED]>
> Date: Wed, 4 Sep 2002 20:39:48 -0400
>
> I would like my program to know where it has been installed, in
> particular, the location of $datadir. Looks like a natural way to do
> it is to have a #define in config.h, like this:
>
> /*
> * myprog data
Es schrieb Viktor Pavlenko:
>
> Hello,
>
> I would like my program to know where it has been installed, in
> particular, the location of $datadir. Looks like a natural way to do
> it is to have a #define in config.h, like this:
>
> /*
> * myprog data directory
> */
> #define MYPROG_DATA_DIR "
| Hello,
| I would like my program to know where it has been installed, in
| particular, the location of $datadir. Looks like a natural way to do
| it is to have a #define in config.h, like this:
|
| /*
| * myprog data directory
| */
| #define MYPROG_DATA_DIR "/usr/local/share/myprog"
|
| I t
Viktor Pavlenko <[EMAIL PROTECTED]> writes:
> AC_DEFINE_UNQUOTED(MYPROG_DATA_DIR,$datadir,[myprog data directory])
[...]
> but it doesn't work ($prefix/share is inserted and not expanded). I
> would appreciate it if someone could tell me how to do this properly.
The following code works, but I c
Hello,
I would like my program to know where it has been installed, in
particular, the location of $datadir. Looks like a natural way to do
it is to have a #define in config.h, like this:
/*
* myprog data directory
*/
#define MYPROG_DATA_DIR "/usr/local/share/myprog"
I tried the following in
12 matches
Mail list logo
