Hi, I'm having trouble finding an answer to this question:
My team is trying to use automake for a C++ project we are developing.
The project design has been changing rapidly and we are finding that
keeping the list of source files in Makefile.am up to sync with the
contents of the directory is v
On Wed, 17 Nov 2004, Jonathan wrote:
Hi, I'm having trouble finding an answer to this question:
My team is trying to use automake for a C++ project we are developing.
The project design has been changing rapidly and we are finding that
keeping the list of source files in Makefile.am up to sync with
My autoconf/automake project is optimizing by default with "-g -O2".
Unfortunately, we have verified that this is causing a run-time error
by overriding CXXFLAGS in Makefile.am with just "-g". With the "-O2"
flag removed, everything works great.
I have been trying to find out where this "-O2" is
How do I disable the "-O2" flag in the most portable way possible?
I am just learning, I am no authority. But, I would do it at configure time:
'CXXFLAGS=-O0' 'CFLAGS=-O0'
If you have some *file* that needs some specific flag, you could set it
in your Makefile.am. I think it would be something li
On Wed, 2004-11-17 at 18:48 -0500, Jonathan wrote:
> My autoconf/automake project is optimizing by default with "-g -O2".
> Unfortunately, we have verified that this is causing a run-time error
> by overriding CXXFLAGS in Makefile.am with just "-g". With the "-O2"
> flag removed, everything works
Hello,
On Wed, Nov 17, 2004 at 08:01:45PM -0500, Braden McDaniel wrote:
> if test -n "${CXXFLAGS}"; then
> user_set_cxxflags=yes
> fi
> AC_PROG_CXX
> if test X$user_set_cxxflags != Xyes; then
> CXXFLAGS="-g"
> fi
out of curiosity, what w
Hello.
On Wed, Nov 17, 2004 at 01:14:05PM -0600, Bob Friesenhahn wrote:
> Automake developers feel that package
> developers should be more careful/responsible than to build and
> distribute whatever files happen to be available.
A friend of mine told me that it took him quite a long time until
