lex rule doesn't work when enabling C++ scanner with GNU Flex

ould it be possible for Automake to tweak the lex rule if "%option c++" is found in the lex source/input file, or if the "-+" flag is found in the $(AM_LFLAGS) make variable? Thanks, -Ossama -- Ossama Othman 1024D/F7A394A8 - 84ED AA0B 1203 99E4 1068 70E6 5EB7 5E71 F7A3 94A8

CORBA IDL support revisited

generate ".PRECIOUS" targets. - Object files for stubs and skeletons must be explicitly added to the object file list (e.g. LDADD/LIBADD). - Needs to be tested with Java. I've only tested with C++. Thanks, -Ossama -- Ossama Othman <[EMAIL PROTECTED]> Distributed Objec

Re: On the fly expansion of make targets

On Fri, Mar 01, 2002 at 10:58:17PM -0800, Ossama Othman wrote: > Is there any way to achieve the following portably? > > source = test.foo # assume it exists > source_suffixes = bar baz > targets = \ > $(shell base=`echo $(source) | sed -e 's/\.

On the fly expansion of make targets

$(targets): $(source) $(SOME_COMMAND) $? The is to generate the following on-the-fly: testbar testbaz: test.foo $(SOME_COMMAND) $? Thanks, -Ossama -- Ossama Othman <[EMAIL PROTECTED]> Distributed Object Computing Laboratory, Univ. of California at Irvine 1024D/F7A394A8 - 84ED

Re: Compiler Flags

the compiler actually accepts them). Actually, the flags he listed were preprocessor flags. I think that it would be better to use $CPPFLAGS since this variable is specifically for preprocessor flags. -Ossama -- Ossama Othman <[EMAIL PROTECTED]> Distributed Object Computing Laboratory, Un

Re: Building c++ library with cxx/osf with libtool

+ support in the libtool multi-language branch work for you? There may be no need to modify libtool, if so. -Ossama -- Ossama Othman <[EMAIL PROTECTED]> Distributed Object Computing Laboratory, Univ. of California at Irvine 1024D/F7A394A8 - 84ED AA0B 1203 99E4 1068 70E6 5EB7 5E71 F7A3 94A8

Re: How to install "config.h"

e library. One could argue that the inlined functions shouldn't depend on the output of configure. On that point, I would agree. If you had a solution for this problem then I'd be eternally grateful! :-) -Ossama -- Ossama Othman <[EMAIL PROTECTED]> Distributed Object Computing Labo

Re: How to install "config.h"

Hi Hari, On Mon, Oct 30, 2000 at 11:51:10AM -0600, Raja R Harinath wrote: > Ossama Othman <[EMAIL PROTECTED]> writes: > > I'm not sure that I agree with you, though I confess that I probably > > haven't thought about this issue as much as you. Please feel free t

Re: How to install "config.h"

ould be nice if it was possible to make autoconf prepend a package name, for example, to such automatically defined macros. That would at least help alleviate the problem. -Ossama -- Ossama Othman <[EMAIL PROTECTED]> Distributed Object Computing Laboratory, Univ. of California at Irvine 1024D/F7A394A8 - 84ED AA0B 1203 99E4 1068 70E6 5EB7 5E71 F7A3 94A8

Re: How to install "config.h"

ion is already installed and a user is compiling a new version > > from source, that user will pick up the installed .h files which will > > Even more evil: These files will contain definitions for PACKAGE and > VERSION. Not if you give AM_INIT_AUTOMAKE the dummy third argument.

Re: How to install "config.h"

nd use `#include ' in all other headers > that include it. Ah! Good call Alexandre! Robert, please ignore my last post. Installing config.h in /usr/local/include, for example, would be obviously be bad idea. :-) BTW, I do exactly what Alexandre suggests in some of my own packages. It work

Re: How to install "config.h"

ig.h' to be installed in $prefix/include. HTH -Ossama -- Ossama Othman <[EMAIL PROTECTED]> Distributed Object Computing Laboratory, Univ. of California at Irvine 1024D/F7A394A8 - 84ED AA0B 1203 99E4 1068 70E6 5EB7 5E71 F7A3 94A8

Re: CLEANFILES?

On Mon, Oct 16, 2000 at 10:02:02AM -0700, Ossama Othman wrote: > ## Clean up template repositories, etc. > clean-local: > -rm -rf .rpo ptrepository SunWS_cache Templates.DB That should have been "*.rpo," but you get the idea. :-) -Ossama -- Ossama Othma

Re: CLEANFILES?

, here's what I do in one of my C++ packages: ## Clean up template repositories, etc. clean-local: -rm -rf .rpo ptrepository SunWS_cache Templates.DB The clean-local target will automatically be invoked when doing a "make clean." BTW, this is documented in the Automake documen

Re: Re: [Automake] Making a Distribution

generate Makefiles, etc. Those `.in' files automatically get packaged with your distribution when you invoke "make dist." HTH, -Ossama -- Ossama Othman <[EMAIL PROTECTED]> Distributed Object Computing Laboratory, Univ. of California at Irvine 1024D/F7A394A8 - 84ED AA0B 1203 99

Re: VPATH in automake

.c > VPATH += @srcdir@/a:@srcdir@/b:@srcdir@/c Instead of relying on VPATHs, why not just use libtool convenience libraries? Libtool convenience library support is integrated quite well into Automake. HTH, -Ossama -- Ossama Othman <[EMAIL PROTECTED]> Distributed Object Computing Laborato

Re: Problem with CVS autoconf + automake + libtool

gt; # Include the architecture-specific sources > if TARGET_BEOS > ARCH_SRCS = SDL_sysjoystick.cc > else > if TARGET_WIN32 > ARCH_SRCS = SDL_mmjoystick.c > else > ARCH_SRCS = SDL_sysjoystick.c > endif > endif Perhaps Automake is confused. It doesn't look like it noti

Re: Maintaining header file directory structure on install

my head out of libtool, and back in to Makefile land. :-) Thanks! -Ossama -- Ossama Othman <[EMAIL PROTECTED]> Distributed Object Computing Laboratory, Univ. of California at Irvine 1024D/F7A394A8 - 84ED AA0B 1203 99E4 1068 70E6 5EB7 5E71 F7A3 94A8

Re: Maintaining header file directory structure on install

me way to preserve the directory structure of > the header files to make things a little less complicated. There may be an easier to achieve what you want. How about the following: pkgincludedir = $(prefix)/include/PackageName pkginclude_HEADERS = \ File1.h \

Re: Maintaining header file directory structure on install

... \ fileN.h However, both my sources and headers are in the same directory. I'm not sure how "pkginclude" deals with your directory structure, but adding a Makefile.am to your PackageName directory in your package distribution that contains some

Re: IDL dependencies, proposed solution.

st not have been pleasant. 8) -Ossama -- Ossama Othman <[EMAIL PROTECTED]> Distributed Object Computing Laboratory, Univ. of California at Irvine 1024D/F7A394A8 - 84ED AA0B 1203 99E4 1068 70E6 5EB7 5E71 F7A3 94A8

Re: Best way of dealing with program-generated files?

ed more perl since I wrote this patch and someone > with perl-knowledge would probably clean it up better :-) One day I'll get past the Bourne shell and learn how to better use Perl. :-) Anyway, I like your ideas. Hopefully we, the automake community, can get moving on IDL support

Re: IDL dependencies, proposed solution.

the client, not the skeletons. OTOH, skeletons generally do depend on the stubs so it would be somewhat beneficial to have a single library containing both stubs and skeletons, IMO. -Ossama -- Ossama Othman <[EMAIL PROTECTED]> Distributed Object Computing Laboratory, Univ. of California

CVS Automake prerequisites?

install -c checking whether build environment is sane... yes ./configure: line 1441: syntax error near unexpected token `"(c' ./configure: line 1441: ` echo $ac_n "(cached) $ac_c" 1>&6' Thanks, -Ossama -- Ossama Othman <[EMAIL PROTECTED]> Distributed Object Com

Re: Best way of dealing with program-generated files?

ule/target generation for CORBA IDL stubs and skeletons, then please let us know. I'd be very interested. -Ossama -- Ossama Othman <[EMAIL PROTECTED]> Distributed Object Computing Laboratory, Univ. of California at Irvine 1024D/F7A394A8 - 84ED AA0B 1203 99E4 1068 70E6 5EB7 5E71 F7A3 94A8

Re: multi-language-branch of libtool

't tried it, but I don't see why it wouldn't. > I think Alexandre might do this already. > > Give it a try and tell us what you find out... Indeed we do. Infact, I still use autoconf 2.13 and automake 1.4 for its development, not the ones in the CVS repository. -Ossama -- Ossa