Hi,
thanks for you quick replies.
On Fri, Sep 18, 2009 at 7:07 PM, Ralf Wildenhues wrote:
> * Steffen Dettmer wrote on Fri, Sep 18, 2009 at 12:19:19PM CEST:
> > But because of the tests it would not make much sense to do so, right?
> > So it is better to have dummy entry code I think.
> > Sorry
On Fri, Sep 18, 2009 at 7:11 PM, Ralf Wildenhues wrote:
> * Steffen Dettmer wrote on Fri, Sep 18, 2009 at 11:49:20AM CEST:
>>
>> Do I understand correctly that this was a temporary change that
>> had been undone?
>
> Well yes, a regression is a bug in a newer version
> When --build is omitted
Hi David,
On 9/19/2009 4:43 PM, David Bruce wrote:
I have a project with all the source files in a src directory just
below trunk, which is where the top level configure.ac and Makefile.am
live. When I run configure, config.h is created at build/config.h.
If I run configure from within trunk, m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey guys
I found a nice solution for this yet, but i have a project and trying
to find the nicest way to build and deploy with a config file, and
define the path to the file so as it isn't hard-coded. I know i could
just deploy a file with a bash redi
Philip Herron wrote:
I found a nice solution for this yet, but i have a project and trying
to find the nicest way to build and deploy with a config file, and
define the path to the file so as it isn't hard-coded. I know i could
just deploy a file with a bash redirect, and then AC_DEFINE the path,
* David Bruce wrote on Sun, Sep 20, 2009 at 12:43:54AM CEST:
> I have a project with all the source files in a src directory just
> below trunk, which is where the top level configure.ac and Makefile.am
> live. When I run configure, config.h is created at build/config.h.
> If I run configure from
* Steffen Dettmer wrote on Mon, Sep 21, 2009 at 10:24:26AM CEST:
> On Fri, Sep 18, 2009 at 7:07 PM, Ralf Wildenhues wrote:
> > * Steffen Dettmer wrote on Fri, Sep 18, 2009 at 12:19:19PM CEST:
> > > But because of the tests it would not make much sense to do so, right?
> > > So it is better to have
Hi Steffen,
>
> Could it be that you have multiple config.h files and the wrong is used?
>
That was it - basically, some of the project members like to build
with CMake instead of autotools, and a stray "config.h" got created
and saved in a location that mislead the compiler.
Thanks for the hel
