Re: call for help/crazy idea: nmake support

2010-08-10 Thread Braden McDaniel
On Tue, 2010-08-10 at 16:38 -0700, Natalie Tasman wrote: > Hi Ralf, > > I think this is a great idea and would be interested in hearing your > plans for moving forward. I've invested a lot of time in an autotools > build system that works on *nix and mingw (and cross-compiling to > mingw from li

Re: call for help/crazy idea: nmake support

2010-08-10 Thread Braden McDaniel
On Sat, 2010-07-31 at 19:26 +0200, Ralf Wildenhues wrote: > Here's a crazy idea: how about if automake optionally output an input > file suitable for nmake (after configure substitution)? > Is that even feasible? (I'd guess so) > Maybe if we have contents conditional on 'make' or 'nmake' output?

Re: "No rule to make target" in a BUILT_SOURCES, non-recursive, multi-directory project

2010-08-10 Thread Ralf Wildenhues
* Daily, Jeff A wrote on Tue, Aug 10, 2010 at 11:29:42PM CEST: > Sorry for missing that. GNU Make 3.81 built for i386-apple-darwin9.0. Weird. I cannot reproduce your issue with that make version on GNU/Linux. Which file system does this happen on, maybe a case-insensitive one and there is anoth

Re: call for help/crazy idea: nmake support

2010-08-10 Thread Natalie Tasman
Hi Ralf, I think this is a great idea and would be interested in hearing your plans for moving forward. I've invested a lot of time in an autotools build system that works on *nix and mingw (and cross-compiling to mingw from linux!) and I do think this would be interesting to see this work on min

RE: "No rule to make target" in a BUILT_SOURCES, non-recursive, multi-directory project

2010-08-10 Thread Daily, Jeff A
> > > Which make version and implementation, > > Please answer this one as well. Sorry for missing that. GNU Make 3.81 built for i386-apple-darwin9.0.

Re: "No rule to make target" in a BUILT_SOURCES, non-recursive, multi-directory project

2010-08-10 Thread Ralf Wildenhues
* Daily, Jeff A wrote on Tue, Aug 10, 2010 at 09:45:43PM CEST: > > Which make version and implementation, Please answer this one as well.

RE: "No rule to make target" in a BUILT_SOURCES, non-recursive, multi-directory project

2010-08-10 Thread Daily, Jeff A
> > #*snip* > > BUILT_SOURCES = > > lib_LTLIBRARIES = libfoo.la > > libfoo_la_SOURCES = > > #*snip* > > If HAVE_PYTHON > > BUILT_SOURCES += foo/bar/wapi.c > > foo/bar/wapi.c: foo/bar/papi.h $(top_srcdir)/build-aux/wapi.py > > -rm -f foo/bar/wapi.c && \ > > $(PYTHON) $(top_srcdir)/bu

Re: "No rule to make target" in a BUILT_SOURCES, non-recursive, multi-directory project

2010-08-10 Thread Ralf Wildenhues
Hi Jeff, * Daily, Jeff A wrote on Tue, Aug 10, 2010 at 08:54:53PM CEST: > I am using subdir-objects and I have a single, top-level Makefile.am: > > #*snip* > BUILT_SOURCES = > lib_LTLIBRARIES = libfoo.la > libfoo_la_SOURCES = > #*snip* > If HAVE_PYTHON > BUILT_SOURCES += foo/bar/wapi.c > foo/bar/

"No rule to make target" in a BUILT_SOURCES, non-recursive, multi-directory project

2010-08-10 Thread Daily, Jeff A
I have almost the same situation as a post many years ago. The solution didn't seem to apply, however, http://www.opensubscriber.com/message/automake@gnu.org/3498366.html I am using subdir-objects and I have a single, top-level Makefile.am: #*snip* BUILT_SOURCES = lib_LTLIBRARIES = libfoo.la l