On Mon, Oct 30, 2000 at 09:18:42AM -0800, Ossama Othman wrote:
> Hi Gary,
>
> On Fri, Oct 27, 2000 at 08:44:40PM +0100, Gary V. Vaughan wrote:
> > Hmmm. I think that installing config.h is a bad idea under any
> > circumstances. I talk about this in some detail in the ``Project''
> > chapters o
On Tue, 31 Oct 2000, Simon Richter wrote:
> On Mon, 30 Oct 2000, Bob Friesenhahn wrote:
>
> > If we should not be installing config.h files, then it would be
> > beneficial for Automake (or Autoconf) to support an automated way to
> > provide the benefits of config.h, but in a better form.
>
>
On Mon, Oct 30, 2000 at 07:41:21PM -0600, Bob Friesenhahn wrote:
: If we should not be installing config.h files, then it would be
: beneficial for Automake (or Autoconf) to support an automated way to
: provide the benefits of config.h, but in a better form.
You can use the generated config.stat
On Mon, 30 Oct 2000, Bob Friesenhahn wrote:
> If we should not be installing config.h files, then it would be
> beneficial for Automake (or Autoconf) to support an automated way to
> provide the benefits of config.h, but in a better form.
How about the bin/-config approach: configure creates a s
Hi, Ossama.
Ossama Othman <[EMAIL PROTECTED]> writes:
> However, sometimes this can't be avoided in the case of inlined
> functions (e.g. C++). It isn't always feasible, particularly in
> terms of performance, to always keep function implementations hidden
> within the library. One could argue
On Mon, 30 Oct 2000, Ossama Othman wrote:
>
> On Tue, Oct 31, 2000 at 01:40:30AM +0100, Assar Westerlund wrote:
> > I would agree with Gary here that the symptom is installing the
> > config.h (or whatever it's called). The problem is that the interface
> > exported from the library should not d
Hi Assar,
On Tue, Oct 31, 2000 at 01:40:30AM +0100, Assar Westerlund wrote:
> I would agree with Gary here that the symptom is installing the
> config.h (or whatever it's called). The problem is that the interface
> exported from the library should not depend on the parameters found
> out by con
Ossama Othman <[EMAIL PROTECTED]> writes:
> If the macros placed in the package specific config.h are named so
> that they are specific to the given package then why is installing
> that header a problem.
I would agree with Gary here that the symptom is installing the
config.h (or whatever it's c
Hi Hari,
On Mon, Oct 30, 2000 at 11:51:10AM -0600, Raja R Harinath wrote:
> Ossama Othman <[EMAIL PROTECTED]> writes:
> > I'm not sure that I agree with you, though I confess that I probably
> > haven't thought about this issue as much as you. Please feel free to
> > correct me. :-)
>
> But, y
Ossama Othman <[EMAIL PROTECTED]> writes:
> On Fri, Oct 27, 2000 at 08:44:40PM +0100, Gary V. Vaughan wrote:
> > Hmmm. I think that installing config.h is a bad idea under any
> > circumstances. I talk about this in some detail in the ``Project''
> > chapters of the Goat Book (linked from my hom
Assar Westerlund wrote:
>
> Robert Boehne <[EMAIL PROTECTED]> writes:
> > I have a massive set of C++ libraries that use
> > CVS libtool, autoconf and automake to build and install.
> > Since users then need to have _all_ the header files
> > they also need to have the configure generated config.
Hi Gary,
On Fri, Oct 27, 2000 at 08:44:40PM +0100, Gary V. Vaughan wrote:
> Hmmm. I think that installing config.h is a bad idea under any
> circumstances. I talk about this in some detail in the ``Project''
> chapters of the Goat Book (linked from my homepages), and offer an
> ugly but functio
Some food for thought:
On Thu, Oct 26, 2000 at 02:20:10PM -0700, Ossama Othman wrote:
> Hi Alexandre,
>
> On Thu, Oct 26, 2000 at 07:13:28PM -0200, Alexandre Oliva wrote:
> > If you really want to have it installed, don't call it `config.h', or
> > at least install it in include/. To accomplish
Robert Boehne <[EMAIL PROTECTED]> writes:
> I have a massive set of C++ libraries that use
> CVS libtool, autoconf and automake to build and install.
> Since users then need to have _all_ the header files
> they also need to have the configure generated config.h
>
> What is the "best" way to coer
Simon Richter <[EMAIL PROTECTED]> writes:
> On 27 Oct 2000, Mark Galassi wrote:
> [Installing config.h]
>
> > But be careful: if any of the C code in the package itself includes
> > you might be in for a nasty surprise: if
> > a version is already installed and a user is compiling a new version
Hi,
On Fri, Oct 27, 2000 at 09:30:47PM +0200, Simon Richter wrote:
> On 27 Oct 2000, Mark Galassi wrote:
>
> [Installing config.h]
>
> > But be careful: if any of the C code in the package itself includes
> > you might be in for a nasty surprise: if
> > a version is already installed and a use
On 27 Oct 2000, Mark Galassi wrote:
[Installing config.h]
> But be careful: if any of the C code in the package itself includes
> you might be in for a nasty surprise: if
> a version is already installed and a user is compiling a new version
> from source, that user will pick up the installed .
>> And use `#include ' in all other
>> headers that include it.
Ossama> BTW, I do exactly what Alexandre suggests in some of my
Ossama> own packages. It works out quite nicely.
But be careful: if any of the C code in the package itself includes
you might be in for a nasty surp
Ossama Othman wrote:
>
> Hi Alexandre,
>
> On Thu, Oct 26, 2000 at 07:13:28PM -0200, Alexandre Oliva wrote:
> > If you really want to have it installed, don't call it `config.h', or
> > at least install it in include/. To accomplish
> > that, use:
> >
> > pkginclude_HEADERS = config.h ...
> >
>
Hi Alexandre,
On Thu, Oct 26, 2000 at 07:13:28PM -0200, Alexandre Oliva wrote:
> If you really want to have it installed, don't call it `config.h', or
> at least install it in include/. To accomplish
> that, use:
>
> pkginclude_HEADERS = config.h ...
>
> And use `#include ' in all other header
On Oct 26, 2000, Robert Boehne <[EMAIL PROTECTED]> wrote:
> Since users then need to have _all_ the header files
> they also need to have the configure generated config.h
> What is the "best" way to coerce Automake into installing
> config.h in $(prefix) ?
If you really want to have it installe
On Thu, 26 Oct 2000, Robert Boehne wrote:
[Finding libraries from other packages]
> What is the "best" way to coerce Automake into installing
> config.h in $(prefix) ?
Not at all. Instead, create m4 macros that search for the libraries
somehow and place them in ${datadir}/aclocal. A common sear
Hi Robert,
On Thu, Oct 26, 2000 at 01:32:42PM -0500, Robert Boehne wrote:
> I have a massive set of C++ libraries that use
> CVS libtool, autoconf and automake to build and install.
> Since users then need to have _all_ the header files
> they also need to have the configure generated config.h
>
I have a massive set of C++ libraries that use
CVS libtool, autoconf and automake to build and install.
Since users then need to have _all_ the header files
they also need to have the configure generated config.h
What is the "best" way to coerce Automake into installing
config.h in $(prefix) ?
-
24 matches
Mail list logo
