Re: [MAD SCIENCE EXPERIMENT]: Replace some libtool functionality with handcoded C

[Steve Ellcey]

I'm curious.  I thought I knew shell scripting and the basics of
automake but I don't know what 'fnord' is (or is it just a variable like
foo and/or bar).  Perhaps as a consequence of that I don't know why
there is a need for a seperate LIBTOOL_BEGIN_COMPILE_CC and
LIBTOOL_END_COMPILE_CC macro (as opposed to a single LIBTOOL_COMPILE_CC
macro).  Anyone willing to give me a brief explanation?  I tried
googling for fnord but all I came up with is uses without any
explanation.

Steve Ellcey
Have you driven a fnord lately?


> From: Alexandre Oliva <address@hidden>
>
> LIBTOOL_BEGIN_COMPILE_CC = set fnord \
> 
> LIBTOOL_END_COMPILE_CC = ; shift 1; \
>   { test -d $$dir"/$(libtool_libdir) || \
>     $(mkdir_p) "$$dir"/$(libtool_libdir); } && \
>   rm -f "$$lofile"T "$$lofile" "$$dir/$$ofile" \
>     "$$dir/$(libtool_libdir)/$$ofile" || : ; \
>   $(LIBTOOL_COMPILE_CC_PIC) -o "$$dir/$(libtool_libdir)/$$ofile" \
>     $${1+"$$@"} && \
>   $(LIBTOOL_COMPILE_CC_NONPIC) -o "$$dir/$$ofile" $${1+"$$@"} && \
>   { echo pic_object=$(LIBTOOL_PIC_OBJECT); \
>     echo non_pic_object=$(LIBTOOL_NONPIC_OBJECT); } > "$$lofile"T && \
>   mv "$$lofile"T "$$lofile"