https://bz.apache.org/bugzilla/show_bug.cgi?id=64063
--- Comment #18 from Michael Osipov <micha...@apache.org> ---
(In reply to Christopher Schultz from comment #17)
> (In reply to Michael Osipov from comment #16)
> > (In reply to Christopher Schultz from comment #13)
> > > (In reply to Michael Osipov from comment #12)
> > > > My proposal would be platform-aware in Tomcat 10 and 8.5 + 9 would 
> > > > support
> > > > both for a transition phase. Of course, this will require decent
> > > > documentation. We should stick to wellknown behavior rather rolling our 
> > > > own.
> > > 
> > > My contention is that there is no "well-known behavior" to stick to.
> > 
> > There is, if you handle with native libraries daily, like I do.
> 
> The convention on Windows is "search the launch directory, then current
> directory, then %windows%\system32, then %PATH% for DLLs". No lib. No bin.
> 
> "Because Michael says so" isn't a good justification.

It is actually bin, because there is no distinction between bin and lib on
Windows. It loads DLLs from the same directory as executables. This is what I
am trying to say. Please look at the bin directory of OpenJDK 11 on Windows.
DLLs and EXEs side by side.

> > > I don't like that the answer to the question "where do I put my tcnative 
> > > and
> > > APR libraries?" is "it depends".
> > 
> > As mentioned by Rémy, at best the OS package manager does that, at worst you
> > compile your own with GNU autoconf and in most cases it will either go to
> > /usr/local/lib on BSD or /opt/<package>/lib on System V Unices.
> 
> You are going in circles. It doesn't matter what GNU autoconf does, or what
> the tcnative build process itself does. Or what nmake/cname/vstudiowhatever
> does. It matters where Tomcat bundles those output artifacts. Neither GNU
> autoconf nor make nor any other tool should be dropping binaries directly
> into another application (i.e. Tomcat).

Though I do not fully understand why I am going circles here, I agree with that
> Neither GNU
> autoconf nor make nor any other tool should be dropping binaries directly
> into another application (i.e. Tomcat).

This would mean that we remove the loading of native libraries from
CATALINA_HOME/bin in Tomcat 10 as well as from the build.xml. They have always
to be externally hosted.

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reply via email to