You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@harmony.apache.org by Nathan Beyer <nd...@apache.org> on 2007/03/15 04:10:07 UTC
[awt] gl DLL for windows 200?
The current gl.dll that's part of the build with AWT has a dependency
on a uxtheme.dll, which isn't part of Windows 2000. Apparently it's a
Windows XP/2003 and above bit. As such, the gl.dll is failing to load
because this dependency is missing.
I'm not familiar with what's going on in the 'gl' library, but is this
dependency a requirement? Do we just need a Windows 2000 build?
-Nathan
Re: [awt] gl DLL for windows 200?
Posted by Nathan Beyer <nd...@apache.org>.
That sounds good to me. The only qualification I would have is that
the OS version be optional, such that if it's not included, the OS
family applies to all versions.
-Nathan
On 3/19/07, Alexey Varlamov <al...@gmail.com> wrote:
> No, "hy.os" has semantics of OS family name and is used accordingly,
> let's leave it as is.
> You might want to introduce a *new* property for that, like
> "hy.os.version" or "hy.os.flavor", and perform *additional* lookup for
> x-list using that property. IIRC we already had different failures on
> WinXP and Win2003 server, but our x-list machinery was not so advanced
> at that time. So let's add such feature now ;)
>
> 2007/3/19, Alexei Zakharov <al...@gmail.com>:
> > Well, I see. But the current scheme for exclude lists' names is:
> > exclude.${hy.os}.${hy.arch}.${hy.test.vm.name}
> >
> > So the last portion of the name is "hy.test.vm.name" - (originally)
> > the name of JVM to be run. In fact, if we like to add special support
> > for Windows 2000 we can encapsulate it in "hy.os" property. It is
> > "windows" for all windows platforms currently. However, it seems
> > Windows 2K can be detected through ant's condition:
> > <os name="Windows 2000">
> > since System.getProperty("os.name") returns "Windows 2000", at least
> > on all modern version of RI :) [1]. This way, we may choose some value
> > like "win2000" or "windows2k" and the resulted exclude list name will
> > look like:
> > exclude.windows2k.x86.ibm
> >
> > Thoughts?
> >
> > [1] http://tolstoy.com/samizdat/sysprops-windows.html
> >
> > Regards,
> >
> > 2007/3/17, Nathan Beyer <nd...@apache.org>:
> > > Note, the IBM VM works perfectly well on Windows 2000. It's just the
> > > class library code that doesn't. I think it would be more appropriate
> > > to be something like "exclude.x86.windows.2000"
> > >
> > > -Nathan
> > >
> > > On 3/16/07, Alexei Zakharov <al...@gmail.com> wrote:
> > > > > Is there a means of excluding tests for win 2000?
> > > >
> > > > Well, we may add it. For example choose some exotic vm name -
> > > > "ibm2000", "ibm2" or like it. The corresponding exclude list will have
> > > > name "exclude.windows.x86.ibm2000".
> > > >
> > > > Regards,
> > > >
> > > > 2007/3/15, Nathan Beyer <nd...@apache.org>:
> > > > > I think win 2000 is going to be a needed platform.
> > > > >
> > > > > Is there a means of excluding tests for win 2000? The build files are
> > > > > little deceiving as they indicate working for all win32 sdks.
> > > > >
> > > > > -Nathan
> > > > >
> > > > >
> > > > > On 3/15/07, Alexey Petrenko <al...@gmail.com> wrote:
> > > > > > 2007/3/15, Alexey Varlamov <al...@gmail.com>:
> > > > > > > It should be possible to made the dependency dynamic?
> > > > > > As I said before I'm not sure for now.
> > > > > > But yes, it is probably possible.
> > > > > >
> > > > > > And I do not think that this is very important task for now.
> > > > > >
> > > > > > SY, Alexey
> > > > > >
> > > > > > > Re Win2000 build in general - it might be of little interest right
> > > > > > > now, yet apparently has its niche and could be worth to address in
> > > > > > > some future (IMO).
> > > > > > >
> > > > > > > --
> > > > > > > Alexey
> > > > > > >
> > > > > > > 2007/3/15, Alexey Petrenko <al...@gmail.com>:
> > > > > > > > Yes, this is a requirement for now. Check WinThemeGraphics.cpp from awt
> > > > > > module.
> > > > > > > > I'm not sure can we remove this dependency or not.
> > > > > > > >
> > > > > > > > SY, Alexey
> > > > > > > >
> > > > > > > > 2007/3/15, Nathan Beyer <nd...@apache.org>:
> > > > > > > > > The current gl.dll that's part of the build with AWT has a dependency
> > > > > > > > > on a uxtheme.dll, which isn't part of Windows 2000. Apparently it's a
> > > > > > > > > Windows XP/2003 and above bit. As such, the gl.dll is failing to load
> > > > > > > > > because this dependency is missing.
> > > > > > > > >
> > > > > > > > > I'm not familiar with what's going on in the 'gl' library, but is this
> > > > > > > > > dependency a requirement? Do we just need a Windows 2000 build?
> >
> >
> > --
> > Alexei Zakharov,
> > Intel ESSD
> >
>
Re: [awt] gl DLL for windows 200?
Posted by Alexei Zakharov <al...@gmail.com>.
Well, I can't say I completely agree that "hy.os" has OS family
semantic. The whole picture looks like this. We have two properties:
hy.os - can be windows, linux, freebsd and aix; Mostly used to
distinguish different version of UNIX while building classlib natives
hy.os.family - only windows or unix; also used by native build where
fine grained OS selection is not required.
So as far as I can see on Windows "hy.os" and "hy.os.family" is the
same thing. So do we really need to add a new property? We can
probably replace current entries of "hy.os" with "hy.os.family" for
Windows makefiles. Thoughts?
Regards,
2007/3/19, Alexey Varlamov <al...@gmail.com>:
> No, "hy.os" has semantics of OS family name and is used accordingly,
> let's leave it as is.
> You might want to introduce a *new* property for that, like
> "hy.os.version" or "hy.os.flavor", and perform *additional* lookup for
> x-list using that property. IIRC we already had different failures on
> WinXP and Win2003 server, but our x-list machinery was not so advanced
> at that time. So let's add such feature now ;)
>
> 2007/3/19, Alexei Zakharov <al...@gmail.com>:
> > Well, I see. But the current scheme for exclude lists' names is:
> > exclude.${hy.os}.${hy.arch}.${hy.test.vm.name}
> >
> > So the last portion of the name is "hy.test.vm.name" - (originally)
> > the name of JVM to be run. In fact, if we like to add special support
> > for Windows 2000 we can encapsulate it in "hy.os" property. It is
> > "windows" for all windows platforms currently. However, it seems
> > Windows 2K can be detected through ant's condition:
> > <os name="Windows 2000">
> > since System.getProperty("os.name") returns "Windows 2000", at least
> > on all modern version of RI :) [1]. This way, we may choose some value
> > like "win2000" or "windows2k" and the resulted exclude list name will
> > look like:
> > exclude.windows2k.x86.ibm
> >
> > Thoughts?
> >
> > [1] http://tolstoy.com/samizdat/sysprops-windows.html
> >
> > Regards,
> >
> > 2007/3/17, Nathan Beyer <nd...@apache.org>:
> > > Note, the IBM VM works perfectly well on Windows 2000. It's just the
> > > class library code that doesn't. I think it would be more appropriate
> > > to be something like "exclude.x86.windows.2000"
> > >
> > > -Nathan
> > >
> > > On 3/16/07, Alexei Zakharov <al...@gmail.com> wrote:
> > > > > Is there a means of excluding tests for win 2000?
> > > >
> > > > Well, we may add it. For example choose some exotic vm name -
> > > > "ibm2000", "ibm2" or like it. The corresponding exclude list will have
> > > > name "exclude.windows.x86.ibm2000".
> > > >
> > > > Regards,
> > > >
> > > > 2007/3/15, Nathan Beyer <nd...@apache.org>:
> > > > > I think win 2000 is going to be a needed platform.
> > > > >
> > > > > Is there a means of excluding tests for win 2000? The build files are
> > > > > little deceiving as they indicate working for all win32 sdks.
> > > > >
> > > > > -Nathan
> > > > >
> > > > >
> > > > > On 3/15/07, Alexey Petrenko <al...@gmail.com> wrote:
> > > > > > 2007/3/15, Alexey Varlamov <al...@gmail.com>:
> > > > > > > It should be possible to made the dependency dynamic?
> > > > > > As I said before I'm not sure for now.
> > > > > > But yes, it is probably possible.
> > > > > >
> > > > > > And I do not think that this is very important task for now.
> > > > > >
> > > > > > SY, Alexey
> > > > > >
> > > > > > > Re Win2000 build in general - it might be of little interest right
> > > > > > > now, yet apparently has its niche and could be worth to address in
> > > > > > > some future (IMO).
> > > > > > >
> > > > > > > --
> > > > > > > Alexey
> > > > > > >
> > > > > > > 2007/3/15, Alexey Petrenko <al...@gmail.com>:
> > > > > > > > Yes, this is a requirement for now. Check WinThemeGraphics.cpp from awt
> > > > > > module.
> > > > > > > > I'm not sure can we remove this dependency or not.
> > > > > > > >
> > > > > > > > SY, Alexey
> > > > > > > >
> > > > > > > > 2007/3/15, Nathan Beyer <nd...@apache.org>:
> > > > > > > > > The current gl.dll that's part of the build with AWT has a dependency
> > > > > > > > > on a uxtheme.dll, which isn't part of Windows 2000. Apparently it's a
> > > > > > > > > Windows XP/2003 and above bit. As such, the gl.dll is failing to load
> > > > > > > > > because this dependency is missing.
> > > > > > > > >
> > > > > > > > > I'm not familiar with what's going on in the 'gl' library, but is this
> > > > > > > > > dependency a requirement? Do we just need a Windows 2000 build?
--
Alexei Zakharov,
Intel ESSD
Re: [awt] gl DLL for windows 200?
Posted by Alexey Varlamov <al...@gmail.com>.
No, "hy.os" has semantics of OS family name and is used accordingly,
let's leave it as is.
You might want to introduce a *new* property for that, like
"hy.os.version" or "hy.os.flavor", and perform *additional* lookup for
x-list using that property. IIRC we already had different failures on
WinXP and Win2003 server, but our x-list machinery was not so advanced
at that time. So let's add such feature now ;)
2007/3/19, Alexei Zakharov <al...@gmail.com>:
> Well, I see. But the current scheme for exclude lists' names is:
> exclude.${hy.os}.${hy.arch}.${hy.test.vm.name}
>
> So the last portion of the name is "hy.test.vm.name" - (originally)
> the name of JVM to be run. In fact, if we like to add special support
> for Windows 2000 we can encapsulate it in "hy.os" property. It is
> "windows" for all windows platforms currently. However, it seems
> Windows 2K can be detected through ant's condition:
> <os name="Windows 2000">
> since System.getProperty("os.name") returns "Windows 2000", at least
> on all modern version of RI :) [1]. This way, we may choose some value
> like "win2000" or "windows2k" and the resulted exclude list name will
> look like:
> exclude.windows2k.x86.ibm
>
> Thoughts?
>
> [1] http://tolstoy.com/samizdat/sysprops-windows.html
>
> Regards,
>
> 2007/3/17, Nathan Beyer <nd...@apache.org>:
> > Note, the IBM VM works perfectly well on Windows 2000. It's just the
> > class library code that doesn't. I think it would be more appropriate
> > to be something like "exclude.x86.windows.2000"
> >
> > -Nathan
> >
> > On 3/16/07, Alexei Zakharov <al...@gmail.com> wrote:
> > > > Is there a means of excluding tests for win 2000?
> > >
> > > Well, we may add it. For example choose some exotic vm name -
> > > "ibm2000", "ibm2" or like it. The corresponding exclude list will have
> > > name "exclude.windows.x86.ibm2000".
> > >
> > > Regards,
> > >
> > > 2007/3/15, Nathan Beyer <nd...@apache.org>:
> > > > I think win 2000 is going to be a needed platform.
> > > >
> > > > Is there a means of excluding tests for win 2000? The build files are
> > > > little deceiving as they indicate working for all win32 sdks.
> > > >
> > > > -Nathan
> > > >
> > > >
> > > > On 3/15/07, Alexey Petrenko <al...@gmail.com> wrote:
> > > > > 2007/3/15, Alexey Varlamov <al...@gmail.com>:
> > > > > > It should be possible to made the dependency dynamic?
> > > > > As I said before I'm not sure for now.
> > > > > But yes, it is probably possible.
> > > > >
> > > > > And I do not think that this is very important task for now.
> > > > >
> > > > > SY, Alexey
> > > > >
> > > > > > Re Win2000 build in general - it might be of little interest right
> > > > > > now, yet apparently has its niche and could be worth to address in
> > > > > > some future (IMO).
> > > > > >
> > > > > > --
> > > > > > Alexey
> > > > > >
> > > > > > 2007/3/15, Alexey Petrenko <al...@gmail.com>:
> > > > > > > Yes, this is a requirement for now. Check WinThemeGraphics.cpp from awt
> > > > > module.
> > > > > > > I'm not sure can we remove this dependency or not.
> > > > > > >
> > > > > > > SY, Alexey
> > > > > > >
> > > > > > > 2007/3/15, Nathan Beyer <nd...@apache.org>:
> > > > > > > > The current gl.dll that's part of the build with AWT has a dependency
> > > > > > > > on a uxtheme.dll, which isn't part of Windows 2000. Apparently it's a
> > > > > > > > Windows XP/2003 and above bit. As such, the gl.dll is failing to load
> > > > > > > > because this dependency is missing.
> > > > > > > >
> > > > > > > > I'm not familiar with what's going on in the 'gl' library, but is this
> > > > > > > > dependency a requirement? Do we just need a Windows 2000 build?
>
>
> --
> Alexei Zakharov,
> Intel ESSD
>
Re: [awt] gl DLL for windows 200?
Posted by Alexei Zakharov <al...@gmail.com>.
Well, I see. But the current scheme for exclude lists' names is:
exclude.${hy.os}.${hy.arch}.${hy.test.vm.name}
So the last portion of the name is "hy.test.vm.name" - (originally)
the name of JVM to be run. In fact, if we like to add special support
for Windows 2000 we can encapsulate it in "hy.os" property. It is
"windows" for all windows platforms currently. However, it seems
Windows 2K can be detected through ant's condition:
<os name="Windows 2000">
since System.getProperty("os.name") returns "Windows 2000", at least
on all modern version of RI :) [1]. This way, we may choose some value
like "win2000" or "windows2k" and the resulted exclude list name will
look like:
exclude.windows2k.x86.ibm
Thoughts?
[1] http://tolstoy.com/samizdat/sysprops-windows.html
Regards,
2007/3/17, Nathan Beyer <nd...@apache.org>:
> Note, the IBM VM works perfectly well on Windows 2000. It's just the
> class library code that doesn't. I think it would be more appropriate
> to be something like "exclude.x86.windows.2000"
>
> -Nathan
>
> On 3/16/07, Alexei Zakharov <al...@gmail.com> wrote:
> > > Is there a means of excluding tests for win 2000?
> >
> > Well, we may add it. For example choose some exotic vm name -
> > "ibm2000", "ibm2" or like it. The corresponding exclude list will have
> > name "exclude.windows.x86.ibm2000".
> >
> > Regards,
> >
> > 2007/3/15, Nathan Beyer <nd...@apache.org>:
> > > I think win 2000 is going to be a needed platform.
> > >
> > > Is there a means of excluding tests for win 2000? The build files are
> > > little deceiving as they indicate working for all win32 sdks.
> > >
> > > -Nathan
> > >
> > >
> > > On 3/15/07, Alexey Petrenko <al...@gmail.com> wrote:
> > > > 2007/3/15, Alexey Varlamov <al...@gmail.com>:
> > > > > It should be possible to made the dependency dynamic?
> > > > As I said before I'm not sure for now.
> > > > But yes, it is probably possible.
> > > >
> > > > And I do not think that this is very important task for now.
> > > >
> > > > SY, Alexey
> > > >
> > > > > Re Win2000 build in general - it might be of little interest right
> > > > > now, yet apparently has its niche and could be worth to address in
> > > > > some future (IMO).
> > > > >
> > > > > --
> > > > > Alexey
> > > > >
> > > > > 2007/3/15, Alexey Petrenko <al...@gmail.com>:
> > > > > > Yes, this is a requirement for now. Check WinThemeGraphics.cpp from awt
> > > > module.
> > > > > > I'm not sure can we remove this dependency or not.
> > > > > >
> > > > > > SY, Alexey
> > > > > >
> > > > > > 2007/3/15, Nathan Beyer <nd...@apache.org>:
> > > > > > > The current gl.dll that's part of the build with AWT has a dependency
> > > > > > > on a uxtheme.dll, which isn't part of Windows 2000. Apparently it's a
> > > > > > > Windows XP/2003 and above bit. As such, the gl.dll is failing to load
> > > > > > > because this dependency is missing.
> > > > > > >
> > > > > > > I'm not familiar with what's going on in the 'gl' library, but is this
> > > > > > > dependency a requirement? Do we just need a Windows 2000 build?
--
Alexei Zakharov,
Intel ESSD
Re: [awt] gl DLL for windows 200?
Posted by Nathan Beyer <nd...@apache.org>.
Note, the IBM VM works perfectly well on Windows 2000. It's just the
class library code that doesn't. I think it would be more appropriate
to be something like "exclude.x86.windows.2000"
-Nathan
On 3/16/07, Alexei Zakharov <al...@gmail.com> wrote:
> > Is there a means of excluding tests for win 2000?
>
> Well, we may add it. For example choose some exotic vm name -
> "ibm2000", "ibm2" or like it. The corresponding exclude list will have
> name "exclude.windows.x86.ibm2000".
>
> Regards,
>
> 2007/3/15, Nathan Beyer <nd...@apache.org>:
> > I think win 2000 is going to be a needed platform.
> >
> > Is there a means of excluding tests for win 2000? The build files are
> > little deceiving as they indicate working for all win32 sdks.
> >
> > -Nathan
> >
> >
> > On 3/15/07, Alexey Petrenko <al...@gmail.com> wrote:
> > > 2007/3/15, Alexey Varlamov <al...@gmail.com>:
> > > > It should be possible to made the dependency dynamic?
> > > As I said before I'm not sure for now.
> > > But yes, it is probably possible.
> > >
> > > And I do not think that this is very important task for now.
> > >
> > > SY, Alexey
> > >
> > > > Re Win2000 build in general - it might be of little interest right
> > > > now, yet apparently has its niche and could be worth to address in
> > > > some future (IMO).
> > > >
> > > > --
> > > > Alexey
> > > >
> > > > 2007/3/15, Alexey Petrenko <al...@gmail.com>:
> > > > > Yes, this is a requirement for now. Check WinThemeGraphics.cpp from awt
> > > module.
> > > > > I'm not sure can we remove this dependency or not.
> > > > >
> > > > > SY, Alexey
> > > > >
> > > > > 2007/3/15, Nathan Beyer <nd...@apache.org>:
> > > > > > The current gl.dll that's part of the build with AWT has a dependency
> > > > > > on a uxtheme.dll, which isn't part of Windows 2000. Apparently it's a
> > > > > > Windows XP/2003 and above bit. As such, the gl.dll is failing to load
> > > > > > because this dependency is missing.
> > > > > >
> > > > > > I'm not familiar with what's going on in the 'gl' library, but is this
> > > > > > dependency a requirement? Do we just need a Windows 2000 build?
> > > > > >
> > > > > > -Nathan
>
>
> --
> Alexei Zakharov,
> Intel ESSD
>
Re: [awt] gl DLL for windows 200?
Posted by Alexei Zakharov <al...@gmail.com>.
> Is there a means of excluding tests for win 2000?
Well, we may add it. For example choose some exotic vm name -
"ibm2000", "ibm2" or like it. The corresponding exclude list will have
name "exclude.windows.x86.ibm2000".
Regards,
2007/3/15, Nathan Beyer <nd...@apache.org>:
> I think win 2000 is going to be a needed platform.
>
> Is there a means of excluding tests for win 2000? The build files are
> little deceiving as they indicate working for all win32 sdks.
>
> -Nathan
>
>
> On 3/15/07, Alexey Petrenko <al...@gmail.com> wrote:
> > 2007/3/15, Alexey Varlamov <al...@gmail.com>:
> > > It should be possible to made the dependency dynamic?
> > As I said before I'm not sure for now.
> > But yes, it is probably possible.
> >
> > And I do not think that this is very important task for now.
> >
> > SY, Alexey
> >
> > > Re Win2000 build in general - it might be of little interest right
> > > now, yet apparently has its niche and could be worth to address in
> > > some future (IMO).
> > >
> > > --
> > > Alexey
> > >
> > > 2007/3/15, Alexey Petrenko <al...@gmail.com>:
> > > > Yes, this is a requirement for now. Check WinThemeGraphics.cpp from awt
> > module.
> > > > I'm not sure can we remove this dependency or not.
> > > >
> > > > SY, Alexey
> > > >
> > > > 2007/3/15, Nathan Beyer <nd...@apache.org>:
> > > > > The current gl.dll that's part of the build with AWT has a dependency
> > > > > on a uxtheme.dll, which isn't part of Windows 2000. Apparently it's a
> > > > > Windows XP/2003 and above bit. As such, the gl.dll is failing to load
> > > > > because this dependency is missing.
> > > > >
> > > > > I'm not familiar with what's going on in the 'gl' library, but is this
> > > > > dependency a requirement? Do we just need a Windows 2000 build?
> > > > >
> > > > > -Nathan
--
Alexei Zakharov,
Intel ESSD
Re: [awt] gl DLL for windows 200?
Posted by Nathan Beyer <nd...@apache.org>.
Maybe I'm inferring it, but x86 and Windows equals Win32. We're using
different monikers for 64bit OSes, correct?
Does this problem pop-up in Linux? There are various kernel versions,
correct? I presume we can't support all versions of the Linux kernel.
-Nathan
On 3/16/07, Alexey Varlamov <al...@gmail.com> wrote:
> > > Is there a means of excluding tests for win 2000?
> No, current builds are not capable of OS flavours differentiation,
> family only. Feel free to file a new JIRA.
>
> >> The build files are
> > > little deceiving as they indicate working for all win32 sdks.
> > In fact AWT code will not work with Win9x. Since it uses GDI+
> There is a lot of staff in DRLVM too which is unsupported on Win9x.
> Who calls it win32? ;)
>
> --
> Alexey
>
Re: [awt] gl DLL for windows 200?
Posted by Alexey Varlamov <al...@gmail.com>.
> > Is there a means of excluding tests for win 2000?
No, current builds are not capable of OS flavours differentiation,
family only. Feel free to file a new JIRA.
>> The build files are
> > little deceiving as they indicate working for all win32 sdks.
> In fact AWT code will not work with Win9x. Since it uses GDI+
There is a lot of staff in DRLVM too which is unsupported on Win9x.
Who calls it win32? ;)
--
Alexey
Re: [awt] gl DLL for windows 200?
Posted by Alexey Petrenko <al...@gmail.com>.
2007/3/15, Nathan Beyer <nd...@apache.org>:
> I think win 2000 is going to be a needed platform.
It looks like we can remove this dependency as requirement.
Please file a JIRA.
> Is there a means of excluding tests for win 2000? The build files are
> little deceiving as they indicate working for all win32 sdks.
In fact AWT code will not work with Win9x. Since it uses GDI+
SY, Alexey
> On 3/15/07, Alexey Petrenko <al...@gmail.com> wrote:
> > 2007/3/15, Alexey Varlamov <al...@gmail.com>:
> > > It should be possible to made the dependency dynamic?
> > As I said before I'm not sure for now.
> > But yes, it is probably possible.
> >
> > And I do not think that this is very important task for now.
> >
> > SY, Alexey
> >
> > > Re Win2000 build in general - it might be of little interest right
> > > now, yet apparently has its niche and could be worth to address in
> > > some future (IMO).
> > >
> > > --
> > > Alexey
> > >
> > > 2007/3/15, Alexey Petrenko <al...@gmail.com>:
> > > > Yes, this is a requirement for now. Check WinThemeGraphics.cpp from awt
> > module.
> > > > I'm not sure can we remove this dependency or not.
> > > >
> > > > SY, Alexey
> > > >
> > > > 2007/3/15, Nathan Beyer <nd...@apache.org>:
> > > > > The current gl.dll that's part of the build with AWT has a dependency
> > > > > on a uxtheme.dll, which isn't part of Windows 2000. Apparently it's a
> > > > > Windows XP/2003 and above bit. As such, the gl.dll is failing to load
> > > > > because this dependency is missing.
> > > > >
> > > > > I'm not familiar with what's going on in the 'gl' library, but is this
> > > > > dependency a requirement? Do we just need a Windows 2000 build?
> > > > >
> > > > > -Nathan
> > > > >
> > > >
> > >
> >
>
Re: [awt] gl DLL for windows 200?
Posted by Nathan Beyer <nd...@apache.org>.
I think win 2000 is going to be a needed platform.
Is there a means of excluding tests for win 2000? The build files are
little deceiving as they indicate working for all win32 sdks.
-Nathan
On 3/15/07, Alexey Petrenko <al...@gmail.com> wrote:
> 2007/3/15, Alexey Varlamov <al...@gmail.com>:
> > It should be possible to made the dependency dynamic?
> As I said before I'm not sure for now.
> But yes, it is probably possible.
>
> And I do not think that this is very important task for now.
>
> SY, Alexey
>
> > Re Win2000 build in general - it might be of little interest right
> > now, yet apparently has its niche and could be worth to address in
> > some future (IMO).
> >
> > --
> > Alexey
> >
> > 2007/3/15, Alexey Petrenko <al...@gmail.com>:
> > > Yes, this is a requirement for now. Check WinThemeGraphics.cpp from awt
> module.
> > > I'm not sure can we remove this dependency or not.
> > >
> > > SY, Alexey
> > >
> > > 2007/3/15, Nathan Beyer <nd...@apache.org>:
> > > > The current gl.dll that's part of the build with AWT has a dependency
> > > > on a uxtheme.dll, which isn't part of Windows 2000. Apparently it's a
> > > > Windows XP/2003 and above bit. As such, the gl.dll is failing to load
> > > > because this dependency is missing.
> > > >
> > > > I'm not familiar with what's going on in the 'gl' library, but is this
> > > > dependency a requirement? Do we just need a Windows 2000 build?
> > > >
> > > > -Nathan
> > > >
> > >
> >
>
Re: [awt] gl DLL for windows 200?
Posted by Alexey Petrenko <al...@gmail.com>.
2007/3/15, Alexey Varlamov <al...@gmail.com>:
> It should be possible to made the dependency dynamic?
As I said before I'm not sure for now.
But yes, it is probably possible.
And I do not think that this is very important task for now.
SY, Alexey
> Re Win2000 build in general - it might be of little interest right
> now, yet apparently has its niche and could be worth to address in
> some future (IMO).
>
> --
> Alexey
>
> 2007/3/15, Alexey Petrenko <al...@gmail.com>:
> > Yes, this is a requirement for now. Check WinThemeGraphics.cpp from awt module.
> > I'm not sure can we remove this dependency or not.
> >
> > SY, Alexey
> >
> > 2007/3/15, Nathan Beyer <nd...@apache.org>:
> > > The current gl.dll that's part of the build with AWT has a dependency
> > > on a uxtheme.dll, which isn't part of Windows 2000. Apparently it's a
> > > Windows XP/2003 and above bit. As such, the gl.dll is failing to load
> > > because this dependency is missing.
> > >
> > > I'm not familiar with what's going on in the 'gl' library, but is this
> > > dependency a requirement? Do we just need a Windows 2000 build?
> > >
> > > -Nathan
> > >
> >
>
Re: [awt] gl DLL for windows 200?
Posted by Alexey Varlamov <al...@gmail.com>.
It should be possible to made the dependency dynamic?
Re Win2000 build in general - it might be of little interest right
now, yet apparently has its niche and could be worth to address in
some future (IMO).
--
Alexey
2007/3/15, Alexey Petrenko <al...@gmail.com>:
> Yes, this is a requirement for now. Check WinThemeGraphics.cpp from awt module.
> I'm not sure can we remove this dependency or not.
>
> SY, Alexey
>
> 2007/3/15, Nathan Beyer <nd...@apache.org>:
> > The current gl.dll that's part of the build with AWT has a dependency
> > on a uxtheme.dll, which isn't part of Windows 2000. Apparently it's a
> > Windows XP/2003 and above bit. As such, the gl.dll is failing to load
> > because this dependency is missing.
> >
> > I'm not familiar with what's going on in the 'gl' library, but is this
> > dependency a requirement? Do we just need a Windows 2000 build?
> >
> > -Nathan
> >
>
Re: [awt] gl DLL for windows 200?
Posted by Alexey Petrenko <al...@gmail.com>.
Yes, this is a requirement for now. Check WinThemeGraphics.cpp from awt module.
I'm not sure can we remove this dependency or not.
SY, Alexey
2007/3/15, Nathan Beyer <nd...@apache.org>:
> The current gl.dll that's part of the build with AWT has a dependency
> on a uxtheme.dll, which isn't part of Windows 2000. Apparently it's a
> Windows XP/2003 and above bit. As such, the gl.dll is failing to load
> because this dependency is missing.
>
> I'm not familiar with what's going on in the 'gl' library, but is this
> dependency a requirement? Do we just need a Windows 2000 build?
>
> -Nathan
>