CCing: build-dev, macosx-port-dev
Request for review of JDK-8016096:
https://bugs.openjdk.java.net/browse/JDK-8016096
Proposed changes:
http://cr.openjdk.java.net/~ddehaven/8016096/
Significant build system changes for this one so feedback from build-dev is
appreciated. Actual functional chang
CCing: build-dev, macosx-port-dev, hotspot-dev
Request for review of JDK-8025673:
https://bugs.openjdk.java.net/browse/JDK-8025673
Proposed changes:
http://cr.openjdk.java.net/~ddehaven/8025673/
This change disables building libawt_xawt.dylib and libawt_headless.dylib on
Mac since they are not
Thanks guys.
Anthony, can you sponsor this for me?
-DrD-
> This fix looks fine to me as well.
>
> --
> best regards,
> Anthony
>
> On 10/20/2013 11:56 PM, David DeHaven wrote:
>>
>> CCing: build-dev, macosx-port-dev, hotspot-dev
>>
>>
well.
>>
>> --
>> best regards,
>> Anthony
>>
>> On 10/20/2013 11:56 PM, David DeHaven wrote:
>>>
>>> CCing: build-dev, macosx-port-dev, hotspot-dev
>>>
>>> Request for review of JDK-8025673:
>>> https://bugs.openjd
Anthony, can you sponsor this for me?
>>
>> -DrD-
>>
>>> This fix looks fine to me as well.
>>>
>>> --
>>> best regards,
>>> Anthony
>>>
>>> On 10/20/2013 11:56 PM, David DeHaven wrote:
>>>>
>>>&g
on Mac will be to force it with
>> the system property. It works this way on Windows, but on Windows we're
>> sure that WToolkit can run even without a UI session. Is it also true on
>> Mac? Did you try to launch AWT without -Djava.awt.headless=true from
>> remote console
headless on Mac will be to force it with the
>>>> system property. It works this way on Windows, but on Windows we're sure
>>>> that WToolkit can run even without a UI session. Is it also true on Mac?
>>>> Did you try to launch AWT without -Djava.awt.headless=true f
automatically in java.awt.Toolkit.getDefaultToolkit().
>
> A reliable way to test it is, I guess, as follows: log out of your GUI
> session, ssh to the Mac box, and try running a headless app (e.g. a printing
> jtreg test.)
>
> --
> best regards,
> Anthony
>
&g
ur GUI
> session, ssh to the Mac box, and try running a headless app (e.g. a printing
> jtreg test.)
>
> --
> best regards,
> Anthony
>
> On 10/22/2013 10:15 PM, David DeHaven wrote:
>>
>> [removing hotspot-dev and build-dev..]
>>
>> I can&
> Hi there mac porters :-)
>
> When I fiddled with the build system for using freetype in the OpenJDK
> builds, it turned out a couple of inconsistencies regarding freetype on
> macosx.
>
> The current build system actually requires freetype to be present when
> building. When building libfon
> You might have managed to build, but there will be some things that do not run
> without freetype.
>
> You could try using java.awt.Font.createFont(..) with a Postscript Type 1
> font - this
> doesn't need a head if you pass in -Djava.awt.headless=true - and I am
> 99.999%
> sure you'll get
> Back in September when I had Mountain Lion (OS X 10.8) I was able to build my
> own version of OpenJDK 7 Update 40.
>
> Now I have Mavericks (OS X 10.9) and it fails to build Hotspot with the error:
>
>> clang: error: argument unused during compilation: '-fcheck-new’
>
> If I comment out the
t;
>> Having multiple XCode versions installed is also a work-around.
>>
>> /Staffan
>>
>>>
>>> William
>>>
>>> On 9 Dec 2013, at 6:26pm, David DeHaven wrote:
>>>
>>>>
>>>>> Back in September when I had Mountai
> when I drag something over a Finder window that is partially in the
> background it automatically brings itself in the background after a
> short delay. Is this something I have to specifically program into my
> Java application or is there some global flag/property to activate
> this behavior o
> Hi,
>
> I've noticed a problem with key events in applets - specifically, "key
> released" are being inappropriately generated for some keys and not generated
> at all for other keys. I have a small demo applet, live version is here:
>
> http://bluej.org/davmac/KeyApplet.html
There are seve
> Is the AppleScript engine no longer not even the default one but no longer
> shipped?
> My HalfPipe application has some launch dependencies on it being there. It
> was throwing NPE's apparently not getting the engine.
> I stuck in some code to list out available engines and get…
What Java ve
> Just noticed this in Console.app when launching an application without an
> embedded JRE…
>
> 2/22/14 5:57:39.093 PM JavaAppLauncher[5669]: objc[5669]: Class
> JavaLaunchHelper is implemented in both /Library/Internet
> Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/lib/jli/libjli.dylib and
> I think I asked this before. I'm not sure it was answered, not remembering
> the answer anyhow.
> Should java System.getenv pick up ones that are added with LSEnvironment in
> the Info.plist file?
> It doesn't seem to.
> What would be a workaround for java code that depends on things like a H
>>> Just noticed this in Console.app when launching an application without an
>>> embedded JRE…
>>>
>>> 2/22/14 5:57:39.093 PM JavaAppLauncher[5669]: objc[5669]: Class
>>> JavaLaunchHelper is implemented in both /Library/Internet
>>> Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/lib/jli/libjl
> Application. Signed, not sandboxed. Something recently, Lion -> Mountain Lion
> maybe? seemed not to work unless I signed it. So I self-signed. I first
> looked at this a while ago I think before it was even signed and still
> couldn't get it to work.
I don't know what the core issue is but
>> Requiring R_HOME to be set in the environment seems sketchy to me. At worst
>> you should be able to set it through a system property, not rely on the
>> environment. Is it open source? Maybe it could be fixed and contributed back.
>>
>> The ugly workaround might be to drill down through JNI
> $ sudo rm -r /Library/Java/JavaVirtualMachines/jdk1.8.0.jdk
> $ java_home -V
> Matching Java Virtual Machines (3):
>1.7.0_51, x86_64: "Java SE 7"
> /Library/Java/JavaVirtualMachines/jdk1.7.0_51.jdk/Contents/Home
>1.6.0_65-b14-462, x86_64: "Java SE 6"
> /System/Library/Java/Ja
You may want to join the OpenJFX mailing list, the developers working on JavaFX
packager are more likely to see packager questions over there.
openjfx-...@openjdk.java.net
-DrD-
> Hi,
>
> using javafxpackager -deploy on a jar with SplashScreen in the manifest.mf
> will not create an entity in
Is anyone using JavaAppLauncher in jdk/src/macosx/bundle/JavaAppLauncher?
I'm going to be posting a review to remove it and the associated Java source as
it's completely unused in the JDK (and hence does not belong there). If you
want to continue to use it, then you'll need to fork it and maint
> I might keep in mind there is still…
> https://bitbucket.org/infinitekind/appbundler
If it's truly a fork of AppBundler then it doesn't use it. AppBundler has it's
own launcher code, the executable it produces is also called JavaAppLauncher
(and may have been based on this). The Java class us
>>> I might keep in mind there is still…
>>> https://bitbucket.org/infinitekind/appbundler
>>
>> If it's truly a fork of AppBundler then it doesn't use it. AppBundler has
>> it's own launcher code, the executable it produces is also called
>> JavaAppLauncher (and may have been based on this). T
Yes, for the most part. If the questions tend to be more about specific parts
of the JRE then those are better directed toward their respective mailing
lists, e.g., AWT questions should be directed to awt-...@openjdk.java.net
-DrD-
> Thanks. That's good to know. Is this still the right mailing
Since you're asking about Swing, it may be better to raise this on the
swing-dev mailing list.
>>>
>>> I dont see why as the issue is very much specific to OSX
>>
>> Agreed, but I guess the Swing people unfortunately don't necessarily read
>> this list..
>
> I think there's a need
Are you linking against JavaVM.framework? If you just need the JNI headers,
it's better to use those provided in the JDK (the headers are even correct
these days...). You shouldn't need to link anything to just open and use
libjvm. This is generally true for JNI libraries too since native metho
>> Are you linking against JavaVM.framework?
>
> If you’re not using Xcode but instead gcc somehow that would be…
> -framework JavaVM
> If you’re trying for a single launcher that will work with multiple versions
> of the framework. I’m not sure how that would work.
Using -framework JavaVM used
> -F/System/Library/Frameworks/JavaVM.framework/Frameworks
I've stopped relying on any headers ever appearing in
/System/Library/Frameworks, use ${SDKROOT}/System/Library/Frameworks instead.
If you're not using Xcode you can use xcrun to get a path to the SDK:
$ xcrun --show-sdk-path
/Applicati
We have this nice little comment in common/autoconf/jdk-options.m4:
# On Macosx universal binaries are produced, but they only contain
# 64 bit intel. This invalidates control of which jvms are built
# from configure, but only server is valid anyway. Fix this
# whe
I don't know why Hotspot is packaged as a universal binary. In the jdk,
only libJObjC was built as a universal binary and that lib was removed
before JDK 8 shipped. What part of Macosx would need to interact
directly with libjvm.dylib in a way that required a (fake) universal
>
What version of the javafxpackager? Try using the latest in the 8u40 EA builds
if you haven't already. You should still be able to bundle Java 7 with it if
your app doesn't run with 8.
-DrD-
> Thank you all for your suggestions.
> Just to be clear, this error happens for very few users in a sa
>> Are you linking against JavaVM.framework? If you just need the JNI
>> headers, it's better to use those provided in the JDK (the headers are
>> even correct these days...). You shouldn't need to link anything to
>> just open and use libjvm. This is generally true for JNI libraries too
>> since
>>> Follow-up question here: I'm trying to use autoconf to identify the
>>> location of the proper include directories and libraries for subsequent
>>> use of libtool to create a .libjni JNI dynamic library.
>>
>> You should be using .dylib for JNI libs these days.
>
> Please excuse my ignorance
>>>
>>> Please excuse my ignorance, but
>>>
>>> Why?
>>> And what's the difference?
>>
>> .dylib is the standard extension used by the dynamic loader on OSX, .jnilib
>> was originally used by Apples JRE specifically for JNI libraries and (I
>> believe) we’ve never really supported it except t
> In case anyone's interested, the answer to my original question is
>
> http://www.gnu.org/software/autoconf-archive/ax_jni_include_dir.html
Ah, nice find!
-DrD-
Follow-up question here: I'm trying to use autoconf to identify the
location of the proper include directories and libraries for subsequent
use of libtool to create a .libjni JNI dynamic library.
>>>
>>> You should be using .dylib for JNI libs these days.
>>
>> Please excuse
> Hi again,
>
> Some time ago, I noticed a strange issue in applets that happen with Safari,
> and not with Firefox and Chrome:
> As the two following screen captures show clearly
> http://www.sweethome3d.com/images/forum/IssueWithSweetHome3DOnlineUnderSafari.jpg
> http://www.sweethome3d.com/ima
It’d be more helpful to know what the NSException was. Without that
information, it’s nearly impossible to figure out what’s going on from the
stack trace alone. Debug symbols would help too, but if you’re using Java
Packager that won’t be an option (sounds like an RFE waiting to happen..).
Whi
>
> Curious. I just started jconsole to watch memory usage for a java
> application. It shows a non-mac in-frame menubar?
> With just jconsole….
> which jconsole
> /usr/bin/jconsole
>
> ls -l /usr/bin/jconsole
> lrwxr-xr-x 1 root wheel 78 Sep 16 19:13 /usr/bin/jconsole ->
> /System/Library/
>> Brief question. What is the recommended deployment tool for applications at
>> this time?
>
> Found that there had been some discussion on the Kenai AppBundler list that
> mentioned javapackager. Looking at that now.
Java Packager included with the JDK is under (very) active development. Th
> Less brief background.
> I’ve installed the java 9 ea releases. A while back for the jdk, today the
> jre as well.
Be careful with those... 9 is undergoing a lot of changes so results may vary
between ea releases. I highly recommend sticking with JDK 8 releases for now,
especially for produc
>> http://www.jwrapper.com
>>
>
> There are alternatives that can be found I came across…
> https://github.com/joshmarinacci/AppBundler
There's an unofficial fork of AppBundler that's being maintained by (?) at
BitBucket, those who were involved with the now defunct AppBundler Kenai
project d
>>> Less brief background.
>>> I’ve installed the java 9 ea releases. A while back for the jdk, today the
>>> jre as well.
>>
>> Be careful with those... 9 is undergoing a lot of changes so results may
>> vary between ea releases. I highly recommend sticking with JDK 8 releases
>> for now, esp
> Since I do most of my testing with one particular application of my own. I
> was trying to figure out how to embed Java 9 JRE or JDK into a copy of the
> application.
> I haven’t done that much with embedding. It seemed to indicate different
> files missing. I was thinking this was because t
>> Sorry, should wait until I’m done here before updating.
>
> Started over for (default) 1.8 embedded jdk. I think I made the same changes.
> No go. Seems to be launching for a second. Then disappears with nothing in
> console.
> Think I’ll leave it at that for today. Maybe try a simpler app
> It was suggested on the jigsaw-dev list that I raise this issue here.
> The jeps command appears to have no /usr/bin symlink.
>
> which jdeps
> /Library/Java/JavaVirtualMachines/jdk1.8.0_40.jdk/Contents/Home/bin/jdeps
>
> I believe this command was introduced with JDK 8.
>
> One thing that I
> I just wonder if there wouldn’t be some way to have a platform wide
> mechanism. Build something in the java installer maybe that makes sure the
> complete set of /usr/bin links is there?
> Or if scripts like this start getting to OS X with /usr/bin/jdeps they will
> break.
The issue (for O
Fix looks good to me too.
-DrD-
> On Jun 29, 2016, at 12:54 PM, Gerard Ziemski
> wrote:
>
> hi Brent,
>
> Thank you for fixing the original issue and for putting in this follow-up fix!
>
> Looks good! (for full disclosure I proposed the workaround)
>
>
> cheers
>
>> On Jun 29, 2016, at 2
51 matches
Mail list logo
