need to build a DLL for an openjdk test

[Lussier, Denis]

In my personal JDK6/7 experience from a couple years back, the Windows
OpenJDK build environment is an order of magnitude trickier to work thru
than the Linux one.    You need outdated versions of lots of tools,
utilities, environments, compilers and operating systems to get it all
right (a single binary that runs on old & new Windows versions with just a
simple non-root install with no rebooting).

In the end you get something that works darn well (although there were
still rough edges in the area of Swings Fonts and Sound a couple years
back).  Not suer if the Oracle propietary binaries still use non GPL
components in these areas on Windows.

--Luss



On Thu, Jun 4, 2015 at 4:18 AM, Staffan Larsen <staffan.larsen at oracle.com>
wrote:

>
> > On 4 jun 2015, at 07:10, David Holmes <david.holmes at oracle.com> wrote:
> >
> > Peter,
> >
> > On 4/06/2015 11:43 AM, Pete Brunet wrote:
> >> Cross posting to build-dev for possible insight regarding Jon's last
> >> paragraph below.
> >
> > See jdk/make/test/JtregNative.gmk and other references to test-image.
>
> There are example tests in jdk/test/native_sanity - take a look at those.
>
> /Staffan
>
> >
> > David
> >
> >> On 6/3/15 8:13 PM, Jonathan Gibbons wrote:
> >>>
> >>> On 06/03/2015 04:27 PM, Pete Brunet wrote:
> >>>> Hi, As part of my test I need to build a simple DLL and then load it
> >>>> from my test class.  Can jtreg build the DLL or will I need to create
> it
> >>>> and include it in my test directory?  -Pete
> >>>
> >>> jtreg cannot directly compile native code.  In theory, you could do it
> >>> in a shell script, but that immediately becomes a rats nest of "which
> >>> platform, and where do I find the compilers?"
> >>>
> >>> If you are talking about native code and tests in OpenJDK
> >>> repositories, then it is not acceptable to stash binaries in OpenJDK
> >>> repositories.  But, there is an infrastructure in place for an OpenJDK
> >>> build to build native libraries to be made available to test code.
> >>> Perhaps someone else on this list can explain how that works.
> >>>
> >>> -- Jon
> >>
>
>