On 10/19/07, Harlan Stenn <[EMAIL PROTECTED]> wrote:
> Why worry about which library files should be executable and which ones
> are not?
>
> Would it be easier to use:
>
> foodir=/where/ever
> foo_LIBRARIES = ...
>
> and let the generated Makefile handle getting the permissions right?
For 8 or so of the many many libraries, I do just that. However, I
don't know how to use automake to build a makefile that generates the
bulk of the libraries the way that I need. Observe:
crt_SCRIPTS = libcrtdll.a libmsvcrt.a libmsvcr80.a
libcrtdll.a libmsvcrt.a libmsvcr80.a:
base=`echo $@ | sed -e 's/\.a//' -e 's/^lib//'`; \
$(DLLTOOL) $(DLLOPTS) --dllname $${base}.dll --def
$(top_srcdir)/$${base}.def
To generate those three libraries, I do nothing other than run
dlltool, passing in the appropriate .def file. There is no source
file to speak of, nor any ar or ranlib applied. If I used the
_LIBRARIES primary, the way I understand it is that I would be
required to supply source files (I think), and I could not execute
just dlltool but instead ar and ranlib.
Do you know how to achieve the above effect with using the _LIBRARIES
primary instead of overriding the use of _SCRIPTS?
