* Jef Driesen wrote on Wed, Mar 17, 2010 at 01:23:09PM CET:
> On 16/03/2010 14:22, Peter Johansson wrote:
> >Which method to use depends on where you want the MY_REVISION_VERSION to
> >propagate. Do you need it in any Makefiles, e.g., or do you only need it
> >compiled into your program.
>
> I onl
Hi Jef,
On 3/17/10 8:23 AM, Jef Driesen wrote:
I only need it compiled into my library. The goal is that an
application using my library can report the exact revision of the
library (for diagnostic purpose).
With the solution I outlined in my previous posts, I can already get
the "normal" ve
On 16/03/2010 14:22, Peter Johansson wrote:
On 3/16/10 8:29 AM, Jef Driesen wrote:
On 15/03/2010 22:18, Ralf Wildenhues wrote:
* Jef Driesen wrote on Sat, Mar 13, 2010 at 11:21:45PM CET:
I suppose you are referring to solutions like this:
m4_define([mylib_version_revision],m4_esyscmd([my_rev
On 3/16/10 8:29 AM, Jef Driesen wrote:
On 15/03/2010 22:18, Ralf Wildenhues wrote:
* Jef Driesen wrote on Sat, Mar 13, 2010 at 11:21:45PM CET:
I suppose you are referring to solutions like this:
m4_define([mylib_version_revision],m4_esyscmd([my_revision_script]))
where the revision script fe
On 15/03/2010 22:18, Ralf Wildenhues wrote:
* Jef Driesen wrote on Sat, Mar 13, 2010 at 11:21:45PM CET:
For instance, I prefer to have:
typedef foobar ticks_t;
instead of:
#define ticks_t foobar
It might be possible to achieve the same with AC_CONFIG_HEADERS, but
I don't know how. I had a lo
* Jef Driesen wrote on Sat, Mar 13, 2010 at 11:21:45PM CET:
> On 13/03/10 11:34, Ralf Wildenhues wrote:
> >You are using a AC_CONFIG_FILES now instead of a AC_CONFIG_HEADERS.
> >That's fine per se, but config files are updated unconditionally by
> >config.status, meaning that the updated timestamp
On 13/03/10 11:34, Ralf Wildenhues wrote:
* Jef Driesen wrote on Mon, Mar 08, 2010 at 02:10:04PM CET:
On 02/03/10 22:17, Ralf Wildenhues wrote:
Hmm, put
AC_CONFIG_HEADERS([config.h foo-api.h])
...
AC_DEFINE([ticks_t], [...], [...])
in configure.ac, create foo-api.h.in with contents
* Jef Driesen wrote on Mon, Mar 08, 2010 at 02:10:04PM CET:
> On 02/03/10 22:17, Ralf Wildenhues wrote:
> >Hmm, put
> > AC_CONFIG_HEADERS([config.h foo-api.h])
> > ...
> > AC_DEFINE([ticks_t], [...], [...])
> >
> >in configure.ac, create foo-api.h.in with contents
> > /* Public API header o
On 02/03/10 22:17, Ralf Wildenhues wrote:
* Jef Driesen wrote on Tue, Mar 02, 2010 at 10:03:35PM CET:
On 01/03/10 19:35, Ralf Wildenhues wrote:
* Jef Driesen wrote on Mon, Mar 01, 2010 at 01:33:46PM CET:
Since a config.h header files is not supposed to be public, that's
not an option. But how
On 3/3/2010 12:53 PM, Russ Allbery wrote:
John Calcote writes:
While I agree that standards should be followed, I find this one
distasteful. I mean, "long long"? Is that supposed to be someone's idea
of a scalable solution? What happens when we have 128-bit systems? Dare
I venture: "long l
John Calcote writes:
> While I agree that standards should be followed, I find this one
> distasteful. I mean, "long long"? Is that supposed to be someone's idea
> of a scalable solution? What happens when we have 128-bit systems? Dare
> I venture: "long long long"? And please don't say we'll nev
Sorry - I addressed this note to Jef. It should have gone to Ben. My
apologies.
On 3/3/2010 12:16 PM, John Calcote wrote:
Hi Jef,
On 3/3/2010 11:53 AM, Ben Pfaff wrote:
Jef Driesen writes:
It works fine for every system I have access too, but long long is not
standard and thus not guarante
Hi Jef,
On 3/3/2010 11:53 AM, Ben Pfaff wrote:
Jef Driesen writes:
It works fine for every system I have access too, but long long is not
standard and thus not guaranteed to be present. So I just want to make
sure it will work on other systems too.
"long long" has been standard for
Jef Driesen writes:
> It works fine for every system I have access too, but long long is not
> standard and thus not guaranteed to be present. So I just want to make
> sure it will work on other systems too.
"long long" has been standard for 11 years now. It is irritating
that some vendors have
* Jef Driesen wrote on Tue, Mar 02, 2010 at 10:03:35PM CET:
> On 01/03/10 19:35, Ralf Wildenhues wrote:
> >* Jef Driesen wrote on Mon, Mar 01, 2010 at 01:33:46PM CET:
> >>Since a config.h header files is not supposed to be public, that's
> >>not an option. But how can I do this correctly?
> >
> >Us
On 01/03/10 19:35, Ralf Wildenhues wrote:
Hello Jef,
* Jef Driesen wrote on Mon, Mar 01, 2010 at 01:33:46PM CET:
How do I get information generated by autotools into my public
header files? For instance I want to define version numbers
somewhere in my configure.ac file, and have the same
Hello Jef,
* Jef Driesen wrote on Mon, Mar 01, 2010 at 01:33:46PM CET:
> How do I get information generated by autotools into my public
> header files? For instance I want to define version numbers
> somewhere in my configure.ac file, and have the same numbers appear
> in a public
On Mon, Mar 1, 2010 at 7:33 AM, Jef Driesen wrote:
> Hi,
>
> How do I get information generated by autotools into my public header files?
> For instance I want to define version numbers somewhere in my configure.ac
> file, and have the same numbers appear in a public header file w
Hi,
How do I get information generated by autotools into my public header
files? For instance I want to define version numbers somewhere in my
configure.ac file, and have the same numbers appear in a public header
file without having to modify both files manually? Another example is
that my
19 matches
Mail list logo
