On 10/21/07, Brian Dessent <[EMAIL PROTECTED]> wrote:
> Ralf Wildenhues wrote:
>
> > Well, I could tell you that Libtool can create DLLs plus import
> > libraries (it names them libfoo.dll.a), but I don't think you want
> > to hear that at this point. ;-)
>
> Libtool isn't appropriate here because
Ralf Wildenhues wrote:
> Well, I could tell you that Libtool can create DLLs plus import
> libraries (it names them libfoo.dll.a), but I don't think you want
> to hear that at this point. ;-)
Libtool isn't appropriate here because he's not actually building any
libraries, only synthesizing impor
On 10/21/07, Ralf Wildenhues <[EMAIL PROTECTED]> wrote:
> * NightStrike wrote on Fri, Oct 19, 2007 at 09:25:08PM CEST:
> >
> > crt_SCRIPTS = libcrtdll.a libmsvcrt.a libmsvcr80.a
> > libcrtdll.a libmsvcrt.a libmsvcr80.a:
> > base=`echo $@ | sed -e 's/\.a//' -e 's/^lib//'`; \
> > $(DL
* NightStrike wrote on Fri, Oct 19, 2007 at 09:25:08PM CEST:
>
> 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)/$${b
On 10/19/07, Andreas Schwab <[EMAIL PROTECTED]> wrote:
> NightStrike <[EMAIL PROTECTED]> writes:
>
> > Ok. I just tested your idea, and I am going to move all .a custom
> > targets to a _DATA primary, and leave the _SCRIPTS primary for just
> > the custom executable targets (like crt1.o, etc).
>
>
NightStrike <[EMAIL PROTECTED]> writes:
> Ok. I just tested your idea, and I am going to move all .a custom
> targets to a _DATA primary, and leave the _SCRIPTS primary for just
> the custom executable targets (like crt1.o, etc).
crt1.o is DATA as well.
Andreas.
--
Andreas Schwab, SuSE Labs,
On 10/19/07, Ralf Wildenhues <[EMAIL PROTECTED]> wrote:
> * NightStrike wrote on Fri, Oct 19, 2007 at 09:14:22PM CEST:
> >
> > Should static libraries be executable?
>
> They need not be. But it's no problem if they are.
Ok. I just tested your idea, and I am going to move all .a custom
targets t
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
* NightStrike wrote on Fri, Oct 19, 2007 at 09:14:22PM CEST:
>
> Should static libraries be executable?
They need not be. But it's no problem if they are.
Cheers,
Ralf
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?
H
On 10/19/07, Ralf Wildenhues <[EMAIL PROTECTED]> wrote:
> | # These targets require special handling that automake can't
> | # yet support (or that I don't know how to do properly)
> | crtdir=$(prefix)/$(target)/lib
> | crt_SCRIPTS = \
> | crt1.o crt2.
>
> There is nothing inherently wrong with d
* NightStrike wrote on Tue, Oct 16, 2007 at 10:42:55PM CEST:
> I am trying to build a Makefile.am file "correctly". This is what I
> have so far:
>
> http://mingw-w64.svn.sourceforge.net/viewvc/mingw-w64/experimental/buildsystem/Makefile.am?revision=137&view=markup
>
> Some issues that I've note
ping..
On 10/16/07, NightStrike <[EMAIL PROTECTED]> wrote:
> I am trying to build a Makefile.am file "correctly". This is what I
> have so far:
>
> http://mingw-w64.svn.sourceforge.net/viewvc/mingw-w64/experimental/buildsystem/Makefile.am?revision=137&view=markup
>
> Some issues that I've noted i
I am trying to build a Makefile.am file "correctly". This is what I
have so far:
http://mingw-w64.svn.sourceforge.net/viewvc/mingw-w64/experimental/buildsystem/Makefile.am?revision=137&view=markup
Some issues that I've noted include installing all libraries as
executables instead of 644 (due to
14 matches
Mail list logo
