On 28 December 2010 10:53, kknd1233 wrote:
>
> Hello everyone, I am new to automake and learning on it.
>
> I am asked to 'develop autobuild script using Automake', the GNU Automake
> website (http://www.gnu.org/software/hello/manual/automake/index.html) gives
> me some ideas but still not sure.
>
You can look at the problem in 2 ways, really you can say ylwrap is
too simplistic and not great which is correct but it does work for
standard-ish inputs like C parsers. But c++ and GLR doesnt work right
but you could say they dont comform to the standard way ylwrap expects
so it fails.
I do want
that GLR parsers and C++ parsers have
the head declarations where you would generally include this manually
yourself.
--Phil
On 2 November 2010 08:44, Paulo J. Matos wrote:
> Philip Herron writes:
>
>> Yeah this all seems like a bug to me, i dont do much C++ i prefer to
>> use
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 got the time
at the moment. Bas
On 1 November 2010 10:08, Pippijn van Steenhoven wrote:
> On Mon, Nov 01, 2010 at 02:14:49AM +0000, Philip Herron wrote:
>> Then thats probably a bug although i havent played with GLR prarsers
>> in bison you may want to post this to bison-help and see what they
>> say.
Then thats probably a bug although i havent played with GLR prarsers
in bison you may want to post this to bison-help and see what they
say.
--Phil
On 31 October 2010 23:03, Pippijn van Steenhoven wrote:
> On Sun, Oct 31, 2010 at 10:55:53PM +0000, Philip Herron wrote:
>> Your b
On 31 October 2010 18:49, Paulo J. Matos wrote:
> 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 a
On 31 October 2010 10:54, Jan Engelhardt wrote:
> Hi,
>
>
> While trying to utilize Autotools in a preexisting project that
> previously just relied on Makefiles, I came across ylwrap failing for
> some absurd, unknown reason. I couldn't help but run sh -x and debug it
> piecewise.
>
> So what's u
On 30 October 2010 11:46, Paulo J. Matos wrote:
> 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
On 10 September 2010 04:28, Reuben Hawkins wrote:
> Hi y'all,
>
> Attached is my Makefile.am. My problem is editing scanner.l or
> grammar.y doesn't trigger a rebuild of my whole project when *I think*
> it should... How do I set dependencies such that editing scanner.l or
> grammar.y will rebui
On 31 July 2010 18:26, Ralf Wildenhues wrote:
> Maybe if we have contents conditional on 'make' or 'nmake' output?
> Would that even help anybody? (no idea)
> Is there anybody willing to work on this?
This sounds amazing on one of my other projects i support a cmake
build along side my autoconf
nsson :
> Philip Herron wrote:
>>
>> or do I have to link directly of
>> this as in ``gcc -o ... /usr/local/lib/libcrules.so''.
>
> Well, if they use Automake they can do
>
> LDADD = -lcrules
>
> or they can append `-lcrules' to $LIBS in configu
Hey guys,
I've been reading through the manual a few times but i cant seem to
find what i am looking for. Recently i now need to make some full
shared libraries not just '-module' for dlopen which is what i was
doing before for some modules/plugins. But now i want a full shared
library for client
Hey
Autoconf is what should handle your libraries etc:
bignum="no"
AC_ARG_WITH(bignum,
[AS_HELP_STRING([--with-bignum=yes/no],
[With GNU MP and MPFR multi-precision support, default no.])],
[bignum="$withval"])
if test "x$bignum" == "xyes"; then
AC_CHECK_LIB([gmp], [__gmpz_init], ,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey
I think i see the portable solution to the multiple lexer problem we
have been having, i think i will just put in a test case and update
the documentation on whats the best way to use automake to handle it
for you.
The solution is correct on the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey guys
I just made a quick test project there its not pretty but the
src/Makefile.am
bin_PROGRAMS = test
noinst_LIBRARIES = libparser_a.a libparser_b.a
test_SOURCES = main.c
test_LDADD = libparser_a.a libparser_b.a
libparser_a_a_YFLAGS = -d -p pr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey
>
> To be completely portable (not depending on flex options) I don't
> think either the prefix/outfile options or the prefix commandline
> option can be given to lex (they are not mentioned in lex(1p) at
> least).
>
Yeah your right about that! The
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ralf Wildenhues wrote:
> * Philip Herron wrote on Sun, May 17, 2009 at 02:00:45PM CEST:
>> But i'll maby play with this. If i find a more standard solution
>> what should i do?
>
> Write a patch (preferably against git master
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ralf Wildenhues wrote:
> Hello,
>
> * Philip Herron wrote on Sun, May 17, 2009 at 12:49:32PM CEST:
>> I solved this problem a while back!
>>
>> http://lists.gnu.org/archive/html/automake/2009-04/msg00095.html
>>
>&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Ahh interesting, I did stumble upon your mail before but I missed
> the bit about the "outfile" option, so I got stuck with that. I
> guess this option is flex-specific but at this point I just want it
> to work, portability is less important since o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey
I solved this problem a while back!
http://lists.gnu.org/archive/html/automake/2009-04/msg00095.html
The trick is in each of your lexers(flex .l) add this:
%option prefix="prefix" outfile="lex.yy.c"
Dont change the outfile ylwrap needs it to be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey
This is probably in the automake manual but hey. I am wondering is it
possible to say in a Makefile.am besides your bin_programs CFLAGS etc...
Can you add extra things like a: make check rule -> to run the
bin_program(s) and grep for a certain ou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christian Rössel wrote:
> Philip Herron wrote:
>> Hey
>>
>> I was just wondering say you have a Makefile.am like this:
>>
>> bin_PROGRAMS= myprog
>> AM_YFLAGS= -d
>> AM_LFLAGS=
>>
>> mprog_CFLAG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christian Rössel wrote:
> Philip Herron wrote:
>> Hey
>>
>> I was just wondering say you have a Makefile.am like this:
>>
>> bin_PROGRAMS= myprog
>> AM_YFLAGS= -d
>> AM_LFLAGS=
>>
>> mprog_CFLAG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter Johansson wrote:
> Philip Herron wrote:
>> What i would like to do is have sperate Makefile.am in each subdir that
>> just compile to object files that in the src/Makefile can link into the
>> main binary. Or is this the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey
Another topic, its another basic question. Dont worry its not yacc/lex
related ;). But say you have a project structure like
project->
include->*.h
src->*.c
-> subdir -> *.c
-> subdir2 -> *.c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey
I was just wondering say you have a Makefile.am like this:
bin_PROGRAMS= myprog
AM_YFLAGS= -d
AM_LFLAGS=
mprog_CFLAGS= -I$(top_srcdir)/include
myprog_SOURCES= foo1.c foo2.c bla.l bla_gram.y bla2.l bla bla bla
Can you specify seperate FLAG l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Philip Herron wrote:
> Hey guys
>
> This is my first post so sorry if this is a little basic. I was bugging
> some guys on the autoconf lists about this but its not an autoconf
> problem. Whats the best strategy for multiple lexers in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey guys
This is my first post so sorry if this is a little basic. I was bugging
some guys on the autoconf lists about this but its not an autoconf
problem. Whats the best strategy for multiple lexers in one program. So
i made a simple lexer
So my Ma
29 matches
Mail list logo
