Re: How to use BUILT_SOURCES in non-recursive, multi-directory project?

2006-03-12 Thread Duncan Gibson
I wrote: .fl.h: d=`dirname [EMAIL PROTECTED] ; \ f=`basename $@ .h`.fl ; \ cp $ $(top_builddir)/$$d/$$f ; \ cd $(top_builddir)/$$d ; \ fluid -c $$f BUILT_SOURCES += src/foo.h Ralf replied: dirname and basename are not

Re: How to use BUILT_SOURCES in non-recursive, multi-directory project?

2006-03-09 Thread Ralf Wildenhues
Hi Duncan, Note: I don't know whether and how much of this was already addressed. * Duncan Gibson wrote on Sat, Mar 04, 2006 at 06:09:22PM CET: use 'fluid -c foo.fl' to create foo.h and foo.cxx create libfoo.a from foo.cxx compile foo_test.cxx and link against libfoo.a *snip*

Re: How to use BUILT_SOURCES in non-recursive, multi-directory project?

2006-03-09 Thread Thomas Dickey
On Thu, 9 Mar 2006, Ralf Wildenhues wrote: dirname and basename are not portable to ancient hosts. In practice they will work fine, though. I'd write I know that dirname is not, but what platform did not support basename? -- Thomas E. Dickey http://invisible-island.net

Re: How to use BUILT_SOURCES in non-recursive, multi-directory project?

2006-03-09 Thread Ralf Wildenhues
* Thomas Dickey wrote on Thu, Mar 09, 2006 at 08:13:07PM CET: On Thu, 9 Mar 2006, Ralf Wildenhues wrote: dirname and basename are not portable to ancient hosts. In practice they will work fine, though. I'd write I know that dirname is not, but what platform did not support basename? No

Re: How to use BUILT_SOURCES in non-recursive, multi-directory project?

2006-03-09 Thread Thomas Dickey
On Thu, 9 Mar 2006, Ralf Wildenhues wrote: * Thomas Dickey wrote on Thu, Mar 09, 2006 at 08:13:07PM CET: On Thu, 9 Mar 2006, Ralf Wildenhues wrote: dirname and basename are not portable to ancient hosts. In practice they will work fine, though. I'd write I know that dirname is not, but

Re: How to use BUILT_SOURCES in non-recursive, multi-directory project?

2006-03-09 Thread Thomas 'Tom' R. Treadway III
On Mar 9, 2006, at 11:51 AM, Thomas Dickey wrote: On Thu, 9 Mar 2006, Ralf Wildenhues wrote: * Thomas Dickey wrote on Thu, Mar 09, 2006 at 08:13:07PM CET: On Thu, 9 Mar 2006, Ralf Wildenhues wrote: dirname and basename are not portable to ancient hosts. In practice they will work fine,

Re: How to use BUILT_SOURCES in non-recursive, multi-directory project?

2006-03-09 Thread Thomas Dickey
On Thu, 9 Mar 2006, Thomas 'Tom' R. Treadway III wrote: On Mar 9, 2006, at 11:51 AM, Thomas Dickey wrote: hmm - I can remember when it was a problem (around 1990), but can't recall whether it was Apollo SR9, SunOS 3 or HPUX. You did say ancient... The dirname utility originated in System III.

Re: How to use BUILT_SOURCES in non-recursive, multi-directory project?

2006-03-09 Thread Thomas 'Tom' R. Treadway III
On Mar 9, 2006, at 12:57 PM, Thomas Dickey wrote: On Thu, 9 Mar 2006, Thomas 'Tom' R. Treadway III wrote: On Mar 9, 2006, at 11:51 AM, Thomas Dickey wrote: hmm - I can remember when it was a problem (around 1990), but can't recall whether it was Apollo SR9, SunOS 3 or HPUX. You did say

How to use BUILT_SOURCES in non-recursive, multi-directory project?

2006-03-04 Thread Duncan Gibson
I've been trying to set up a multi-directory project using non-recursive auto{conf,make} to build an FLTK application (see http://www.fltk.org). I have created a simple example for testing, where I have a sub-directory containing foo.fl and foo_test.cxx, and what I need to do is: use 'fluid