AM_PROG_LEX ?
Ansley, Michael
Michael.Ansley at intec.co.za
Wed Nov 10 07:23:02 GMT 1999
You have to add it earlier than that, probably after the AC_PROG_CC. Try it
there, and see how it goes.
MikeA
>> -----Original Message-----
>> From: Philip M. Galea [mailto:pgalea at btinternet.com]
>> Sent: Tuesday, November 09, 1999 12:31 AM
>> To: 'kdevelop at barney.cs.uni-potsdam.de'
>> Subject: RE: AM_PROG_LEX ?
>>
>>
>> I've added the AM_PROG_LEX into the configure.in but I'm
>> still having problems. The configuration.in looks like so :
>>
>> dnl without this order in this file, autoconf will not work!
>> dnl the argument is a source file out of your sources. But
>> dnl acinclude.m4 makes the job for all programs ;-)
>> AC_INIT(acinclude.m4)
>>
>> dnl without this order in this file, automake will be confused!
>> dnl the argument
>> AM_CONFIG_HEADER(config.h)
>>
>> dnl insert here your program name and version number
>> AC_PROG_CC
>> KDE_DO_IT_ALL(avns,0.1)
>>
>> dnl in this space add everything you want to check for
>> dnl examples are specific headers, libraries, etc.
>> dnl everything to compile and run a KDE program is already checked
>>
>> dnl add here all your Makefiles. This are created by configure
>> AC_OUTPUT(Makefile avns/Makefile avns/docs/Makefile
>> avns/docs/en/Makefile )
>>
>>
>> AM_PROG_LEX
>>
>>
>>
>>
>> However when I make the project it does this:
>>
>> *** failed ***
>> cd .. && automake --gnu avns/Makefile
>> cd .. && perl automoc avns/Makefile.in
>> cd .. \
>> && CONFIG_FILES=avns/Makefile CONFIG_HEADERS= /bin/sh
>> ./config.status
>> creating avns/Makefile
>> Making all in docs
>> gmake[1]: Entering directory `/home/pgalea/avns/avns/docs'
>> cd ../.. && automake --gnu avns/docs/Makefile
>> cd ../.. \
>> && CONFIG_FILES=avns/docs/Makefile CONFIG_HEADERS= /bin/sh
>> ./config.status
>> creating avns/docs/Makefile
>> gmake[1]: Leaving directory `/home/pgalea/avns/avns/docs'
>> gmake[1]: Entering directory `/home/pgalea/avns/avns/docs'
>> Making all in en
>> gmake[2]: Entering directory `/home/pgalea/avns/avns/docs/en'
>> cd ../../.. && automake --gnu avns/docs/en/Makefile
>> cd ../../.. \
>> && CONFIG_FILES=avns/docs/en/Makefile CONFIG_HEADERS=
>> /bin/sh ./config.status
>> creating avns/docs/en/Makefile
>> gmake[2]: Leaving directory `/home/pgalea/avns/avns/docs/en'
>> gmake[2]: Entering directory `/home/pgalea/avns/avns/docs/en'
>> gmake[2]: Nothing to be done for `all'.
>> gmake[2]: Leaving directory `/home/pgalea/avns/avns/docs/en'
>> gmake[1]: Leaving directory `/home/pgalea/avns/avns/docs'
>> /bin/sh: LEX@: command not found
>> gmake: *** [Parser_VRML2.c++] Error 127
>>
>>
>> I can't seem to find where this LEX is defined? (I'm
>> looking for LEX=lex or LEX=flex)
>>
>> Thanks
>>
>>
>> Philip M. Galea
>> http://www.cee.hw.ac.uk/~ceepmg/
>>
>>
>> -----Original Message-----
>> From: Bernd Gehrmann [SMTP:bernd at physik.hu-berlin.de]
>> Sent: 07 November 1999 18:49
>> To: kdevelop at barney.cs.uni-potsdam.de
>> Subject: Re: AM_PROG_LEX ?
>>
>> On Sat, 06 Nov 1999 Philip M. Galea wrote:
>>
>> >Anyway I'm working on a project at the moment, where I'm
>> using lex to
>> >create a file parser (for VRML), however when I add a *.l
>> file to the
>> >project a small popup reminds me to add AM_PROG_LEX to the
>> configure.in
>> >file. Thats great but what does that mean?
>>
>> Well, just that: add the string AM_PROG_LEX to the file configure.in
>> in your project :-)
>>
>> For other macros, the best source of information are the autoconf
>> and automake info pages.
>>
>> Bernd.
>>
>>
More information about the KDevelop
mailing list