On Jun 8, 2001, Gary V. Vaughan [EMAIL PROTECTED] wrote:
Unfortunately this probably comes dow to wrapper scripts, which is ugly too
Since we're talking Cygwin, shouldn't it be a wrapper executable?
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC
On Jun 8, 2001, Guido Draheim [EMAIL PROTECTED] wrote:
hmmm, or an autoconf wrapper macro?
Nope, this wouldn't work for libraries that are not installed in
libdir, but in a subdir thereof.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer
On Sunday 17 June 2001 8:25 pm, Alexandre Oliva wrote:
On Jun 8, 2001, Gary V. Vaughan [EMAIL PROTECTED] wrote:
Unfortunately this probably comes dow to wrapper scripts, which is ugly
too
Since we're talking Cygwin, shouldn't it be a wrapper executable?
Good point.
--
())_. Gary V.
Since we are trying to make things work like UNIX here, I think that the dlls
should probably be installed to $libdir. The problem that needs solving is
how to teach the executable to find its dlls.
Unfortunately this probably comes dow to wrapper scripts, which is ugly too
=(O|
Bah!
The current cygwin shared library installation logic seems to be
install path../bin
This fails for things like l3 in depdemo where the install dir is
extradir = $(libdir)/extra
extra_LTLIBRARIES = libl3.la
I'm not sure what we should use as install logic... maybe walk up the
install path
- Original Message -
From: edward [EMAIL PROTECTED]
To: Robert Collins [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Thursday, June 07, 2001 1:22 AM
Subject: Re: dll installation logic
make it a module
cheers,
edward
What will that do for the test case? If the test case is checking
: Thursday, June 07, 2001 1:22 AM
Subject: Re: dll installation logic
make it a module
cheers,
edward
What will that do for the test case? If the test case is checking
installation of shared libraries in lib\extra, changing the test case
won't solve the brokenness in libtool...
Rob
