Randy W. Sims <ml...@th...> wrote:
> I don't know enough about the autotools to answer, but I'd be very
> curious to learn what you come up with.
So far, nothing too hot:
--snip--
PERL_MODULE = Net-BitTorrent-LibBTT/blib/arch/auto/Net/BitTorrent/LibBTT/LibBTT.so
Net-BitTorrent-LibBTT/Makefile: Net-BitTorrent-LibBTT/Makefile.PL
cd Net-BitTorrent-LibBTT && \
APR_CONFIG=@APR_CONFIG@ $(PERL) Makefile.PL \
CCFLAGS="-I../.. $(CPPFLAGS) $(CFLAGS)" LDDLFLAGS=$(LDDLFLAGS)
$(PERL_MODULE): Net-BitTorrent-LibBTT/Makefile
$(MAKE) -C Net-BitTorrent-LibBTT
if BUILD_PERL
install-exec-local:: $(PERL_MODULE)
$(MAKE) -C Net-BitTorrent-LibBTT install
clean-local::
@if test -e Net-BitTorrent-LibBTT/Makefile; then $(MAKE) -C
Net-BitTorrent-LibBTT distclean; fi
all-local:: $(PERL_MODULE)
endif
--snip--
Ideally, I want to generalize this a bit more. The main problem is
dertermining a good "make" target to signify that a module has been
compiled. There's pm_to_blib, but that's not always accurate. Or maybe I
should just dumbly "make" in the perl directory every single time an
appropriate target is invoked from outside? Either way, make/automake need a
target they can point at and say "ah, that means the perl module"...
- Tyler
|