<html> <head> <base href="https://bugs.documentfoundation.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - allow to build shared libraries in bundled projects on Windows" href="https://bugs.documentfoundation.org/show_bug.cgi?id=91480#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - allow to build shared libraries in bundled projects on Windows" href="https://bugs.documentfoundation.org/show_bug.cgi?id=91480">bug 91480</a> from <a class="email" href="mailto:dtardon@redhat.com" title="David Tardon <dtardon@redhat.com>"> David Tardon</a> <pre>(In reply to Ashod Nakashian from <a href="show_bug.cgi?id=91480#c3">comment #3</a>) > Thanks for the detailed feedback David. > > > So, that is probably because libtool finds no known dynamic linker. > > At least in the case of libwps shared lib was disabled explicitly for > non-gcc compilers (actually, it assumes non-gcc to mean mvs/msc). Do you speak about libwps itself here, or about its build inside libreoffice? By the reference to msvc I assume the latter... In that case, libwps is not being built using its native build mechanism on Windows, because that currently cannot produce a shared library! The patch I attached switches the libwps build to the native build mechanism, so it can be used for experimentation. > I have a > patch to enable it, but, as you note, it still defaults to static linking. I > think I know where to look: libtool. As I have said, you should check the build log first. There might be some info message(s) from libtool telling why it switched back to static linking. > > > I agree that a ld-wrapper seems to be needed. > > I'll experiment with a wrapper and investigate how we could get it to > cooperate with libtool to create shared libs. > > Btw, are we waiting for Windows support of shared libs to enable/test on > other platforms, or does shared work on Linux? Do we know these libraries > can/do link as shared? I haven't tried building on Linux, and it's easier to > ask :) It seems I was not clear enough on that in the initial description... The libraries in question are already built as shared on all platforms. The libraries' native build mechanism (IOW, configure + make) is used on Linux and OS X. It is only Windows that needs special treatment (and the idea of this task is to try to change that). > > But not with the rest. > > You mean only with some projects? Not sure I get your point here. I do not agree that there is any need to patch configure or Makefiles.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>