Re: performing pre-build shell commands with automake

2010-06-20 Thread John Calcote
On 6/20/2010 4:48 PM, Wesley Smith wrote: > >> src/lcairo.c : resource.qt >> >> I tested this and it works - here's my test code: >> > It definitely does work! Thanks so much. The QT resources in my case > or code generated files from the actual source files, so it makes > sense to trigger t

Re: performing pre-build shell commands with automake

2010-06-20 Thread Wesley Smith
>> There are 2 issues I see: >> 1) Why would the Makefile.am below produce 2 commands compiling the >> same source file into 2 different directories? >> > > The two libtool commands are not exactly alike. The first command > generates position-independent code (PIC) to be used in your libtool > sha

Re: performing pre-build shell commands with automake

2010-06-20 Thread John Calcote
On 6/20/2010 3:05 PM, Wesley Smith wrote: > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. > -I/usr/include/lua5.1 -I/usr/include/cairo -I/usr/include/directfb > -I/usr/include/freetype2 -g -O2 -MT lcairo.lo -MD -MP -MF > .deps/lcairo.Tpo -c src/lcairo.c -fPIC -DPIC -o .libs/lcairo.o > > libto

Re: performing pre-build shell commands with automake

2010-06-20 Thread Wesley Smith
> Build once without your qt dependencies in place and carefully note the > name and relative location of the object file generated from > src/lcairo.c. The qt dependency rule will have to look like this: > > exact-name-and-relative-location-of-object : resource.qt > > This is the short answer. You

Re: performing pre-build shell commands with automake

2010-06-20 Thread John Calcote
On 6/20/2010 2:34 PM, Wesley Smith wrote: > I also tried using lcairo.lo, which triggered the preliminary shell > commands but barfed because the commands didn't generate lcairo.lo. > hmm.. Is there a way to print out what rules were invoked during a > make invocation? > You do want the actual

Re: performing pre-build shell commands with automake

2010-06-20 Thread John Calcote
Wes, On 6/20/2010 2:14 PM, Wesley Smith wrote: > How does one do this kind of thing when the source file is specified > in a subfolder? > INCLUDES = -I/usr/include/lua5.1 -I/usr/include/cairo > -I/usr/include/directfb -I/usr/include/freetype2 > > lib_LTLIBRARIES = cairo.la > cairo_la_LDFLAGS = -mo

Re: performing pre-build shell commands with automake

2010-06-20 Thread Wesley Smith
I also tried using lcairo.lo, which triggered the preliminary shell commands but barfed because the commands didn't generate lcairo.lo. hmm.. Is there a way to print out what rules were invoked during a make invocation? wes On Sun, Jun 20, 2010 at 10:14 PM, Wesley Smith wrote: >>> >>> consumer.

Re: performing pre-build shell commands with automake

2010-06-20 Thread Wesley Smith
>> >> consumer.o: resource.qt > How does one do this kind of thing when the source file is specified in a subfolder? INCLUDES = -I/usr/include/lua5.1 -I/usr/include/cairo -I/usr/include/directfb -I/usr/include/freetype2 lib_LTLIBRARIES = cairo.la cairo_la_LDFLAGS = -module -avoid-version cairo_la

Re: performing pre-build shell commands with automake

2010-06-20 Thread Wesley Smith
> However, that said, the correct way to do what you want is to place a > make dependency between the sources you want to generate, and the > consumers of those sources. Automake generates normal makefiles (or > rather makefile.in templates for Autotconf) from Makefile.am files. Some > of the code

Re: performing pre-build shell commands with automake

2010-06-20 Thread John Calcote
Hi Wesley, You could use BUILT_SOURCES to accomplish this. Any sources listed in BUILT_SOURCES are built before any other rules are executed. Automake does this by making BUILT_SOURCES a dependency of "all", "check" and "install", so that when you run "make all", "make check" or "make install", th

Re: performing pre-build shell commands with automake

2010-06-20 Thread Peter Johansson
On 6/20/10 2:56 PM, Wesley Smith wrote: I've been looking through the automake docs trying to figure out how to execute shell commands as part of the build process but before anything actually gets compiled. Is this possible? I need this for things like Qt's 'moc' and some other script-based co