Re: Installing program in other directory

On April 8, 2005 23:40, Ralf Corsepius wrote: > myxxxdir = somedirectory > myxxx_PROGRAMS = myprogram Oh, wow, thanks a lot. I'm a bit ashamed that it was so simple.

Installing program in other directory

Hi, In my package I build numerous libraries and programs and the installation method given by bin_PROGRAMS and lib_LTLIBRARIES works perfectly. However, I now have a program that can't be installed in $(bindir). It must be installed in $prefix/some/where/else. How can I do that? Thanks

Re: Mixing BUILT_SOURCES, double quote include and separation of source and binary directory

On March 31, 2005 07:56, [EMAIL PROTECTED] wrote: > (*) Hence you don't have to write #include "../include/inc.h" in > main.c, but rather #include , and you can simply write > #include , no matter if built.h is generated or not. Sure, that would work except I can't modify the code itself b

Re: Mixing BUILT_SOURCES, double quote include and separation of source and binary directory

On March 30, 2005 10:44, Ralf Wildenhues wrote: > > #include "../include/inc.h" > > which is not portable, by the way (but I can see if you don't care about > that part of the world). Why do you say that? That code is being ported from Microsoft's compiler, and I guess that if it works there and

Re: Mixing BUILT_SOURCES, double quote include and separation of source and binary directory

On March 30, 2005 10:14, Gary V. Vaughan wrote: > AM_CPPFLAGS = -I$(top_srcdir)/include -I$(top_builddir)/include Sure, this fixes the problem given in my example. But I can't do that because of this: > > The quick fix is to add the location of inc.h, prefixed with > > $(top_builddir). However

Mixing BUILT_SOURCES, double quote include and separation of source and binary directory

Hi, I have a problem which I figure must be fairly common, although I found no reference to it anywhere. I think it must be common because the SCons manual says they fixed it. [1] Anyway... Let's say I have two directories, "src" and "include". I place main.c in src and inc.h in include. main.

Kernel style output

Hi, I am wondering how I could get kernel-style make output using automake. By kernel-style, I mean that I want to see for example [C] myfile.c instead of the compiler command-line. Other letter codes are used in other cases, for example when linking. This style is used in the Linux build

Re: How to setup an example programs subdirectory?

On January 11, 2005 06:16, Stepan Kasal wrote: > Another approach would be to put the subdir into SUBDIRS, but prevent > the target `all' from making the programs there: > [...] Thank you! This is much better and cleaner than what I had proposed. This is exactly what I need

Re: How to setup an example programs subdirectory?

(top_builddir)/examples && $(MAKE) $(MFLAGS) clean ) clean-local: clean-examples ==== Comments? Improvements? -- Simon Perreault <[EMAIL PROTECTED]> -- http://nomis80.org

Re: How to setup an example programs subdirectory?

les SUBDIRS = wrap tests @EXAMPLES@ Automake is able to interpret that syntax, but it doesn't seem to produce valid output: Making all in @EXAMPLES@ /bin/sh: line 0: cd: @EXAMPLES@: No such file or directory -- Simon Perreault <[EMAIL PROTECTED]> -- http://nomis80.org

Re: How to setup an example programs subdirectory?

example programs are located. Am I supposed to use something like this? EXTRA_PROGRAMS=examples/foo examples/bar Do I then remove the Makefile.am file from the examples directory? Do I need to list "examples" in the SUBDIRS variable or not? That seems so wrong... -- Simon Perreault <[EMAIL PROTECTED]> -- http://nomis80.org

How to setup an example programs subdirectory?

be built on a "make examples" directive. How can I handle that? Thanks! -- Simon Perreault <[EMAIL PROTECTED]> -- http://nomis80.org