HI all,
Automake provides targets for generating the distributions of the
software with dist-bzip2 and dist-gzip however it will not keep the
structure of src directory. I wonder how to work with projects with
hundreds of files. Do you have them all in a plain src dir or you
ignore dist-bzip2 and
On 29/03/06, Stepan Kasal <[EMAIL PROTECTED]> wrote:
> Hello,
>
> On Wed, Mar 29, 2006 at 11:33:37AM +0100, Paulo J. Matos wrote:
> > software with dist-bzip2 and dist-gzip however it will not keep the
> > structure of src directory.
>
> it keeps the structure.
lo,
On Wed, Mar 29, 2006 at 11:33:37AM +0100, Paulo J. Matos wrote:
> software with dist-bzip2 and dist-gzip however it will not keep the
> structure of src directory.
it keeps the structure. But it distributes only the files mentioned
in Makefile.am. For details, please see the man
On 03/04/06, Ralf Wildenhues <[EMAIL PROTECTED]> wrote:
> Hi Paulo,
>
> * Paulo J. Matos wrote on Mon, Apr 03, 2006 at 06:29:19PM CEST:
> > I'm having a problem with dist-bzip2 since on my makefile I have :
> > VPATH %.cc ./x ./xx ./xxx ...
> >
> >
On 03/04/06, Paulo J. Matos <[EMAIL PROTECTED]> wrote:
> On 03/04/06, Ralf Wildenhues <[EMAIL PROTECTED]> wrote:
> > Hi Paulo,
> >
> > * Paulo J. Matos wrote on Mon, Apr 03, 2006 at 06:29:19PM CEST:
> > > I'm having a problem with dist-bzip2 since on
ATT: Cross-sent to automake and autoconf MLs since problem spans both
worlds, I think!
Hi all,
I'm currently using autoconf for the for my libraries with
AC_CHECK_LIB, and to generate static binaries I do everytime I
configure:
./configure LDFLAGS="-static"
However, in google groups:
http://gro
On 29/04/06, Ralf Wildenhues <[EMAIL PROTECTED]> wrote:
Hi Paulo,
* Paulo J. Matos wrote on Sat, Apr 29, 2006 at 01:15:47PM CEST:
> ATT: Cross-sent to automake and autoconf MLs since problem spans both
> worlds, I think!
Do you use Libtool? Then it would probably a Libtool q
Hi all,
I have a source tree, which is maintained with autotools. It goes
something like this:
MySoftware
|- lib
|- lib1
|- lib2
|- src
lib1 and lib2 are compiled and then linked to the src software.
However, I've just developed a logger utility interface which uses
log4cpp and I w
On 11/05/06, Warren Young <[EMAIL PROTECTED]> wrote:
Paulo J. Matos wrote:
> I see two ways: Creating yet another library and then link it with
> lib1 and lib2 and later link to the main code lib1, lib2 and
> liblogger.
That's what I do.
Thanks for all your replies. I
On 12/05/06, Ralf Wildenhues <[EMAIL PROTECTED]> wrote:
Hi Paulo,
* Paulo J. Matos wrote on Fri, May 12, 2006 at 12:22:59AM CEST:
>
> I've created liblogger basically as a new project with configure.ac
> and Makefile.am, etc. It builds ok and then I added to Makefile.am of
On 12/05/06, Paulo J. Matos <[EMAIL PROTECTED]> wrote:
How can I do that? I don't think I ensured that.
Hi, I just changed lib1/Makefile.am to:
SUBDIRS = ../../liblogger src
Now it is making liblogger before but still I get the same nasty error
from make. :-(
make[2]: *** No r
On 12/05/06, Paulo J. Matos <[EMAIL PROTECTED]> wrote:
Now it is making liblogger before but still I get the same nasty error
from make. :-(
make[2]: *** No rule to make target
`../../liblogger/src/liblogger.la', needed by `lib1.la'. Stop.
Argh, it should be ../../
On 12/05/06, Warren Young <[EMAIL PROTECTED]> wrote:
Paulo J. Matos wrote:
>
> I've created liblogger basically as a new project with configure.ac
> and Makefile.am, etc. It builds ok and then I added to Makefile.am of
> both lib1 and lib2:
> lib1_la_LIBADD = ../../
On 12/05/06, Paulo J. Matos <[EMAIL PROTECTED]> wrote:
Ah, that's most probably what I need. Thanks a lot!
After reading the chapter you mentioned and browsing the rest of the
very nice book I implemented things that way and set up the structure
(I'll forget li
Hi all,
I'd like to know what's the best way to pass some options to the linker?
I'd like to add -Wl,--whole-archive to the linker before the libraries
I want to link, which are listed in LIBADD. Any ideas on how to do
this?
This is needed due to some conclusions I referred in:
http://groups.goo
On 24/05/06, Ralf Wildenhues <[EMAIL PROTECTED]> wrote:
Hi Paulo,
* Paulo J. Matos wrote on Wed, May 24, 2006 at 05:34:50PM CEST:
>
> I'd like to know what's the best way to pass some options to the linker?
> I'd like to add -Wl,--whole-archive to the linker be
On 24/05/06, Ralf Wildenhues <[EMAIL PROTECTED]> wrote:
* Ralf Wildenhues wrote on Wed, May 24, 2006 at 05:40:43PM CEST:
> * Paulo J. Matos wrote:
>
> > This is needed due to some conclusions I referred in:
> >
http://groups.google.com/group/gnu.g++.help/browse_frm
On 24/05/06, Paulo J. Matos <[EMAIL PROTECTED]> wrote:
No, it is still not working. If we concentrate ourselves only in the
first situations where I want the libraries to be all linked
statically I have for the core:
bin_PROGRAMS = extsat
extsat_SOURCES = esatmathcluster.cc ...
extsat_L
On 24/05/06, Paulo J. Matos <[EMAIL PROTECTED]> wrote:
On 24/05/06, Paulo J. Matos <[EMAIL PROTECTED]> wrote:
> No, it is still not working. If we concentrate ourselves only in the
> first situations where I want the libraries to be all linked
> statically I have for the
On 24/05/06, Ralf Wildenhues <[EMAIL PROTECTED]> wrote:
* Ralf Wildenhues wrote on Wed, May 24, 2006 at 05:40:43PM CEST:
> * Paulo J. Matos wrote:
>
> > This is needed due to some conclusions I referred in:
> >
http://groups.google.com/group/gnu.g++.help/browse_frm
Hi all,
In: http://sources.redhat.com/automake/automake.html#Conditionals
AC_ARG_ENABLE(debug,
[ --enable-debugTurn on debugging],
[case "${enableval}" in
yes) debug=true ;;
no) debug=false ;;
*) AC_MSG_ERROR(bad value ${enableval} for --enable-debug) ;;
esac]
Thank you all for your help on this issue. Now everything seems to fit
in the right place. :-D
--
Paulo Jorge Matos - pocm at sat inesc-id pt
Web: http://sat.inesc-id.pt/~pocm
Computer and Software Engineering
INESC-ID - SAT Group
Hi all,
I'm getting a directory autom4te.cache in my tree with big files in
it, how can I remove this? make clean won't help. Problem is haven't
noticed them and they are getting into cvs. :-(
Cheers,
--
Paulo Jorge Matos - pocm at sat inesc-id pt
Web: http://sat.inesc-id.pt/~pocm
Computer and S
On 05/08/06, Stepan Kasal <[EMAIL PROTECTED]> wrote:
BTW, autom4te is part of the Autoconf, so if you have more questions,
please direct them to [EMAIL PROTECTED]
Thanks a lot for the explanation. I'm sorry I have send it to automake
but regularly I just don't know what's the correct mailing
Hi all,
I'm trying to override -g -O2 CXXFLAGS set up by default but I'm quite
confused on how to do this. I have specific _CXXFLAGS setup, I have
also tried to setup AM_CXXFLAGS to empty but still those god damn
flags show up when compiling and linking. How can I make them go away?
Regards,
--
On 11/13/06, Paulo J. Matos <[EMAIL PROTECTED]> wrote:
Hi all,
I'm trying to override -g -O2 CXXFLAGS set up by default but I'm quite
confused on how to do this. I have specific _CXXFLAGS setup, I have
also tried to setup AM_CXXFLAGS to empty but still those god damn
fl
Hello,
I'm quite curious how can I with autotools integrate a code generator
during the make process. For example:
a generator receives as input .gen files and produces .hh files which
are then used for compilation. How can I integrate this generator by
running the program in all .gen files and t
On 11/14/06, Benoit Sigoure <[EMAIL PROTECTED]> wrote:
Hello,
bin_PROGRAMS = foo
foo_SOURCES = foo.hh foo.cc
BUILT_SOURCES = foo.hh
foo.hh: foo.gen
cp foo.gen foo.hh
CLEANFILES = foo.hh
EXTRA_DIST = foo.gen
--
Hello all,
I added to my configure.ac:
AC_ARG_ENABLE([debug-parser],
AC_HELP_STRING([--enable-debug-parser],
[enable parser debug (default is NO)]),
[case "${enableval}" in
yes) debug_parser=true;;
For some reason this now works:
AM_YFLAGS = -d
AM_LFLAGS = -o$(LEX_OUTPUT_ROOT).c -CFa
if DEBUG_PARSER
AM_YFLAGS += --debug
endif
if DEBUG_LEXER
AM_LFLAGS += -d
endif
Cheers
On 4/13/07, Paulo J. Matos <[EMAIL PROTECTED]> wrote:
Hello all,
I added to my configure.ac:
AC_ARG_ENABLE(
Hello all,
Which files of a autotools project should be kept in a control
versioning system?
I've been keeping the files kept by make maintainer-clean but that
keeps the configure script, for example, which is machine dependent (I
think) , so I guess I need something stricter?
Cheers,
--
Paulo
On Jan 24, 2008 11:34 AM, Ralf Wildenhues <[EMAIL PROTECTED]> wrote:
> Hello Paulo,
>
> * Paulo J. Matos wrote on Thu, Jan 24, 2008 at 11:55:21AM CET:
> >
> > Which files of a autotools project should be kept in a control
> > versioning system?
>
> Some
On Jan 24, 2008 2:59 PM, Bob Friesenhahn <[EMAIL PROTECTED]> wrote:
> On Thu, 24 Jan 2008, Ralf Wildenhues wrote:
> >> I've been keeping the files kept by make maintainer-clean but that
> >> keeps the configure script, for example, which is machine dependent (I
> >> think) , so I guess I need somet
On Jan 24, 2008 9:54 PM, Warren Young <[EMAIL PROTECTED]> wrote:
> Paulo J. Matos wrote:
> >
> > Which files of a autotools project should be kept in a control
> > versioning system?
>
> IMHO, nothing generated goes in the repository. Ever. If that means
>
Hello all,
To compile a program fully-statically I do:
./configure CPPFLAGS="-DNDEBUG -I../../libfileIO-0.2.3/src"
CXXFLAGS="-O3" LDFLAGS="-static-libgcc -static -Wl,-Bstatic
-L../../libfileIO-0.2.3/src"
In the linking phase things go wrong:
/bin/sh ../libtool --tag=CXX --mode=link g++ -Wall -s
Hello all,
To compile a program fully-statically I do:
./configure CPPFLAGS="-DNDEBUG -I../../libfileIO-0.2.3/src"
CXXFLAGS="-O3" LDFLAGS="-static-libgcc -static -Wl,-Bstatic
-L../../libfileIO-0.2.3/src"
In the linking phase things go wrong:
/bin/sh ../libtool --tag=CXX --mode=link g++ -Wall -s
Hello all,
To compile a program fully-statically I do:
./configure CPPFLAGS="-DNDEBUG -I../../libfileIO-0.2.3/src"
CXXFLAGS="-O3" LDFLAGS="-static-libgcc -static -Wl,-Bstatic
-L../../libfileIO-0.2.3/src"
In the linking phase things go wrong:
/bin/sh ../libtool --tag=CXX --mode=link g++ -Wall -s
Dear all,
I am sorry for the repetition of emails but my university internet
connection has been up and down lately and I thought it hadn't been
sent.
Truly sorry,
--
Paulo Jorge Matos - pocm at soton.ac.uk
http://www.personal.soton.ac.uk/pocm
PhD Student @ ECS
University of Southampton, UK
Hi,
I am slightly confused as to whether I should be posting this to the
bison or this mailing list but here it goes.
I have a bison based project which has the following definitions:
,
| BUILT_SOURCES = scgparser.h
| AM_YFLAGS = -d
| AM_LDFLAGS = -lgmpxx -lgmp
|
| bin_PROGRAMS = scgc
|
| s
Philip Herron writes:
> Your bison generated header also gets renamed by ylwrap, and yeah this
> is probably the best place to ask about this problem your bison header
> (y.tab.h) will get renamed to the same name as your bla.y but changed
> to bla.h.
>
> Notice the make line you posted was scgpa
Pippijn van Steenhoven writes:
>
> I solved this problem by adding my own y.tab.h which does nothing but
> #include "scgparser.h".
Thanks. This sounds like a good workaround but it's far from a perfect
solution.
--
PMatos
Pippijn van Steenhoven writes:
> On Sun, Oct 31, 2010 at 10:55:53PM +, Philip Herron wrote:
>> Your bison file shouldnt generate any code with includes y.tab.h. You
>> must have it in your field delcarations for bison. Its only your lexer
>> needs to see these bison definitions.
>
> It does f
Pippijn van Steenhoven writes:
> I solved this problem by adding my own y.tab.h which does nothing but
> #include "scgparser.h".
But unfortunately each time bison is ran, the file is overwritten it
seems. :(
--
PMatos
Philip Herron writes:
> Yeah this all seems like a bug to me, i dont do much C++ i prefer to
> use C so i havent used C++ bison parsers et'al . But yeah i have a few
> work arounds to get multiple bison and flex working i have some work i
> want to do to ylwrap to help it all but i really haven't
"Andrew W. Nosenko" writes:
>
> Therefore, there is no need neither AC_PROG_YACC nor ylwrap. Just
> need move them away, don't use them. Anyway, if byacc (for example)
> will be found and cough, it won't process GLR-targeted .y source
> anyway. Just threat bison like would be threated any anot
pocma...@gmail.com (Paulo J. Matos) writes:
>
> I understand your opinion, unfortunately it then means that there's no
> support for Bison in C++ mode from the automake side which is
> unfortunate. :-/
I decided to forget automake support and instead go for my own:
So, I rem
46 matches
Mail list logo
