On Wed, Sep 25, 2002 at 03:39:50PM +0200, Alexander Gottwald wrote: > On Wed, 25 Sep 2002, Nicholas Wourms wrote: > > > > But I don't know if this is either valid for imake or if it will > > > break anything. And when you do a shared and a static version, the > > > static version will most likely be name libName.dll.a too. > > > > Well that doesn't make any sense because on linux it builds shared > > libraries with "so" and static libs with ".a". > > The original LibraryTargetName from imake.rules could be overwritten > in cygwin.rules. So all these changes apply to cygwin only. > > > Also, the way it > > builds it makes it possible in my mind. I make puts shared objects > > in $BUILDDIR/ and static into $BUILDDIR/unshared/. It shouldn't be > > too hard to insert the logic necessary to handle archiving the > > contents properly. > > building libraries and programs which depend on another library have > a "progFoo: xc/exports/lib/libFoo.a" as rule. Replacing LibraryTarget- > Name with the Shared/Static switch from my posting will replace this > either by > progFoo: xc/exports/lib/libFoo.a > or > progFoo: xc/exports/lib/libFoo.dll.a > depending on SharedLibraryFoo set to NO or YES > > Hm, actually this is correct and what we want. > > > Also, ld can automatically generate shared import > > libraries during linking of the dll, so that might be a possible > > route to look at. > > This is already done cygwin.rules > > > > This was not the system install but only the global install in the > > > build > > > tree. > > > > > > > I'm sorry, but I don't understand what you mean here... > > running make on the xc tree will _symlink_ (and partly copy) the targets > to xc/export/lib and xc/export/bin. Make install later will _copy_ it > to the installdir.
When you've come to a decision on the patch, post a new one so I can take a look and then commit it. Alan.
