From dennis.eder at etas.com Mon Feb 1 09:22:41 2016 From: dennis.eder at etas.com (Eder Dennis (ETAS/ESY3)) Date: Mon, 1 Feb 2016 09:22:41 +0000 Subject: Scenebuilder 8.1.0 removes Licensing / Copyright Terms and all other comments, worked with v8.0.0 Message-ID: Hi FX'lers, I want to inform everyone that the latest Gluon Scenebuilder 8.1.0, as available here http://gluonhq.com/open-source/scene-builder/ removes comments, in particular License Headers, e.g. This is a regression bug. Keeping comments was explicitly supported in earlier versions, as discussed here: https://community.oracle.com/message/11122448#11122448 Until this is fixed, I recommend to continue using Scenebuilder 8.0.0 It saved the comment back as is. Unfortunately that version does no longer seem to be available on http://gluonhq.com Best regards, Dennis?????????????????????? From hastebrot at gmail.com Mon Feb 1 09:35:46 2016 From: hastebrot at gmail.com (Benjamin Gudehus) Date: Mon, 1 Feb 2016 10:35:46 +0100 Subject: Scenebuilder 8.1.0 removes Licensing / Copyright Terms and all other comments, worked with v8.0.0 In-Reply-To: References: Message-ID: >Until this is fixed, I recommend to continue using Scenebuilder 8.0.0 It saved the comment back as is. That's bad. Is it possible to host old archives on Bintray or even package scenebuilder as single jar and host it on maven central in the future? On Feb 1, 2016 10:23 AM, "Eder Dennis (ETAS/ESY3)" wrote: > Hi FX'lers, > > I want to inform everyone that the latest Gluon Scenebuilder 8.1.0, as > available here > http://gluonhq.com/open-source/scene-builder/ > removes comments, in particular License Headers, e.g. > > > > This is a regression bug. Keeping comments was explicitly supported in > earlier versions, as discussed here: > https://community.oracle.com/message/11122448#11122448 > > Until this is fixed, I recommend to continue using Scenebuilder 8.0.0 > It saved the comment back as is. > > Unfortunately that version does no longer seem to be available on > http://gluonhq.com > > Best regards, > Dennis > > From johan.vos at gluonhq.com Mon Feb 1 09:41:53 2016 From: johan.vos at gluonhq.com (Johan Vos) Date: Mon, 1 Feb 2016 10:41:53 +0100 Subject: Scenebuilder 8.1.0 removes Licensing / Copyright Terms and all other comments, worked with v8.0.0 In-Reply-To: References: Message-ID: Hi, Thanks for reporting this. We'll investigate it (both the issue and making old releases available somehow). - Johan On Mon, Feb 1, 2016 at 10:35 AM, Benjamin Gudehus wrote: > >Until this is fixed, I recommend to continue using Scenebuilder 8.0.0 > It saved the comment back as is. > > That's bad. Is it possible to host old archives on Bintray or even package > scenebuilder as single jar and host it on maven central in the future? > On Feb 1, 2016 10:23 AM, "Eder Dennis (ETAS/ESY3)" > wrote: > >> Hi FX'lers, >> >> I want to inform everyone that the latest Gluon Scenebuilder 8.1.0, as >> available here >> http://gluonhq.com/open-source/scene-builder/ >> removes comments, in particular License Headers, e.g. >> >> >> >> This is a regression bug. Keeping comments was explicitly supported in >> earlier versions, as discussed here: >> https://community.oracle.com/message/11122448#11122448 >> >> Until this is fixed, I recommend to continue using Scenebuilder 8.0.0 >> It saved the comment back as is. >> >> Unfortunately that version does no longer seem to be available on >> http://gluonhq.com >> >> Best regards, >> Dennis >> >> From dennis.eder at etas.com Mon Feb 1 10:27:52 2016 From: dennis.eder at etas.com (Eder Dennis (ETAS/ESY3)) Date: Mon, 1 Feb 2016 10:27:52 +0000 Subject: AW: Scenebuilder 8.1.0 removes Licensing / Copyright Terms and all other comments, worked with v8.0.0 In-Reply-To: References: Message-ID: Hi Johan, if you provided a hyperlink into the tagged OpenJdk source path repository for both your builds ?8.0.0.0? and ?8.1.0.0?, I could help you analyzing the DIFF as a community effort. Sometimes it is just a partially defined XML ?pretty print? instruction. Hopefully it is not an internal non-DOM representation that neglects XML comments altogether between import and export. Best regards, Dennis?????????????????????? From dennis.eder at etas.com Mon Feb 1 10:48:06 2016 From: dennis.eder at etas.com (Eder Dennis (ETAS/ESY3)) Date: Mon, 1 Feb 2016 10:48:06 +0000 Subject: AW: Scenebuilder 8.1.0 removes Licensing / Copyright Terms and all other comments, worked with v8.0.0 In-Reply-To: References: Message-ID: <46c5ee6aa686437a8e8539a1ee5b3894@FE-MBX1012.de.bosch.com> >> [?] or even package scenebuilder as single jar and host it on maven central in the future that is an interesting idea, Benjamin: self-executable, versioned JARs on Maven Central, incl. POM with build definitions. Unfortunately, Maven is lacking a scope "DEV" as in "NPM --save-dev" Gluon Scenebuilder 8.1.0.0 compile true Best regards, Dennis Von: Benjamin Gudehus [mailto:hastebrot at gmail.com] Gesendet: Montag, 1. Februar 2016 10:36 An: Eder Dennis (ETAS/ESY3) Cc: support at gluonhq.com; openjfx-dev at openjdk.java.net Betreff: Re: Scenebuilder 8.1.0 removes Licensing / Copyright Terms and all other comments, worked with v8.0.0 >Until this is fixed, I recommend to continue using Scenebuilder 8.0.0 It saved the comment back as is. That's bad. Is it possible to host old archives on Bintray or even package scenebuilder as single jar and host it on maven central in the future? On Feb 1, 2016 10:23 AM, "Eder Dennis (ETAS/ESY3)" wrote: Hi FX'lers, I want to inform everyone that the latest Gluon Scenebuilder 8.1.0, as available here http://gluonhq.com/open-source/scene-builder/ removes comments, in particular License Headers, e.g. This is a regression bug. Keeping comments was explicitly supported in earlier versions, as discussed here: https://community.oracle.com/message/11122448#11122448 Until this is fixed, I recommend to continue using Scenebuilder 8.0.0 It saved the comment back as is. Unfortunately that version does no longer seem to be available on http://gluonhq.com Best regards, Dennis?????????????????????? From joeri at lodgon.com Mon Feb 1 11:18:33 2016 From: joeri at lodgon.com (Joeri Sykora) Date: Mon, 1 Feb 2016 12:18:33 +0100 Subject: Scenebuilder 8.1.0 removes Licensing / Copyright Terms and all other comments, worked with v8.0.0 In-Reply-To: <46c5ee6aa686437a8e8539a1ee5b3894@FE-MBX1012.de.bosch.com> References: <46c5ee6aa686437a8e8539a1ee5b3894@FE-MBX1012.de.bosch.com> Message-ID: Hi Elder, I've already looked into it and found the culprit. So there is no more need for you to look further into it. I'll create a pull request with a fix for the bug once I've finalized it. Btw, there was already a bug report for this specific issue here: https://bitbucket.org/gluon-oss/scenebuilder/issues/53/comments-inside-fxml-are-removed Kind regards, Joeri Sykora 2016-02-01 11:48 GMT+01:00 Eder Dennis (ETAS/ESY3) : > >> [?] or even package scenebuilder as single jar and host it on maven > central in the future > that is an interesting idea, Benjamin: self-executable, versioned JARs on > Maven Central, incl. POM with build definitions. > Unfortunately, Maven is lacking a scope "DEV" as in "NPM --save-dev" > > > > Gluon > Scenebuilder > 8.1.0.0 > compile > true > > > > Best regards, > Dennis > > Von: Benjamin Gudehus [mailto:hastebrot at gmail.com] > Gesendet: Montag, 1. Februar 2016 10:36 > An: Eder Dennis (ETAS/ESY3) > Cc: support at gluonhq.com; openjfx-dev at openjdk.java.net > Betreff: Re: Scenebuilder 8.1.0 removes Licensing / Copyright Terms and > all other comments, worked with v8.0.0 > > >Until this is fixed, I recommend to continue using Scenebuilder 8.0.0 > It saved the comment back as is. > That's bad. Is it possible to host old archives on Bintray or even package > scenebuilder as single jar and host it on maven central in the future? > On Feb 1, 2016 10:23 AM, "Eder Dennis (ETAS/ESY3)" > wrote: > Hi FX'lers, > > I want to inform everyone that the latest Gluon Scenebuilder 8.1.0, as > available here > http://gluonhq.com/open-source/scene-builder/ > removes comments, in particular License Headers, e.g. > > > > This is a regression bug. Keeping comments was explicitly supported in > earlier versions, as discussed here: > https://community.oracle.com/message/11122448#11122448 > > Until this is fixed, I recommend to continue using Scenebuilder 8.0.0 > It saved the comment back as is. > > Unfortunately that version does no longer seem to be available on > http://gluonhq.com > > Best regards, > Dennis > From dennis.eder at etas.com Mon Feb 1 11:34:57 2016 From: dennis.eder at etas.com (Eder Dennis (ETAS/ESY3)) Date: Mon, 1 Feb 2016 11:34:57 +0000 Subject: AW: Scenebuilder 8.1.0 removes Licensing / Copyright Terms and all other comments, worked with v8.0.0 In-Reply-To: References: <46c5ee6aa686437a8e8539a1ee5b3894@FE-MBX1012.de.bosch.com> Message-ID: <9eb8f848dd914c1bbc8ec5e2b7204b9e@FE-MBX1012.de.bosch.com> That is great news, thank you Joeri! I did not know about that separate issue tracker on https://bitbucket.org/gluon-oss/scenebuilder, outside of openjdk's http://hg.openjdk.java.net/ Maybe Gluon can add hyperlink references from their binary downloads listings (http://gluonhq.com/open-source/scene-builder/) into that repository (e.g. https://bitbucket.org/gluon-oss/scenebuilder/commits/tag/8.1.0). Keep up the good work! Best regards, Dennis?Eder????????????????????? Von: Joeri Sykora [mailto:joeri at lodgon.com] Gesendet: Montag, 1. Februar 2016 12:19 An: Eder Dennis (ETAS/ESY3) Cc: Benjamin Gudehus; support at gluonhq.com; openjfx-dev at openjdk.java.net Betreff: Re: Scenebuilder 8.1.0 removes Licensing / Copyright Terms and all other comments, worked with v8.0.0 Hi Elder, I've already looked into it and found the culprit. So there is no more need for you to look further into it. I'll create a pull request with a fix for the bug once I've finalized it. Btw, there was already a bug report for this specific issue here:?https://bitbucket.org/gluon-oss/scenebuilder/issues/53/comments-inside-fxml-are-removed Kind regards, Joeri Sykora 2016-02-01 11:48 GMT+01:00 Eder Dennis (ETAS/ESY3) : >> [?] or even package scenebuilder as single jar and host it on maven central in the future that is an interesting idea, Benjamin: self-executable, versioned JARs on Maven Central, incl. POM with build definitions. Unfortunately, Maven is lacking a scope "DEV" as in "NPM --save-dev" ? ? ? ? ? ? Gluon ? ? ? Scenebuilder ? ? ? 8.1.0.0 ? ? ? compile ? ? ? true ? ? ? Best regards, Dennis Von: Benjamin Gudehus [mailto:hastebrot at gmail.com] Gesendet: Montag, 1. Februar 2016 10:36 An: Eder Dennis (ETAS/ESY3) Cc: support at gluonhq.com; openjfx-dev at openjdk.java.net Betreff: Re: Scenebuilder 8.1.0 removes Licensing / Copyright Terms and all other comments, worked with v8.0.0 >Until this is fixed, I recommend to continue using Scenebuilder 8.0.0 It saved the comment back as is. That's bad. Is it possible to host old archives on Bintray or even package scenebuilder as single jar and host it on maven central in the future? On Feb 1, 2016 10:23 AM, "Eder Dennis (ETAS/ESY3)" wrote: Hi FX'lers, I want to inform everyone that the latest Gluon Scenebuilder 8.1.0, as available here http://gluonhq.com/open-source/scene-builder/ removes comments, in particular License Headers, e.g. This is a regression bug. Keeping comments was explicitly supported in earlier versions, as discussed here: https://community.oracle.com/message/11122448#11122448 Until this is fixed, I recommend to continue using Scenebuilder 8.0.0 It saved the comment back as is. Unfortunately that version does no longer seem to be available on http://gluonhq.com Best regards, Dennis?????????????????????? From fastegal at swingempire.de Mon Feb 1 16:58:58 2016 From: fastegal at swingempire.de (fastegal at swingempire.de) Date: Mon, 01 Feb 2016 17:58:58 +0100 Subject: TableCellSkinBase: columnVisibility/Width should be protected In-Reply-To: <56AE6747.1070502@oracle.com> References: <20160129141405.Horde.2jX1HnboguNBRPF2zbIrQg1@webmail.df.eu> <56AE6747.1070502@oracle.com> Message-ID: <20160201175858.Horde.FLhfKBYPCWZakHd595m0Og1@webmail.df.eu> Zitat von Jonathan Giles : > In moving most of the skin code to public API (as part of JEP 253), > I worked with the plan of minimising the API as much as possible, > and would then spend time this year bringing API back out in a more > considered way (as opposed to dumping all skin code, warts and all, > into public API and making mistakes). I am happyto make more API > public, and have been encouraging people heavily at conferences to > start playing with JDK 9 _today_. Your bug is now on my radar - I > will look into it ASAP. > > -- Jonathan > shit happens - such as me not being the conference type Seriously, it's a sound plan. Currently I'm slowly moving my experiments to jdk9, stumbling across hidden methods several times per day (not everything a bug, just a change)- where do you want feedback? Thanks and cheers Jeanette From kevin.rushforth at oracle.com Mon Feb 1 20:59:55 2016 From: kevin.rushforth at oracle.com (Kevin Rushforth) Date: Mon, 01 Feb 2016 12:59:55 -0800 Subject: 9-dev unlocked following sanity testing Message-ID: <56AFC74B.2000006@oracle.com> From jonathan.giles at oracle.com Mon Feb 1 23:54:54 2016 From: jonathan.giles at oracle.com (Jonathan Giles) Date: Tue, 2 Feb 2016 12:54:54 +1300 Subject: TableCellSkinBase: columnVisibility/Width should be protected In-Reply-To: <20160201175858.Horde.FLhfKBYPCWZakHd595m0Og1@webmail.df.eu> References: <20160129141405.Horde.2jX1HnboguNBRPF2zbIrQg1@webmail.df.eu> <56AE6747.1070502@oracle.com> <20160201175858.Horde.FLhfKBYPCWZakHd595m0Og1@webmail.df.eu> Message-ID: <56AFF04E.6090200@oracle.com> Probably it is best to just email me directly rather than email the list multiple times per day. I'll bundle them up and review and make plans on what should happen for each. Eventually we'll end up with jira issues - which you're welcome to file directly - but I don't mind keeping the overhead low until we have logical chunks of work either. -- Jonathan On 2/02/16 5:58 AM, fastegal at swingempire.de wrote: > > Zitat von Jonathan Giles : > >> In moving most of the skin code to public API (as part of JEP 253), I >> worked with the plan of minimising the API as much as possible, and >> would then spend time this year bringing API back out in a more >> considered way (as opposed to dumping all skin code, warts and all, >> into public API and making mistakes). I am happyto make more API >> public, and have been encouraging people heavily at conferences to >> start playing with JDK 9 _today_. Your bug is now on my radar - I >> will look into it ASAP. >> >> -- Jonathan >> > > shit happens - such as me not being the conference type > > Seriously, it's a sound plan. Currently I'm slowly moving my > experiments to jdk9, stumbling across hidden methods several times per > day (not everything a bug, just a change)- where do you want feedback? > > Thanks and cheers > Jeanette > From a.ankit.srivastava at oracle.com Tue Feb 2 05:43:48 2016 From: a.ankit.srivastava at oracle.com (Ankit Srivastava) Date: Mon, 1 Feb 2016 21:43:48 -0800 (PST) Subject: [9] Review request for 8088689 : Several fast/regions/webkit-* tests fail Message-ID: <1ba40a7d-187e-4eeb-91c3-704e027e577b@default> Hi Guru, Kevin, Alexander, Please review the webrev : http://cr.openjdk.java.net/~arajkumar/ankit/8088689/webrev.00/ JBS: https://bugs.openjdk.java.net/browse/JDK-8088689 Casue : Css regions flag was not set. Added path to enable flag from WebPage init() method call. Tested on Win 64 and Linux 64, all test case getting passed. Regards, Ankit From swpalmer at gmail.com Tue Feb 2 21:36:09 2016 From: swpalmer at gmail.com (Scott Palmer) Date: Tue, 2 Feb 2016 16:36:09 -0500 Subject: Public API to find node at specific coordinates Message-ID: Do we have such an API yet? I found this: https://bugs.openjdk.java.net/browse/JDK-8091684 and: https://bugs.openjdk.java.net/browse/JDK-8099546 which is still unresolved (and 6 years old!), so I'm guessing no. Is it too late for Java 9? I need a way to forward events to a scene and have them dispatched to the correct node (mouse move, mouse press, etc.). I'm not finding an easy way to do it. Even a Java 9 solution is too late for me anyway. So if there is some reasonable way to implement it for Java 8 please let me know. (There used to be impl_pickNode(double, double) but now it is more complicated with PickRay and PickResultChooser and being undocumented I haven't managed to get it to do anything useful yet.) Scott From swpalmer at gmail.com Tue Feb 2 21:49:59 2016 From: swpalmer at gmail.com (Scott Palmer) Date: Tue, 2 Feb 2016 16:49:59 -0500 Subject: javapackager Message-ID: What's the best place to go to get help with using the javapackager ? I've read the docs, but things aren't working smoothly and it would be helpful if there were some known working examples to base things on. I'm not finding any examples that use the -daemon or -BserviceHint=true options, for example. I attempted to make a .rpm that installs a service/daemon but when I try to install it, it fails claiming the following dependencies cannot be met: libX11.so.6 is needed by myserver-1.0-1.x86_64 libXext.so.6 is needed by myserver-1.0-1.x86_64 libXi.so.6 is needed by myserver-1.0-1.x86_64 libXrender.so.1 is needed by myserver-1.0-1.x86_64 libXtst.so.6 is needed by myserver-1.0-1.x86_64 libasound.so.2 is needed by myserver-1.0-1.x86_64 Considering the app already runs fine on this same system, I'm a bit confused that it is complaining of missing dependencies. Scott From jonathan.giles at oracle.com Tue Feb 2 21:51:15 2016 From: jonathan.giles at oracle.com (Jonathan Giles) Date: Wed, 3 Feb 2016 10:51:15 +1300 Subject: Public API to find node at specific coordinates In-Reply-To: References: Message-ID: <56B124D3.7090704@oracle.com> Check out my blog post here: http://fxexperience.com/2016/01/node-picking-in-javafx/ It might be useful.... -- Jonathan On 3/02/16 10:36 AM, Scott Palmer wrote: > Do we have such an API yet? > I found this: > https://bugs.openjdk.java.net/browse/JDK-8091684 > and: > https://bugs.openjdk.java.net/browse/JDK-8099546 > which is still unresolved (and 6 years old!), so I'm guessing no. > > Is it too late for Java 9? > > I need a way to forward events to a scene and have them dispatched to the > correct node (mouse move, mouse press, etc.). I'm not finding an easy way > to do it. Even a Java 9 solution is too late for me anyway. So if there > is some reasonable way to implement it for Java 8 please let me know. > (There used to be impl_pickNode(double, double) but now it is more > complicated with PickRay and PickResultChooser and being undocumented I > haven't managed to get it to do anything useful yet.) > > Scott From chris.bensen at oracle.com Wed Feb 3 00:03:24 2016 From: chris.bensen at oracle.com (Chris Bensen) Date: Tue, 2 Feb 2016 16:03:24 -0800 Subject: javapackager In-Reply-To: References: Message-ID: <80465D9F-05F9-4F00-A51A-2598AB9FD0C9@oracle.com> This list or the Deployment blog (https://blogs.oracle.com/talkingjavadeployment/) are the best places to get help with the javapackager. Is your app built with the 64-bit or 32-bit packager? I noticed ?x86_64? appended to the name. If it?s 32-bit you could try running: sudo apt-get install libx11-6:i386 Chris > On Feb 2, 2016, at 1:49 PM, Scott Palmer wrote: > > What's the best place to go to get help with using the javapackager ? > > I've read the docs, but things aren't working smoothly and it would be > helpful if there were some known working examples to base things on. I'm > not finding any examples that use the -daemon or -BserviceHint=true > options, for example. > > I attempted to make a .rpm that installs a service/daemon but when I try to > install it, it fails claiming the following dependencies cannot be met: > > libX11.so.6 is needed by myserver-1.0-1.x86_64 > libXext.so.6 is needed by myserver-1.0-1.x86_64 > libXi.so.6 is needed by myserver-1.0-1.x86_64 > libXrender.so.1 is needed by myserver-1.0-1.x86_64 > libXtst.so.6 is needed by myserver-1.0-1.x86_64 > libasound.so.2 is needed by myserver-1.0-1.x86_64 > > Considering the app already runs fine on this same system, I'm a bit > confused that it is complaining of missing dependencies. > > Scott From swpalmer at gmail.com Wed Feb 3 01:07:19 2016 From: swpalmer at gmail.com (Scott Palmer) Date: Tue, 2 Feb 2016 20:07:19 -0500 Subject: javapackager In-Reply-To: <80465D9F-05F9-4F00-A51A-2598AB9FD0C9@oracle.com> References: <80465D9F-05F9-4F00-A51A-2598AB9FD0C9@oracle.com> Message-ID: <445BC429-7AD0-4000-AC4D-5506CBAAADA4@gmail.com> The ?-1.x86-64? is something that javapackager automatically appends. I just confirmed that $JAVA_HOME/bin/java -version indicates the 64-bit VM. I?m invoking javapackager via an Exec task in my Gradle build script. (I?m not using the JavaFX plugin because it has even less documentation, it does strange things like explicitly adding jfxrt.jar to the classpath even on Java 8, and it?s basically unmaintained now :-( .) Here is what my invocation looks like: def bundleVersion = project.version.split('-')[0] // remove -snapshot task javapackager(type: Exec, dependsOn: [checkRpmOrDebBased, prepareDistribution]) { executable "${System.getenv('JAVA_HOME')}/bin/javapackager" doFirst { args = [ '-deploy', '-native', project.packageType, // use deb or rpm for linux '-daemon', '-title', 'My Server', '-vendor', 'My Company', '-srcdir', "${buildDir}/extracted-dist", '-outdir', "${buildDir}", '-outfile', 'MyServer', '-name', 'MyServer', '-appclass', 'com.something.server.MyServerMain', //"-BappResources=${buildDir}/extracted-dist", // conflicts with -srcdir ? '-BuserJvmOptions=-Xmx=512m', '-BjvmProperties=java.util.logging.config.file=conf/logging.properties', "-BappVersion=${bundleVersion}", '-BmainJar=MyServer.jar', '-BlicenseFile=EULA.rtf', '-BsystemWide=true', //'-BserviceHint=true', // conflicts with -daemon ? '-BrunAtStartup=true', '-BstartOnInstall=true', '-BstopOnUninstall=true' ] } } ${buildDir}/extracted-dist contains a full layout of the application image. Scott > On Feb 2, 2016, at 7:03 PM, Chris Bensen wrote: > > This list or the Deployment blog (https://blogs.oracle.com/talkingjavadeployment/) are the best places to get help with the javapackager. > > Is your app built with the 64-bit or 32-bit packager? I noticed ?x86_64? appended to the name. If it?s 32-bit you could try running: > > sudo apt-get install libx11-6:i386 > > Chris > > >> On Feb 2, 2016, at 1:49 PM, Scott Palmer wrote: >> >> What's the best place to go to get help with using the javapackager ? >> >> I've read the docs, but things aren't working smoothly and it would be >> helpful if there were some known working examples to base things on. I'm >> not finding any examples that use the -daemon or -BserviceHint=true >> options, for example. >> >> I attempted to make a .rpm that installs a service/daemon but when I try to >> install it, it fails claiming the following dependencies cannot be met: >> >> libX11.so.6 is needed by myserver-1.0-1.x86_64 >> libXext.so.6 is needed by myserver-1.0-1.x86_64 >> libXi.so.6 is needed by myserver-1.0-1.x86_64 >> libXrender.so.1 is needed by myserver-1.0-1.x86_64 >> libXtst.so.6 is needed by myserver-1.0-1.x86_64 >> libasound.so.2 is needed by myserver-1.0-1.x86_64 >> >> Considering the app already runs fine on this same system, I'm a bit >> confused that it is complaining of missing dependencies. >> >> Scott > From swpalmer at gmail.com Wed Feb 3 03:27:48 2016 From: swpalmer at gmail.com (Scott Palmer) Date: Tue, 2 Feb 2016 22:27:48 -0500 Subject: javapackager In-Reply-To: <80465D9F-05F9-4F00-A51A-2598AB9FD0C9@oracle.com> References: <80465D9F-05F9-4F00-A51A-2598AB9FD0C9@oracle.com> Message-ID: Note that this is a RPM-based system, apt-get is not available, yum is. yum install libX11 ? Package libX11-1.6.0-2.1.el7.x86_64 already installed and latest version I get a similar message for the other dependencies. Examining the .rpm file I can see that the bundled runtime contains a lib/amd64 folder, so I?m pretty sure everything it did was 64-bit. If I run: yum install libX11.so.6 it wants to install the i686 architecture. So I went ahead an used yum to install the dependencies that way, but it failed on the last one (of course): $ sudo yum install libasound.so.2 Resolving Dependencies --> Running transaction check ---> Package alsa-lib.i686 0:1.0.28-2.el7 will be installed --> Finished Dependency Resolution Error: Multilib version problems found. ? ...you can also use --setopt=protected_multilib=false to remove this checking, however this is almost never the correct thing to do as something else is very likely to go wrong (often causing much more problems). Protected multilib versions: alsa-lib-1.0.28-2.el7.i686 != alsa-lib-1.0.27.2-3.el7.x86_64 It seems to be that javapackager has made a mistake and is claiming to depend on the 32-bit packages even though it really requires the 64-bit packages. Scott > On Feb 2, 2016, at 7:03 PM, Chris Bensen wrote: > > This list or the Deployment blog (https://blogs.oracle.com/talkingjavadeployment/) are the best places to get help with the javapackager. > > Is your app built with the 64-bit or 32-bit packager? I noticed ?x86_64? appended to the name. If it?s 32-bit you could try running: > > sudo apt-get install libx11-6:i386 > > Chris > > >> On Feb 2, 2016, at 1:49 PM, Scott Palmer wrote: >> >> What's the best place to go to get help with using the javapackager ? >> >> I've read the docs, but things aren't working smoothly and it would be >> helpful if there were some known working examples to base things on. I'm >> not finding any examples that use the -daemon or -BserviceHint=true >> options, for example. >> >> I attempted to make a .rpm that installs a service/daemon but when I try to >> install it, it fails claiming the following dependencies cannot be met: >> >> libX11.so.6 is needed by myserver-1.0-1.x86_64 >> libXext.so.6 is needed by myserver-1.0-1.x86_64 >> libXi.so.6 is needed by myserver-1.0-1.x86_64 >> libXrender.so.1 is needed by myserver-1.0-1.x86_64 >> libXtst.so.6 is needed by myserver-1.0-1.x86_64 >> libasound.so.2 is needed by myserver-1.0-1.x86_64 >> >> Considering the app already runs fine on this same system, I'm a bit >> confused that it is complaining of missing dependencies. >> >> Scott > From fastegal at swingempire.de Wed Feb 3 13:53:37 2016 From: fastegal at swingempire.de (fastegal at swingempire.de) Date: Wed, 03 Feb 2016 14:53:37 +0100 Subject: TableCellSkinBase: columnVisibility/Width should be protected In-Reply-To: <56AFF04E.6090200@oracle.com> References: <20160129141405.Horde.2jX1HnboguNBRPF2zbIrQg1@webmail.df.eu> <56AE6747.1070502@oracle.com> <20160201175858.Horde.FLhfKBYPCWZakHd595m0Og1@webmail.df.eu> <56AFF04E.6090200@oracle.com> Message-ID: <20160203145337.Horde.McOG9FEqrEarXLan3EV1Mg1@webmail.df.eu> Zitat von Jonathan Giles : > Probably it is best to just email me directly rather than email the > list multiple times per day. I'll bundle them up and review and make > plans on what should happen for each. Eventually we'll end up with > jira issues - which you're welcome to file directly - but I don't > mind keeping the overhead low until we have logical chunks of work > either. > good idea, though personally I'm having a hard time keeping track of mail content :-) I'll keep a loose list of thingies I find at my github wiki https://github.com/kleopatra/swingempire-fx/wiki/Skins9 and ping you by mail if new stuff turns up (that I think important enough for you). Cheers Jeanette From chris.bensen at oracle.com Wed Feb 3 16:40:14 2016 From: chris.bensen at oracle.com (Chris Bensen) Date: Wed, 3 Feb 2016 08:40:14 -0800 Subject: javapackager In-Reply-To: References: <80465D9F-05F9-4F00-A51A-2598AB9FD0C9@oracle.com> Message-ID: On Feb 2, 2016, at 7:27 PM, Scott Palmer wrote: > > Note that this is a RPM-based system, apt-get is not available, yum is. > > yum install libX11 What is the Linux system you are running? > ? > Package libX11-1.6.0-2.1.el7.x86_64 already installed and latest version > > I get a similar message for the other dependencies. > > Examining the .rpm file I can see that the bundled runtime contains a lib/amd64 folder, so I?m pretty sure everything it did was 64-bit. > > If I run: > > yum install libX11.so.6 > > it wants to install the i686 architecture. > > So I went ahead an used yum to install the dependencies that way, but it failed on the last one (of course): > $ sudo yum install libasound.so.2 > Resolving Dependencies > --> Running transaction check > ---> Package alsa-lib.i686 0:1.0.28-2.el7 will be installed > --> Finished Dependency Resolution > Error: Multilib version problems found. > ? > ...you can also use --setopt=protected_multilib=false to remove > this checking, however this is almost never the correct thing to > do as something else is very likely to go wrong (often causing > much more problems). > > Protected multilib versions: alsa-lib-1.0.28-2.el7.i686 != alsa-lib-1.0.27.2-3.el7.x86_64 > > > It seems to be that javapackager has made a mistake and is claiming to depend on the 32-bit packages even though it really requires the 64-bit packages. That?s what it?s sounding like to me. Looking at the code for the RPM bundler there isn?t anything I can find offhand that would suggest this. Bundling with 32/64-bit is triggered off the JDK used. Note that you have to bundle the same bitness JRE as the JDK. It should fail if it isn?t but that isn?t the case yet and that isn?t your problem. It appears the RPM generated is 32-bit. Unless you are bundling a 32-bit JRE and the RPM bundler keys off the native libraries used. Can you check the launcher executable? I think it?d be: $ file myserver-1.0-1.x86_64/app/myserver Can you file a minimum test case along with the Linux system used so we can prioritize with other bugs and find a solution? Chris > Scott > > >> On Feb 2, 2016, at 7:03 PM, Chris Bensen wrote: >> >> This list or the Deployment blog (https://blogs.oracle.com/talkingjavadeployment/) are the best places to get help with the javapackager. >> >> Is your app built with the 64-bit or 32-bit packager? I noticed ?x86_64? appended to the name. If it?s 32-bit you could try running: >> >> sudo apt-get install libx11-6:i386 >> >> Chris >> >> >>> On Feb 2, 2016, at 1:49 PM, Scott Palmer wrote: >>> >>> What's the best place to go to get help with using the javapackager ? >>> >>> I've read the docs, but things aren't working smoothly and it would be >>> helpful if there were some known working examples to base things on. I'm >>> not finding any examples that use the -daemon or -BserviceHint=true >>> options, for example. >>> >>> I attempted to make a .rpm that installs a service/daemon but when I try to >>> install it, it fails claiming the following dependencies cannot be met: >>> >>> libX11.so.6 is needed by myserver-1.0-1.x86_64 >>> libXext.so.6 is needed by myserver-1.0-1.x86_64 >>> libXi.so.6 is needed by myserver-1.0-1.x86_64 >>> libXrender.so.1 is needed by myserver-1.0-1.x86_64 >>> libXtst.so.6 is needed by myserver-1.0-1.x86_64 >>> libasound.so.2 is needed by myserver-1.0-1.x86_64 >>> >>> Considering the app already runs fine on this same system, I'm a bit >>> confused that it is complaining of missing dependencies. >>> >>> Scott >> > From swpalmer at gmail.com Wed Feb 3 21:08:07 2016 From: swpalmer at gmail.com (Scott Palmer) Date: Wed, 3 Feb 2016 16:08:07 -0500 Subject: javapackager In-Reply-To: References: <80465D9F-05F9-4F00-A51A-2598AB9FD0C9@oracle.com> Message-ID: <90F05EC0-3CBC-4A17-906C-0EC050B67130@gmail.com> > On Feb 3, 2016, at 11:40 AM, Chris Bensen wrote: > > On Feb 2, 2016, at 7:27 PM, Scott Palmer wrote: >> >> Note that this is a RPM-based system, apt-get is not available, yum is. >> >> yum install libX11 > > What is the Linux system you are running? It is a version of CentOS. (Created within my company with minor tweaks for branding purposes.) >> >> It seems to be that javapackager has made a mistake and is claiming to depend on the 32-bit packages even though it really requires the 64-bit packages. > > That?s what it?s sounding like to me. Looking at the code for the RPM bundler there isn?t anything I can find offhand that would suggest this. Bundling with 32/64-bit is triggered off the JDK used. Note that you have to bundle the same bitness JRE as the JDK. It should fail if it isn?t but that isn?t the case yet and that isn?t your problem. It appears the RPM generated is 32-bit. Unless you are bundling a 32-bit JRE and the RPM bundler keys off the native libraries used. Can you check the launcher executable? I think it?d be: > > $ file myserver-1.0-1.x86_64/app/myserver I had to extract the launcher from the .rpm. There is no version of it that is sitting around in the output folder. myserver: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.15, BuildID[sha1]=0x7e6522a86eca91b45cfb4dfa5defbddac0b1294a, not stripped So the 64-bit launcher is bundled. > > Can you file a minimum test case along with the Linux system used so we can prioritize with other bugs and find a solution? I?ll try to put something together. I?m still eager to find a workaround that I can implement with 8u72. Scott > > Chris > > >> Scott >> >> >>> On Feb 2, 2016, at 7:03 PM, Chris Bensen wrote: >>> >>> This list or the Deployment blog (https://blogs.oracle.com/talkingjavadeployment/) are the best places to get help with the javapackager. >>> >>> Is your app built with the 64-bit or 32-bit packager? I noticed ?x86_64? appended to the name. If it?s 32-bit you could try running: >>> >>> sudo apt-get install libx11-6:i386 >>> >>> Chris >>> >>> >>>> On Feb 2, 2016, at 1:49 PM, Scott Palmer wrote: >>>> >>>> What's the best place to go to get help with using the javapackager ? >>>> >>>> I've read the docs, but things aren't working smoothly and it would be >>>> helpful if there were some known working examples to base things on. I'm >>>> not finding any examples that use the -daemon or -BserviceHint=true >>>> options, for example. >>>> >>>> I attempted to make a .rpm that installs a service/daemon but when I try to >>>> install it, it fails claiming the following dependencies cannot be met: >>>> >>>> libX11.so.6 is needed by myserver-1.0-1.x86_64 >>>> libXext.so.6 is needed by myserver-1.0-1.x86_64 >>>> libXi.so.6 is needed by myserver-1.0-1.x86_64 >>>> libXrender.so.1 is needed by myserver-1.0-1.x86_64 >>>> libXtst.so.6 is needed by myserver-1.0-1.x86_64 >>>> libasound.so.2 is needed by myserver-1.0-1.x86_64 >>>> >>>> Considering the app already runs fine on this same system, I'm a bit >>>> confused that it is complaining of missing dependencies. >>>> >>>> Scott From ramonjsantiago at gmail.com Wed Feb 3 21:44:04 2016 From: ramonjsantiago at gmail.com (Ramon Santiago) Date: Wed, 3 Feb 2016 16:44:04 -0500 Subject: Is there a guide/tutorial on writing your own Effect? At the same level as say SepiaEffect Message-ID: Just to be clear, I know how to WritePixels to a buffer and manipulate them ad nauseum. But I want to write an Effect the way SepiaEffect extends Effect. BTW why is there even a SepiaEffect? it makes no sense at all -- rjs From james.graham at oracle.com Thu Feb 4 01:47:06 2016 From: james.graham at oracle.com (Jim Graham) Date: Wed, 3 Feb 2016 17:47:06 -0800 Subject: Is there a guide/tutorial on writing your own Effect? At the same level as say SepiaEffect In-Reply-To: References: Message-ID: <56B2AD9A.4040209@oracle.com> Hi Ramon, Currently the effects framework has no public API for extending it for new effects. WritableImage would be the only option of a public API that you could use at this point... ...jim On 2/3/2016 1:44 PM, Ramon Santiago wrote: > Just to be clear, I know how to WritePixels to a buffer and manipulate them > ad nauseum. > > But I want to write an Effect the way SepiaEffect extends Effect. > > BTW why is there even a SepiaEffect? it makes no sense at all > From bryanb at webbtide.com Thu Feb 4 07:53:25 2016 From: bryanb at webbtide.com (Bryan Buchanan) Date: Thu, 4 Feb 2016 17:53:25 +1000 Subject: Remove a line from GraphicsContext Message-ID: Don't know if this is correct mailing list. If I have gc.setStroke(Color.RED); gc.moveTo(x1, y1); gc.lineTo(x2, y2); gc.stroke(); and later I want to remove this line, how do I do that ? I don't want to clear the whole the Canvas (in fact gc.clearRect(0, 0, canvas.getWidth(), canvas.getHeight()); doesn't remove the line anyway). Also, if I wanted to implement a blinking cursor on a Canvas, is there a neat way to do that ? Thanks. From han.solo at mac.com Thu Feb 4 08:10:56 2016 From: han.solo at mac.com (Gerrit Grunwald) Date: Thu, 04 Feb 2016 09:10:56 +0100 Subject: Remove a line from GraphicsContext In-Reply-To: References: Message-ID: First it will be better using gc.strokeLine(x1, y1, x2, y2); To clear the line itself you could clear a rect around the line like gc.clearRect(x1 - 1, y1 - 1, x2 + 1, y2 + 1); Take a look at this Gist... https://gist.github.com/HanSolo/f25412352ff7ec5b9b53 > Am 04.02.2016 um 08:53 schrieb Bryan Buchanan : > > Don't know if this is correct mailing list. > > If I have > > gc.setStroke(Color.RED); > gc.moveTo(x1, y1); > gc.lineTo(x2, y2); > gc.stroke(); > > and later I want to remove this line, how do I do that ? > > I don't want to clear the whole the Canvas (in fact > > gc.clearRect(0, 0, canvas.getWidth(), canvas.getHeight()); > > doesn't remove the line anyway). > > Also, if I wanted to implement a blinking cursor on a Canvas, is there a > neat way to do that ? > > Thanks. From bryanb at webbtide.com Thu Feb 4 08:31:39 2016 From: bryanb at webbtide.com (Bryan Buchanan) Date: Thu, 4 Feb 2016 18:31:39 +1000 Subject: Remove a line from GraphicsContext In-Reply-To: References: Message-ID: You're an absolute champion ! Thanks very much. On 4 February 2016 at 18:10, Gerrit Grunwald wrote: > First it will be better using > > gc.strokeLine(x1, y1, x2, y2); > > To clear the line itself you could clear a rect around the line like > > gc.clearRect(x1 - 1, y1 - 1, x2 + 1, y2 + 1); > > Take a look at this Gist... > https://gist.github.com/HanSolo/f25412352ff7ec5b9b53 > > > Am 04.02.2016 um 08:53 schrieb Bryan Buchanan : > > Don't know if this is correct mailing list. > > If I have > > gc.setStroke(Color.RED); > gc.moveTo(x1, y1); > gc.lineTo(x2, y2); > gc.stroke(); > > and later I want to remove this line, how do I do that ? > > I don't want to clear the whole the Canvas (in fact > > gc.clearRect(0, 0, canvas.getWidth(), canvas.getHeight()); > > doesn't remove the line anyway). > > Also, if I wanted to implement a blinking cursor on a Canvas, is there a > neat way to do that ? > > Thanks. > > > From swpalmer at gmail.com Thu Feb 4 15:12:47 2016 From: swpalmer at gmail.com (Scott Palmer) Date: Thu, 4 Feb 2016 10:12:47 -0500 Subject: javapackager In-Reply-To: <90F05EC0-3CBC-4A17-906C-0EC050B67130@gmail.com> References: <80465D9F-05F9-4F00-A51A-2598AB9FD0C9@oracle.com> <90F05EC0-3CBC-4A17-906C-0EC050B67130@gmail.com> Message-ID: I noticed that the JDK on my Linux VM was 8u40, I updated to 8u72 and then got the following: Bundler RPM Bundle skipped because of a configuration problem: Specified license file is missing. Advice to fix: Make sure that "EULA.rtf" references a file in the app resources, and that it is relative file reference. I wasn't able to do anything to convince it that the license file was there. I just omitted it for now. Updating to 8u72 did not solve my .rpm dependency issues. Scott On Wed, Feb 3, 2016 at 4:08 PM, Scott Palmer wrote: > > > On Feb 3, 2016, at 11:40 AM, Chris Bensen > wrote: > > > > On Feb 2, 2016, at 7:27 PM, Scott Palmer wrote: > >> > >> Note that this is a RPM-based system, apt-get is not available, yum is. > >> > >> yum install libX11 > > > > What is the Linux system you are running? > > It is a version of CentOS. (Created within my company with minor tweaks > for branding purposes.) > > > >> > >> It seems to be that javapackager has made a mistake and is claiming to > depend on the 32-bit packages even though it really requires the 64-bit > packages. > > > > That?s what it?s sounding like to me. Looking at the code for the RPM > bundler there isn?t anything I can find offhand that would suggest this. > Bundling with 32/64-bit is triggered off the JDK used. Note that you have > to bundle the same bitness JRE as the JDK. It should fail if it isn?t but > that isn?t the case yet and that isn?t your problem. It appears the RPM > generated is 32-bit. Unless you are bundling a 32-bit JRE and the RPM > bundler keys off the native libraries used. Can you check the launcher > executable? I think it?d be: > > > > $ file myserver-1.0-1.x86_64/app/myserver > > I had to extract the launcher from the .rpm. There is no version of it > that is sitting around in the output folder. > > myserver: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically > linked (uses shared libs), for GNU/Linux 2.6.15, > BuildID[sha1]=0x7e6522a86eca91b45cfb4dfa5defbddac0b1294a, not stripped > > > So the 64-bit launcher is bundled. > > > > > > Can you file a minimum test case along with the Linux system used so we > can prioritize with other bugs and find a solution? > > I?ll try to put something together. I?m still eager to find a workaround > that I can implement with 8u72. > > > Scott > > > > > > Chris > > > > > >> Scott > >> > >> > >>> On Feb 2, 2016, at 7:03 PM, Chris Bensen > wrote: > >>> > >>> This list or the Deployment blog ( > https://blogs.oracle.com/talkingjavadeployment/) are the best places to > get help with the javapackager. > >>> > >>> Is your app built with the 64-bit or 32-bit packager? I noticed > ?x86_64? appended to the name. If it?s 32-bit you could try running: > >>> > >>> sudo apt-get install libx11-6:i386 > >>> > >>> Chris > >>> > >>> > >>>> On Feb 2, 2016, at 1:49 PM, Scott Palmer wrote: > >>>> > >>>> What's the best place to go to get help with using the javapackager ? > >>>> > >>>> I've read the docs, but things aren't working smoothly and it would be > >>>> helpful if there were some known working examples to base things on. > I'm > >>>> not finding any examples that use the -daemon or -BserviceHint=true > >>>> options, for example. > >>>> > >>>> I attempted to make a .rpm that installs a service/daemon but when I > try to > >>>> install it, it fails claiming the following dependencies cannot be > met: > >>>> > >>>> libX11.so.6 is needed by myserver-1.0-1.x86_64 > >>>> libXext.so.6 is needed by myserver-1.0-1.x86_64 > >>>> libXi.so.6 is needed by myserver-1.0-1.x86_64 > >>>> libXrender.so.1 is needed by myserver-1.0-1.x86_64 > >>>> libXtst.so.6 is needed by myserver-1.0-1.x86_64 > >>>> libasound.so.2 is needed by myserver-1.0-1.x86_64 > >>>> > >>>> Considering the app already runs fine on this same system, I'm a bit > >>>> confused that it is complaining of missing dependencies. > >>>> > >>>> Scott > > From leif.samuelsson at oracle.com Thu Feb 4 16:27:12 2016 From: leif.samuelsson at oracle.com (Leif Samuelsson) Date: Thu, 4 Feb 2016 17:27:12 +0100 Subject: [9] Request for review: 8143158 [Text, TextFlow] Make public API from internal "impl" APIs Message-ID: <56B37BE0.9040009@oracle.com> Hi Kevin, Please review the implementation of the new API. https://bugs.openjdk.java.net/browse/JDK-8143158 http://cr.openjdk.java.net/~leifs/8143158/webrev.01/ Thanks, Leif From chris.bensen at oracle.com Thu Feb 4 17:12:46 2016 From: chris.bensen at oracle.com (Chris Bensen) Date: Thu, 4 Feb 2016 09:12:46 -0800 Subject: javapackager In-Reply-To: References: <80465D9F-05F9-4F00-A51A-2598AB9FD0C9@oracle.com> <90F05EC0-3CBC-4A17-906C-0EC050B67130@gmail.com> Message-ID: <4B65AC3E-B5EC-46C4-BC77-2F0A04DB360D@oracle.com> There weren?t any noticeable changes for Linux. Besides maybe this one, which if you could file a bug with steps to reproduce that?d be great. Chris > On Feb 4, 2016, at 7:12 AM, Scott Palmer wrote: > > I noticed that the JDK on my Linux VM was 8u40, I updated to 8u72 and then got the following: > > Bundler RPM Bundle skipped because of a configuration problem: Specified license file is missing. > Advice to fix: Make sure that "EULA.rtf" references a file in the app resources, and that it is relative file reference. > > I wasn't able to do anything to convince it that the license file was there. I just omitted it for now. > > Updating to 8u72 did not solve my .rpm dependency issues. > > Scott > > On Wed, Feb 3, 2016 at 4:08 PM, Scott Palmer > wrote: > > > On Feb 3, 2016, at 11:40 AM, Chris Bensen > wrote: > > > > On Feb 2, 2016, at 7:27 PM, Scott Palmer > wrote: > >> > >> Note that this is a RPM-based system, apt-get is not available, yum is. > >> > >> yum install libX11 > > > > What is the Linux system you are running? > > It is a version of CentOS. (Created within my company with minor tweaks for branding purposes.) > > > >> > >> It seems to be that javapackager has made a mistake and is claiming to depend on the 32-bit packages even though it really requires the 64-bit packages. > > > > That?s what it?s sounding like to me. Looking at the code for the RPM bundler there isn?t anything I can find offhand that would suggest this. Bundling with 32/64-bit is triggered off the JDK used. Note that you have to bundle the same bitness JRE as the JDK. It should fail if it isn?t but that isn?t the case yet and that isn?t your problem. It appears the RPM generated is 32-bit. Unless you are bundling a 32-bit JRE and the RPM bundler keys off the native libraries used. Can you check the launcher executable? I think it?d be: > > > > $ file myserver-1.0-1.x86_64/app/myserver > > I had to extract the launcher from the .rpm. There is no version of it that is sitting around in the output folder. > > myserver: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.15, BuildID[sha1]=0x7e6522a86eca91b45cfb4dfa5defbddac0b1294a, not stripped > > > So the 64-bit launcher is bundled. > > > > > > Can you file a minimum test case along with the Linux system used so we can prioritize with other bugs and find a solution? > > I?ll try to put something together. I?m still eager to find a workaround that I can implement with 8u72. > > > Scott > > > > > > Chris > > > > > >> Scott > >> > >> > >>> On Feb 2, 2016, at 7:03 PM, Chris Bensen > wrote: > >>> > >>> This list or the Deployment blog (https://blogs.oracle.com/talkingjavadeployment/ ) are the best places to get help with the javapackager. > >>> > >>> Is your app built with the 64-bit or 32-bit packager? I noticed ?x86_64? appended to the name. If it?s 32-bit you could try running: > >>> > >>> sudo apt-get install libx11-6:i386 > >>> > >>> Chris > >>> > >>> > >>>> On Feb 2, 2016, at 1:49 PM, Scott Palmer > wrote: > >>>> > >>>> What's the best place to go to get help with using the javapackager ? > >>>> > >>>> I've read the docs, but things aren't working smoothly and it would be > >>>> helpful if there were some known working examples to base things on. I'm > >>>> not finding any examples that use the -daemon or -BserviceHint=true > >>>> options, for example. > >>>> > >>>> I attempted to make a .rpm that installs a service/daemon but when I try to > >>>> install it, it fails claiming the following dependencies cannot be met: > >>>> > >>>> libX11.so.6 is needed by myserver-1.0-1.x86_64 > >>>> libXext.so.6 is needed by myserver-1.0-1.x86_64 > >>>> libXi.so.6 is needed by myserver-1.0-1.x86_64 > >>>> libXrender.so.1 is needed by myserver-1.0-1.x86_64 > >>>> libXtst.so.6 is needed by myserver-1.0-1.x86_64 > >>>> libasound.so.2 is needed by myserver-1.0-1.x86_64 > >>>> > >>>> Considering the app already runs fine on this same system, I'm a bit > >>>> confused that it is complaining of missing dependencies. > >>>> > >>>> Scott > > From elric.mn at gmail.com Thu Feb 4 22:49:13 2016 From: elric.mn at gmail.com (Elric Morgenstern) Date: Thu, 4 Feb 2016 23:49:13 +0100 Subject: Canvas Clip performance Message-ID: Hi guys, I've noticed that clipping performance (Canvas GraphicsContext) is extremely bad on an Intel HD graphics chip. One rectangular clip is fine, anything beyond that, or a spherical clip shape, will bring the framerate to its knees. I notice no performance difference on my GeForce system, but on the integrated chip my application is basically insufferable. The same thing performed with Java2D experiences no performance issues on neither system. Any ideas? From philip.race at oracle.com Thu Feb 4 22:52:39 2016 From: philip.race at oracle.com (Philip Race) Date: Thu, 04 Feb 2016 14:52:39 -0800 Subject: Canvas Clip performance In-Reply-To: References: Message-ID: <56B3D637.5040209@oracle.com> Java 2D does not (generally) enable D3D on Intel. We tried for JDK 8 but there were problems and it was disabled again in 8u40 I think. JDK 9 EA builds (currently) still have it enabled to help get some testing so if you are running an 8ux release you might want to switch to 9 to get a fairer comparison. -phil. On 2/4/16, 2:49 PM, Elric Morgenstern wrote: > Hi guys, > > I've noticed that clipping performance (Canvas GraphicsContext) is > extremely bad on an Intel HD graphics chip. One rectangular clip is fine, > anything beyond that, or a spherical clip shape, will bring the framerate > to its knees. > > I notice no performance difference on my GeForce system, but on the > integrated chip my application is basically insufferable. > > The same thing performed with Java2D experiences no performance issues on > neither system. > > Any ideas? From elric.mn at gmail.com Thu Feb 4 22:59:00 2016 From: elric.mn at gmail.com (Elric Morgenstern) Date: Thu, 4 Feb 2016 23:59:00 +0100 Subject: Canvas Clip performance In-Reply-To: <56B3D637.5040209@oracle.com> References: <56B3D637.5040209@oracle.com> Message-ID: I see. Interesting. Isn't there a switch to toggle it on JDK8? Assuming you are talking about JavaFX, right? Because you were referring to Java2D in your reply. On Thu, Feb 4, 2016 at 11:52 PM, Philip Race wrote: > Java 2D does not (generally) enable D3D on Intel. > We tried for JDK 8 but there were problems and it was disabled again in > 8u40 I think. > JDK 9 EA builds (currently) still have it enabled to help get some testing > so > if you are running an 8ux release you might want to switch to 9 to get a > fairer comparison. > > -phil. > > > > On 2/4/16, 2:49 PM, Elric Morgenstern wrote: > >> Hi guys, >> >> I've noticed that clipping performance (Canvas GraphicsContext) is >> extremely bad on an Intel HD graphics chip. One rectangular clip is fine, >> anything beyond that, or a spherical clip shape, will bring the framerate >> to its knees. >> >> I notice no performance difference on my GeForce system, but on the >> integrated chip my application is basically insufferable. >> >> The same thing performed with Java2D experiences no performance issues on >> neither system. >> >> Any ideas? >> > From philip.race at oracle.com Fri Feb 5 00:01:46 2016 From: philip.race at oracle.com (Philip Race) Date: Thu, 04 Feb 2016 16:01:46 -0800 Subject: Canvas Clip performance In-Reply-To: References: <56B3D637.5040209@oracle.com> Message-ID: <56B3E66A.9090603@oracle.com> On 2/4/16, 2:59 PM, Elric Morgenstern wrote: > I see. Interesting. Isn't there a switch to toggle it on JDK8? There is no switch that can enable it if it is disabled by 'default'. > > Assuming you are talking about JavaFX, right? Because you were referring to > Java2D in your reply. No I am talking about 2D. What I meant was that maybe the performance issue is inherent in the card and the only reason it looks OK with Java2D on Intel is that we aren't using anything much at all of the Intel chip and are doing the work on the cpu instead. -phil. > > On Thu, Feb 4, 2016 at 11:52 PM, Philip Race wrote: > >> Java 2D does not (generally) enable D3D on Intel. >> We tried for JDK 8 but there were problems and it was disabled again in >> 8u40 I think. >> JDK 9 EA builds (currently) still have it enabled to help get some testing >> so >> if you are running an 8ux release you might want to switch to 9 to get a >> fairer comparison. >> >> -phil. >> >> >> >> On 2/4/16, 2:49 PM, Elric Morgenstern wrote: >> >>> Hi guys, >>> >>> I've noticed that clipping performance (Canvas GraphicsContext) is >>> extremely bad on an Intel HD graphics chip. One rectangular clip is fine, >>> anything beyond that, or a spherical clip shape, will bring the framerate >>> to its knees. >>> >>> I notice no performance difference on my GeForce system, but on the >>> integrated chip my application is basically insufferable. >>> >>> The same thing performed with Java2D experiences no performance issues on >>> neither system. >>> >>> Any ideas? >>> From chris.bensen at oracle.com Fri Feb 5 03:42:51 2016 From: chris.bensen at oracle.com (Chris Bensen) Date: Thu, 4 Feb 2016 19:42:51 -0800 Subject: javapackager In-Reply-To: <90F05EC0-3CBC-4A17-906C-0EC050B67130@gmail.com> References: <80465D9F-05F9-4F00-A51A-2598AB9FD0C9@oracle.com> <90F05EC0-3CBC-4A17-906C-0EC050B67130@gmail.com> Message-ID: > On Feb 3, 2016, at 1:08 PM, Scott Palmer wrote: > > >> On Feb 3, 2016, at 11:40 AM, Chris Bensen wrote: >> >> On Feb 2, 2016, at 7:27 PM, Scott Palmer wrote: >>> >>> Note that this is a RPM-based system, apt-get is not available, yum is. >>> >>> yum install libX11 >> >> What is the Linux system you are running? > > It is a version of CentOS. (Created within my company with minor tweaks for branding purposes.) When submitting a bug, make sure the test case works on Oracle Linux or Ubuntu since those are the only ?supported? version of Linux. > > >>> >>> It seems to be that javapackager has made a mistake and is claiming to depend on the 32-bit packages even though it really requires the 64-bit packages. >> >> That?s what it?s sounding like to me. Looking at the code for the RPM bundler there isn?t anything I can find offhand that would suggest this. Bundling with 32/64-bit is triggered off the JDK used. Note that you have to bundle the same bitness JRE as the JDK. It should fail if it isn?t but that isn?t the case yet and that isn?t your problem. It appears the RPM generated is 32-bit. Unless you are bundling a 32-bit JRE and the RPM bundler keys off the native libraries used. Can you check the launcher executable? I think it?d be: >> >> $ file myserver-1.0-1.x86_64/app/myserver > > I had to extract the launcher from the .rpm. There is no version of it that is sitting around in the output folder. > > myserver: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.15, BuildID[sha1]=0x7e6522a86eca91b45cfb4dfa5defbddac0b1294a, not stripped > > > So the 64-bit launcher is bundled. > > >> >> Can you file a minimum test case along with the Linux system used so we can prioritize with other bugs and find a solution? > > I?ll try to put something together. I?m still eager to find a workaround that I can implement with 8u72. > > > Scott > > >> >> Chris >> >> >>> Scott >>> >>> >>>> On Feb 2, 2016, at 7:03 PM, Chris Bensen wrote: >>>> >>>> This list or the Deployment blog (https://blogs.oracle.com/talkingjavadeployment/) are the best places to get help with the javapackager. >>>> >>>> Is your app built with the 64-bit or 32-bit packager? I noticed ?x86_64? appended to the name. If it?s 32-bit you could try running: >>>> >>>> sudo apt-get install libx11-6:i386 >>>> >>>> Chris >>>> >>>> >>>>> On Feb 2, 2016, at 1:49 PM, Scott Palmer wrote: >>>>> >>>>> What's the best place to go to get help with using the javapackager ? >>>>> >>>>> I've read the docs, but things aren't working smoothly and it would be >>>>> helpful if there were some known working examples to base things on. I'm >>>>> not finding any examples that use the -daemon or -BserviceHint=true >>>>> options, for example. >>>>> >>>>> I attempted to make a .rpm that installs a service/daemon but when I try to >>>>> install it, it fails claiming the following dependencies cannot be met: >>>>> >>>>> libX11.so.6 is needed by myserver-1.0-1.x86_64 >>>>> libXext.so.6 is needed by myserver-1.0-1.x86_64 >>>>> libXi.so.6 is needed by myserver-1.0-1.x86_64 >>>>> libXrender.so.1 is needed by myserver-1.0-1.x86_64 >>>>> libXtst.so.6 is needed by myserver-1.0-1.x86_64 >>>>> libasound.so.2 is needed by myserver-1.0-1.x86_64 >>>>> >>>>> Considering the app already runs fine on this same system, I'm a bit >>>>> confused that it is complaining of missing dependencies. >>>>> >>>>> Scott > From danielhilst at gmail.com Fri Feb 5 13:07:46 2016 From: danielhilst at gmail.com (Daniel.) Date: Fri, 5 Feb 2016 11:07:46 -0200 Subject: VNC alternative for JavaFX running directly on framebuffer. In-Reply-To: References: Message-ID: Hi everybody, I've succesfully build and using framebuffer-vncserver. The only drawback is that it hasn't input support, but seeing the screen is already enough to me, here is it: https://github.com/ponty/framebuffer-vncserver If there is anybody using Yocto, you may find usefull this two recipes: https://gist.github.com/gkos/9ed87cad62d72c599761 Cheers, 2016-01-20 16:28 GMT-02:00 Daniel. : > I've also tried running with these: > > -Dglass.platform=Monocle -Dmonocle.platform=VNC -Dprism.order=sw > > I can see the 5901 port in listening, can connect to it but got a > blackscreen. At the console I got this flood BufferOverflowException:, > any idea? > > > Here is the full line and first messages: > java -Dglass.platform=Monocle -Dmonocle.platform=VNC -Dprism.order=sw > -Dprism.verbose=true -Xms256m -Xmx256m -Duser.timezone=GMT > br.ind.csi.andon.ui.MainApp andon.ini > Prism pipeline init order: sw > Using native-based Pisces rasterizer > Using dirty region optimizations > Using system sized mask for primitives > Not forcing power of 2 sizes for textures > Using hardware CLAMP_TO_ZERO mode > Opting in for HiDPI pixel scaling > *** Fallback to Prism SW pipeline > Prism pipeline name = com.sun.prism.sw.SWPipeline > (X) Got class = class com.sun.prism.sw.SWPipeline > Initialized prism pipeline: com.sun.prism.sw.SWPipeline > vsync: true vpipe: false > Loading Prism common native library ... > succeeded. > Exception in thread "JavaFX Application Thread" > java.nio.BufferOverflowException > at java.nio.IntBuffer.put(IntBuffer.java:769) > at > com.sun.glass.ui.monocle.Framebuffer.composePixels(Framebuffer.java:168) > at > com.sun.glass.ui.monocle.HeadlessScreen.uploadPixels(HeadlessScreen.java:118) > at > com.sun.glass.ui.monocle.MonocleView._uploadPixels(MonocleView.java:95) > at com.sun.glass.ui.View.uploadPixels(View.java:771) > at > com.sun.prism.PresentableState.uploadPixels(PresentableState.java:295) > at com.sun.javafx.tk.quantum.SceneState.access$001(SceneState.java:40) > at > com.sun.javafx.tk.quantum.SceneState.lambda$uploadPixels$307(SceneState.java:123) > at > com.sun.glass.ui.monocle.RunnableProcessor.runLoop(RunnableProcessor.java:92) > at > com.sun.glass.ui.monocle.RunnableProcessor.run(RunnableProcessor.java:51) > at java.lang.Thread.run(Thread.java:745) > java.nio.BufferOverflowException > at java.nio.DirectIntBufferU.put(DirectIntBufferU.java:363) > at > com.sun.javafx.tk.quantum.UploadingPainter.run(UploadingPainter.java:153) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > .... > > > > Best regards, > > 2016-01-20 14:43 GMT-02:00 Daniel. : > > Hi Dell, thanks for the reply > > > > I have both versions of libegl.so compiled and installed, the > > framebuffer variants are at /opt/VIVANTE-fb. When I run it with x11 > > variants and run x11vnc I can connect to the vnc server, can see the > > application screen, but the inputs doesn't work. I've tested with: > > > > SERVER: x11vnc: 0.9.13 lastmod: 2011-08-10 > > CLIENTS: Vinagre(3.19.2 @ linux) and UltraVNC(1.0.2 @ windows) > > > > I'll try to monitor X input events to see what is happening, > > > > Best regards, > > > > 2016-01-20 3:22 GMT-02:00 Dell Green : > >> > >> > >> I am pretty sure that when i built an operating system for mx6 using > yocto project I had the option for it to spit out x11 versions of libegl.so > libs instead of framebuffer, although I was only interested in framebuffer > option. > >> > >> Dell Green > >> R&D Software Manager > >> t: (+44)203 668 9870 > >> > >> > >> > >> > >> 206 Great Portland Street > >> London W1W 5QJ > >> > >> This email and any files transmitted with it are confidential and > intended solely for the use of the individual or entity to whom they are > addressed. If you are not the intended recipient or the person responsible > for delivering the email to the intended recipient, be advised that you > have received this email in error and that any use, dissemination, > forwarding, printing, or copying of this email is strictly prohibited. Any > views or opinions presented are solely those of the author and do not > necessarily represent those of Ideaworks Limited. Ideaworks (London) > Limited, 206 Great Portland Street, London, W1W 5QJ. Company Registration > No. 3943726 > > > > > > > > -- > > "Do or do not. There is no try" > > Yoda Master > > > > -- > "Do or do not. There is no try" > Yoda Master > -- *"Do or do not. There is no try"* *Yoda Master* From elric.mn at gmail.com Fri Feb 5 13:22:42 2016 From: elric.mn at gmail.com (Elric Morgenstern) Date: Fri, 5 Feb 2016 14:22:42 +0100 Subject: Canvas Clip performance In-Reply-To: <56B3E66A.9090603@oracle.com> References: <56B3D637.5040209@oracle.com> <56B3E66A.9090603@oracle.com> Message-ID: Ok. Maybe the problems I am experiencing now with JavaFX are the reason why D3D is not enabled for J2D? I think Intel Graphics are rather widespread among laptops, so I'm a bit surprised at the huge performance drop (from solid 60 FPS to 8 once I use a spherical clip shape). I'd think Intel Graphics hardware form part of the test set. I'm using a fairly common laptop (especially around business circles) Dell Latitude E6410. Any chance of this being investigated or do you think I will have to settle with a workaround? On Fri, Feb 5, 2016 at 1:01 AM, Philip Race wrote: > > > On 2/4/16, 2:59 PM, Elric Morgenstern wrote: > >> I see. Interesting. Isn't there a switch to toggle it on JDK8? >> > > There is no switch that can enable it if it is disabled by 'default'. > >> >> Assuming you are talking about JavaFX, right? Because you were referring >> to >> Java2D in your reply. >> > > No I am talking about 2D. What I meant was that maybe the performance issue > is inherent in the card and the only reason it looks OK with Java2D on > Intel is > that we aren't using anything much at all of the Intel chip and are doing > the work > on the cpu instead. > > -phil. > > > >> On Thu, Feb 4, 2016 at 11:52 PM, Philip Race >> wrote: >> >> Java 2D does not (generally) enable D3D on Intel. >>> We tried for JDK 8 but there were problems and it was disabled again in >>> 8u40 I think. >>> JDK 9 EA builds (currently) still have it enabled to help get some >>> testing >>> so >>> if you are running an 8ux release you might want to switch to 9 to get a >>> fairer comparison. >>> >>> -phil. >>> >>> >>> >>> On 2/4/16, 2:49 PM, Elric Morgenstern wrote: >>> >>> Hi guys, >>>> >>>> I've noticed that clipping performance (Canvas GraphicsContext) is >>>> extremely bad on an Intel HD graphics chip. One rectangular clip is >>>> fine, >>>> anything beyond that, or a spherical clip shape, will bring the >>>> framerate >>>> to its knees. >>>> >>>> I notice no performance difference on my GeForce system, but on the >>>> integrated chip my application is basically insufferable. >>>> >>>> The same thing performed with Java2D experiences no performance issues >>>> on >>>> neither system. >>>> >>>> Any ideas? >>>> >>>> From vadim.pakhnushev at oracle.com Fri Feb 5 14:30:02 2016 From: vadim.pakhnushev at oracle.com (Vadim Pakhnushev) Date: Fri, 5 Feb 2016 17:30:02 +0300 Subject: In(Sanity) Testing Mondays Message-ID: <56B4B1EA.8080706@oracle.com> Reminder, Monday is our weekly sanity testing. You can find your testing assignment at: https://wiki.openjdk.java.net/display/OpenJFX/Sanity+Testing Also please remember that the repo will be locked from 1am PST until 1pm PST. Happy testing! Thanks, Vadim From vadim.pakhnushev at oracle.com Fri Feb 5 15:06:05 2016 From: vadim.pakhnushev at oracle.com (Vadim Pakhnushev) Date: Fri, 5 Feb 2016 18:06:05 +0300 Subject: =?UTF-8?Q?[9]_Review_request_for_8088078:_[Chart]_=e2=80=9cInsert_S?= =?UTF-8?Q?eries=e2=80=9d_can_not_work_as_expected_after_we_remove_all_data?= Message-ID: <56B4BA5D.6040900@oracle.com> Morris, Could you please take a look at the fix: https://bugs.openjdk.java.net/browse/JDK-8088078 http://cr.openjdk.java.net/~vadim/8088078/webrev.00/ Thanks, Vadim From kevin.rushforth at oracle.com Fri Feb 5 15:34:20 2016 From: kevin.rushforth at oracle.com (Kevin Rushforth) Date: Fri, 05 Feb 2016 07:34:20 -0800 Subject: Canvas Clip performance In-Reply-To: References: <56B3D637.5040209@oracle.com> <56B3E66A.9090603@oracle.com> Message-ID: <56B4C0FC.9090303@oracle.com> Please file a bug. It might be possible for us to find a workaround, although it might also be possible that this is just an unfortunate limitation of Intel HD. -- Kevin Elric Morgenstern wrote: > Ok. Maybe the problems I am experiencing now with JavaFX are the reason why > D3D is not enabled for J2D? > > I think Intel Graphics are rather widespread among laptops, so I'm a bit > surprised at the huge performance drop (from solid 60 FPS to 8 once I use a > spherical clip shape). I'd think Intel Graphics hardware form part of the > test set. I'm using a fairly common laptop (especially around business > circles) Dell Latitude E6410. > > Any chance of this being investigated or do you think I will have to settle > with a workaround? > > > On Fri, Feb 5, 2016 at 1:01 AM, Philip Race wrote: > > >> On 2/4/16, 2:59 PM, Elric Morgenstern wrote: >> >> >>> I see. Interesting. Isn't there a switch to toggle it on JDK8? >>> >>> >> There is no switch that can enable it if it is disabled by 'default'. >> >> >>> Assuming you are talking about JavaFX, right? Because you were referring >>> to >>> Java2D in your reply. >>> >>> >> No I am talking about 2D. What I meant was that maybe the performance issue >> is inherent in the card and the only reason it looks OK with Java2D on >> Intel is >> that we aren't using anything much at all of the Intel chip and are doing >> the work >> on the cpu instead. >> >> -phil. >> >> >> >> >>> On Thu, Feb 4, 2016 at 11:52 PM, Philip Race >>> wrote: >>> >>> Java 2D does not (generally) enable D3D on Intel. >>> >>>> We tried for JDK 8 but there were problems and it was disabled again in >>>> 8u40 I think. >>>> JDK 9 EA builds (currently) still have it enabled to help get some >>>> testing >>>> so >>>> if you are running an 8ux release you might want to switch to 9 to get a >>>> fairer comparison. >>>> >>>> -phil. >>>> >>>> >>>> >>>> On 2/4/16, 2:49 PM, Elric Morgenstern wrote: >>>> >>>> Hi guys, >>>> >>>>> I've noticed that clipping performance (Canvas GraphicsContext) is >>>>> extremely bad on an Intel HD graphics chip. One rectangular clip is >>>>> fine, >>>>> anything beyond that, or a spherical clip shape, will bring the >>>>> framerate >>>>> to its knees. >>>>> >>>>> I notice no performance difference on my GeForce system, but on the >>>>> integrated chip my application is basically insufferable. >>>>> >>>>> The same thing performed with Java2D experiences no performance issues >>>>> on >>>>> neither system. >>>>> >>>>> Any ideas? >>>>> >>>>> >>>>> From vadim.pakhnushev at oracle.com Fri Feb 5 16:25:24 2016 From: vadim.pakhnushev at oracle.com (Vadim Pakhnushev) Date: Fri, 5 Feb 2016 19:25:24 +0300 Subject: [9] Review request for 8139850: CategoryAxis rotates improperly as yAxis Message-ID: <56B4CCF4.4050704@oracle.com> Jonathan, Could you please take a look at the fix: https://bugs.openjdk.java.net/browse/JDK-8139850 http://cr.openjdk.java.net/~vadim/8139850/webrev.00/ Thanks, Vadim From chien.yang at oracle.com Fri Feb 5 17:38:18 2016 From: chien.yang at oracle.com (Chien Yang) Date: Fri, 05 Feb 2016 09:38:18 -0800 Subject: Canvas Clip performance In-Reply-To: <56B4C0FC.9090303@oracle.com> References: <56B3D637.5040209@oracle.com> <56B3E66A.9090603@oracle.com> <56B4C0FC.9090303@oracle.com> Message-ID: <56B4DE0A.80105@oracle.com> It will be great if you can include in your bug report the following 2 piece of information: 1) Run your program with -Dprism.verbose=true. This will give us the graphics hardware information of your system. 2) Run your program with -Dprism.order=sw. This will force JavaFX to use its software pipe instead of hardware graphics acceleration. It will be good to know whether the poor performance is due to use of d3d pipe. - Chien On 2/5/16, 7:34 AM, Kevin Rushforth wrote: > Please file a bug. It might be possible for us to find a workaround, > although it might also be possible that this is just an unfortunate > limitation of Intel HD. > > -- Kevin > > > Elric Morgenstern wrote: >> Ok. Maybe the problems I am experiencing now with JavaFX are the >> reason why >> D3D is not enabled for J2D? >> >> I think Intel Graphics are rather widespread among laptops, so I'm a bit >> surprised at the huge performance drop (from solid 60 FPS to 8 once I >> use a >> spherical clip shape). I'd think Intel Graphics hardware form part of >> the >> test set. I'm using a fairly common laptop (especially around business >> circles) Dell Latitude E6410. >> >> Any chance of this being investigated or do you think I will have to >> settle >> with a workaround? >> >> >> On Fri, Feb 5, 2016 at 1:01 AM, Philip Race >> wrote: >> >>> On 2/4/16, 2:59 PM, Elric Morgenstern wrote: >>> >>>> I see. Interesting. Isn't there a switch to toggle it on JDK8? >>>> >>> There is no switch that can enable it if it is disabled by 'default'. >>> >>>> Assuming you are talking about JavaFX, right? Because you were >>>> referring >>>> to >>>> Java2D in your reply. >>>> >>> No I am talking about 2D. What I meant was that maybe the >>> performance issue >>> is inherent in the card and the only reason it looks OK with Java2D on >>> Intel is >>> that we aren't using anything much at all of the Intel chip and are >>> doing >>> the work >>> on the cpu instead. >>> >>> -phil. >>> >>> >>> >>>> On Thu, Feb 4, 2016 at 11:52 PM, Philip Race >>>> wrote: >>>> >>>> Java 2D does not (generally) enable D3D on Intel. >>>>> We tried for JDK 8 but there were problems and it was disabled >>>>> again in >>>>> 8u40 I think. >>>>> JDK 9 EA builds (currently) still have it enabled to help get some >>>>> testing >>>>> so >>>>> if you are running an 8ux release you might want to switch to 9 to >>>>> get a >>>>> fairer comparison. >>>>> >>>>> -phil. >>>>> >>>>> >>>>> >>>>> On 2/4/16, 2:49 PM, Elric Morgenstern wrote: >>>>> >>>>> Hi guys, >>>>>> I've noticed that clipping performance (Canvas GraphicsContext) is >>>>>> extremely bad on an Intel HD graphics chip. One rectangular clip is >>>>>> fine, >>>>>> anything beyond that, or a spherical clip shape, will bring the >>>>>> framerate >>>>>> to its knees. >>>>>> >>>>>> I notice no performance difference on my GeForce system, but on the >>>>>> integrated chip my application is basically insufferable. >>>>>> >>>>>> The same thing performed with Java2D experiences no performance >>>>>> issues >>>>>> on >>>>>> neither system. >>>>>> >>>>>> Any ideas? >>>>>> >>>>>> From elric.mn at gmail.com Fri Feb 5 22:52:39 2016 From: elric.mn at gmail.com (Elric Morgenstern) Date: Fri, 5 Feb 2016 23:52:39 +0100 Subject: Canvas Clip performance In-Reply-To: <56B4DE0A.80105@oracle.com> References: <56B3D637.5040209@oracle.com> <56B3E66A.9090603@oracle.com> <56B4C0FC.9090303@oracle.com> <56B4DE0A.80105@oracle.com> Message-ID: Hi Chien, Kevin, this is the result of verbose=true: Prism pipeline init order: d3d sw Using native-based Pisces rasterizer Using dirty region optimizations Not using texture mask for primitives Not forcing power of 2 sizes for textures Using hardware CLAMP_TO_ZERO mode Opting in for HiDPI pixel scaling Prism pipeline name = com.sun.prism.d3d.D3DPipeline Loading D3D native library ... succeeded. D3DPipelineManager: Created D3D9Ex device Direct3D initialization succeeded (X) Got class = class com.sun.prism.d3d.D3DPipeline Initialized prism pipeline: com.sun.prism.d3d.D3DPipeline Maximum supported texture size: 8192 Maximum texture size clamped to 4096 OS Information: Windows 7 build 7601 D3D Driver Information: Intel(R) HD Graphics \\.\DISPLAY1 Driver igdumdx32.dll, version 8.15.10.2827 Pixel Shader version 3.0 Device : ven_8086, dev_0046, subsys_040A1028 Max Multisamples supported: 0 vsync: true vpipe: true Loading Prism common native library ... succeeded. The performance when using oval clipping also drops considerably when using the software pipe, but to about the same as when using D3D clipping. D3D no clipping: very comfortable 60 FPS D3D clipping: 10 FPS Software no clipping: 30 FPS Software clipping: 8 FPS I haven't filed a bug (yet), because there are already some issues that could be related to my problem: http://bugs.java.com/bugdatabase/view_bug.do?bug_id=8090206 http://bugs.java.com/bugdatabase/view_bug.do?bug_id=8088687 The comments in this "fixed" bug report also indicate a stark disparity between rectangular and oval clipping: http://bugs.java.com/bugdatabase/view_bug.do?bug_id=8098079 Then there is this, but it's already set to fixed: http://bugs.java.com/bugdatabase/view_bug.do?bug_id=8096359 It's worth mentioning that it's not just an oval clip shape that causes performance drops, but also using more than one rectangular shape. Every rectangular shape beyond the first seems to reduce my FPS by 10. I'm using JDK 1.80_60 by the way. On Fri, Feb 5, 2016 at 6:38 PM, Chien Yang wrote: > It will be great if you can include in your bug report the following 2 > piece of information: > > 1) Run your program with -Dprism.verbose=true. This will give us the > graphics hardware information of your system. > > 2) Run your program with -Dprism.order=sw. This will force JavaFX to use > its software pipe instead of hardware graphics acceleration. It will be > good to know whether the poor performance is due to use of d3d pipe. > > - Chien > > > On 2/5/16, 7:34 AM, Kevin Rushforth wrote: > >> Please file a bug. It might be possible for us to find a workaround, >> although it might also be possible that this is just an unfortunate >> limitation of Intel HD. >> >> -- Kevin >> >> >> Elric Morgenstern wrote: >> >>> Ok. Maybe the problems I am experiencing now with JavaFX are the reason >>> why >>> D3D is not enabled for J2D? >>> >>> I think Intel Graphics are rather widespread among laptops, so I'm a bit >>> surprised at the huge performance drop (from solid 60 FPS to 8 once I >>> use a >>> spherical clip shape). I'd think Intel Graphics hardware form part of the >>> test set. I'm using a fairly common laptop (especially around business >>> circles) Dell Latitude E6410. >>> >>> Any chance of this being investigated or do you think I will have to >>> settle >>> with a workaround? >>> >>> >>> On Fri, Feb 5, 2016 at 1:01 AM, Philip Race >>> wrote: >>> >>> On 2/4/16, 2:59 PM, Elric Morgenstern wrote: >>>> >>>> I see. Interesting. Isn't there a switch to toggle it on JDK8? >>>>> >>>>> There is no switch that can enable it if it is disabled by 'default'. >>>> >>>> Assuming you are talking about JavaFX, right? Because you were referring >>>>> to >>>>> Java2D in your reply. >>>>> >>>>> No I am talking about 2D. What I meant was that maybe the performance >>>> issue >>>> is inherent in the card and the only reason it looks OK with Java2D on >>>> Intel is >>>> that we aren't using anything much at all of the Intel chip and are >>>> doing >>>> the work >>>> on the cpu instead. >>>> >>>> -phil. >>>> >>>> >>>> >>>> On Thu, Feb 4, 2016 at 11:52 PM, Philip Race >>>>> wrote: >>>>> >>>>> Java 2D does not (generally) enable D3D on Intel. >>>>> >>>>>> We tried for JDK 8 but there were problems and it was disabled again >>>>>> in >>>>>> 8u40 I think. >>>>>> JDK 9 EA builds (currently) still have it enabled to help get some >>>>>> testing >>>>>> so >>>>>> if you are running an 8ux release you might want to switch to 9 to >>>>>> get a >>>>>> fairer comparison. >>>>>> >>>>>> -phil. >>>>>> >>>>>> >>>>>> >>>>>> On 2/4/16, 2:49 PM, Elric Morgenstern wrote: >>>>>> >>>>>> Hi guys, >>>>>> >>>>>>> I've noticed that clipping performance (Canvas GraphicsContext) is >>>>>>> extremely bad on an Intel HD graphics chip. One rectangular clip is >>>>>>> fine, >>>>>>> anything beyond that, or a spherical clip shape, will bring the >>>>>>> framerate >>>>>>> to its knees. >>>>>>> >>>>>>> I notice no performance difference on my GeForce system, but on the >>>>>>> integrated chip my application is basically insufferable. >>>>>>> >>>>>>> The same thing performed with Java2D experiences no performance >>>>>>> issues >>>>>>> on >>>>>>> neither system. >>>>>>> >>>>>>> Any ideas? >>>>>>> >>>>>>> >>>>>>> From chien.yang at oracle.com Sat Feb 6 01:09:38 2016 From: chien.yang at oracle.com (Chien Yang) Date: Fri, 5 Feb 2016 17:09:38 -0800 Subject: Canvas Clip performance In-Reply-To: References: <56B3D637.5040209@oracle.com> <56B3E66A.9090603@oracle.com> <56B4C0FC.9090303@oracle.com> <56B4DE0A.80105@oracle.com> Message-ID: <56B547D2.5010806@oracle.com> Hi Elric, Thanks for the extra information. This seems to rule out that the drop in performance might have to do with Intel HD: > D3D no clipping: very comfortable 60 FPS > D3D clipping: 10 FPS > Software no clipping: 30 FPS > Software clipping: 8 FPS It will still be useful to us if you can file a performance bug with a test program. This will help us to ensure that future fixes in this area will also cover your test case. Thanks, - Chien On 2/5/2016 2:52 PM, Elric Morgenstern wrote: > Hi Chien, Kevin, > > this is the result of verbose=true: > > Prism pipeline init order: d3d sw > Using native-based Pisces rasterizer > Using dirty region optimizations > Not using texture mask for primitives > Not forcing power of 2 sizes for textures > Using hardware CLAMP_TO_ZERO mode > Opting in for HiDPI pixel scaling > Prism pipeline name = com.sun.prism.d3d.D3DPipeline > Loading D3D native library ... > succeeded. > D3DPipelineManager: Created D3D9Ex device > Direct3D initialization succeeded > (X) Got class = class com.sun.prism.d3d.D3DPipeline > Initialized prism pipeline: com.sun.prism.d3d.D3DPipeline > Maximum supported texture size: 8192 > Maximum texture size clamped to 4096 > OS Information: > Windows 7 build 7601 > D3D Driver Information: > Intel(R) HD Graphics > \\.\DISPLAY1 > Driver igdumdx32.dll, version 8.15.10.2827 > Pixel Shader version 3.0 > Device : ven_8086, dev_0046, subsys_040A1028 > Max Multisamples supported: 0 > vsync: true vpipe: true > > Loading Prism common native library ... > succeeded. > > > The performance when using oval clipping also drops considerably when > using the software pipe, but to about the same as when using D3D clipping. > D3D no clipping: very comfortable 60 FPS > D3D clipping: 10 FPS > > Software no clipping: 30 FPS > Software clipping: 8 FPS > > I haven't filed a bug (yet), because there are already some issues > that could be related to my problem: > http://bugs.java.com/bugdatabase/view_bug.do?bug_id=8090206 > http://bugs.java.com/bugdatabase/view_bug.do?bug_id=8088687 > > The comments in this "fixed" bug report also indicate a stark > disparity between rectangular and oval clipping: > http://bugs.java.com/bugdatabase/view_bug.do?bug_id=8098079 > > Then there is this, but it's already set to fixed: > http://bugs.java.com/bugdatabase/view_bug.do?bug_id=8096359 > > It's worth mentioning that it's not just an oval clip shape that > causes performance drops, but also using more than one rectangular shape. > Every rectangular shape beyond the first seems to reduce my FPS by 10. > > I'm using JDK 1.80_60 by the way. > > > > > On Fri, Feb 5, 2016 at 6:38 PM, Chien Yang > wrote: > > It will be great if you can include in your bug report the > following 2 piece of information: > > 1) Run your program with -Dprism.verbose=true. This will give us > the graphics hardware information of your system. > > 2) Run your program with -Dprism.order=sw. This will force JavaFX > to use its software pipe instead of hardware graphics > acceleration. It will be good to know whether the poor performance > is due to use of d3d pipe. > > - Chien > > > On 2/5/16, 7:34 AM, Kevin Rushforth wrote: > > Please file a bug. It might be possible for us to find a > workaround, although it might also be possible that this is > just an unfortunate limitation of Intel HD. > > -- Kevin > > > Elric Morgenstern wrote: > > Ok. Maybe the problems I am experiencing now with JavaFX > are the reason why > D3D is not enabled for J2D? > > I think Intel Graphics are rather widespread among > laptops, so I'm a bit > surprised at the huge performance drop (from solid 60 FPS > to 8 once I use a > spherical clip shape). I'd think Intel Graphics hardware > form part of the > test set. I'm using a fairly common laptop (especially > around business > circles) Dell Latitude E6410. > > Any chance of this being investigated or do you think I > will have to settle > with a workaround? > > > On Fri, Feb 5, 2016 at 1:01 AM, Philip Race > > > wrote: > > On 2/4/16, 2:59 PM, Elric Morgenstern wrote: > > I see. Interesting. Isn't there a switch to toggle > it on JDK8? > > There is no switch that can enable it if it is > disabled by 'default'. > > Assuming you are talking about JavaFX, right? > Because you were referring > to > Java2D in your reply. > > No I am talking about 2D. What I meant was that maybe > the performance issue > is inherent in the card and the only reason it looks > OK with Java2D on > Intel is > that we aren't using anything much at all of the Intel > chip and are doing > the work > on the cpu instead. > > -phil. > > > > On Thu, Feb 4, 2016 at 11:52 PM, Philip > Race > > wrote: > > Java 2D does not (generally) enable D3D on Intel. > > We tried for JDK 8 but there were problems and > it was disabled again in > 8u40 I think. > JDK 9 EA builds (currently) still have it > enabled to help get some > testing > so > if you are running an 8ux release you might > want to switch to 9 to get a > fairer comparison. > > -phil. > > > > On 2/4/16, 2:49 PM, Elric Morgenstern wrote: > > Hi guys, > > I've noticed that clipping performance > (Canvas GraphicsContext) is > extremely bad on an Intel HD graphics > chip. One rectangular clip is > fine, > anything beyond that, or a spherical clip > shape, will bring the > framerate > to its knees. > > I notice no performance difference on my > GeForce system, but on the > integrated chip my application is > basically insufferable. > > The same thing performed with Java2D > experiences no performance issues > on > neither system. > > Any ideas? > > > From johan at lodgon.com Mon Feb 8 11:25:17 2016 From: johan at lodgon.com (Johan Vos) Date: Mon, 8 Feb 2016 12:25:17 +0100 Subject: pisces, produceFillAlphas In-Reply-To: References: <561FF83E.3000407@oracle.com> <5620261F.7060206@oracle.com> Message-ID: It's been a while, but I did more investigations in the performance of JavaFX on mobile. The good news: I had a look at a number of individual applications, and managed to increase fps for all of them with a factor between 2 and 5 (e.g. 15 fps -> 60 fps) The bad news: it is hard to do this in a generic way. There are many tips described on this wiki page: https://wiki.openjdk.java.net/display/OpenJFX/Performance+Tips+and+Tricks One of the important things is this: To cache, or not to cache? That is the question! - Every time the thing being cached changes, it is very expensive to redraw it. - But reusing the baked image a zillion times is faster than redrawing! That turns out to be very true. By caching Nodes that hardly change between pulses, performance can improve a lot. However, caching the wrong Nodes decreases performance. In the end, a smart algorithm that determines which Nodes are candidates for being cached would help with this (sort of "hotspot" improvements). For now, I think the JavaFX libraries can address this. Nodes that are used for a ToolBar are for example good candidates for being cached. - Johan 2015-11-17 20:59 GMT+01:00 Johan Vos : > This is an ongoing effort. > Performance is #1 on my list, but it is also a very complex issue. I will > inform this list on relevant progress I make. It is impossible to say how > much time I need for this, but in the end, I'll get there (and only then I > will be able to tell how much time it took). > > - Johan > > On Tue, Nov 17, 2015 at 11:56 AM, Felix Bembrick > > wrote: > > > Hi Johan, > > > > Have you been able to find enough time to be able to answer this > question? > > In my present situation, clarity on these issues is extremely important > to > > me and I would guess to many others as well. > > > > Thanks, > > > > Felix > > > > > On 18 Oct 2015, at 19:01, Felix Bembrick > > wrote: > > > > > > Hi Johan, > > > > > > If you have been getting acceptable but not stunning performance on > > Android and all this time hardware acceleration was not being utilised > then > > it sounds like there is some serious room for some dramatic performance > > increases. > > > > > > Not being that familiar with the finer points of how JavaFX is > > implemented on Android, just how much work is involved in accessing that > > hardware acceleration? Any timeline? > > > > > > I expect that implementing this significant change could be a > > make-or-break factor in determining whether JavaFX is truly viable and > > successful on Android. > > > > > > Good luck Johan! > > > > > > Cheers, > > > > > > Felix > > > > > >> On 17 Oct 2015, at 19:49, Johan Vos wrote: > > >> > > >> As a follow-up on the second part: after about 2 years working on > > JavaFX on > > >> Android, I discovered we are not even using Hardware Acceleration. We > > >> create a SurfaceView and render on that, but it turns out SurfaceView > is > > >> never Hardware Accelerated. The positive thing is that this means > there > > is > > >> even more room for optimization :) > > >> > > >> - Johan > > >> > > >>> On Fri, Oct 16, 2015 at 7:55 PM, Johan Vos > > wrote: > > >>> > > >>> Hi, > > >>> > > >>> Thanks for the suggestions. There are 2 different things: > > >>> > > >>> 1. It seems indeed there is not much being cached, so there are > > definitely > > >>> improvements possible. It also require e.g. VirtualFlow to use the > > >>> Node.setCache(true) in order to cache. The combination of this with > the > > >>> prism.scrollcacheopt reduces the rendering calls. I think the only > > penalty > > >>> is memory, but so far, we didn't run into issues with too high GC > > activity. > > >>> > > >>> 2. Calls to glDrawElements() inside nDrawIndexedQuads take about 100 > > times > > >>> longer on the Nexus 6 compared to the iPhone 6 (e.g. 100,000ns vs > > 1000ns). > > >>> I'll have to look into some EGL options. > > >>> > > >>> - Johan > > >>> > > >>> > > >>> On Fri, Oct 16, 2015 at 12:18 AM, Jim Graham < > james.graham at oracle.com> > > >>> wrote: > > >>> > > >>>> Chien pointed out a system property that is currently disabling the > > >>>> scrolling optimization. For its implementation look at > > CacheFilter.java, > > >>>> in particular the invalidateByTranslation() method and all that it > > kicks > > >>>> off. > > >>>> > > >>>> Another thing to look at is that we added alpha batching to the code > > >>>> which should be batching all of the output of the produceAlphas > calls > > into > > >>>> a texture and then drawing all of the quads together - provided that > > they > > >>>> are all being filled with simple colors (they can have alpha, but > they > > >>>> can't be gradients, etc.). This should be managed by the > > >>>> BaseContext.updateMaskTexture() method which controls the single > batch > > >>>> texture. > > >>>> > > >>>> Again, are there similar number of invocations of the glDrawElements > > on > > >>>> the 2 platforms? > > >>>> > > >>>> ...jim > > >>>> > > >>>>> On 10/15/15 12:30 PM, Johan Vos wrote: > > >>>>> > > >>>>> Thanks Jim. > > >>>>> I tried with different optimization flags, but it doesn't make a > big > > >>>>> difference. Tracing it down to system calls, somehow the gl > > >>>>> implementation seems be be slower (glDrawElements(GL_TRIANGLES, > > numQuads > > >>>>> * 2 * 3, GL_UNSIGNED_SHORT, 0) takes more time on Android than on > > iOS) > > >>>>> per invocation. The number of invocations is comparable between iOS > > and > > >>>>> Android. > > >>>>> > > >>>>> If you can give me a direction on where to search for the disabled > > >>>>> scrolling optimization, I'll try to re-enable that and see how it > > >>>>> improves performance. It might be a huge and quick win... > > >>>>> > > >>>>> Thanks again, > > >>>>> > > >>>>> - Johan > > >>>>> > > >>>>> On Thu, Oct 15, 2015 at 9:02 PM, Jim Graham < > james.graham at oracle.com > > >>>>> > wrote: > > >>>>> > > >>>>> Perhaps optimization flags with the native compiler? Also, was > it > > >>>>> called a similar number of times on both? > > >>>>> > > >>>>> Ideally we'd just be using copyArea for the scrolling, but at one > > >>>>> point we disabled the scrolling optimizations on retina MBP > because > > >>>>> they didn't work with a scale factor and I don't think we > reenabled > > >>>>> them yet. That would kill scrolling performance on mobile as a > > >>>>> result of having to rerender the scene on each scroll regardless > of > > >>>>> how long produceAlphas takes... > > >>>>> > > >>>>> ...jim > > >>>>> > > >>>>> > > >>>>> On 10/15/15 4:27 AM, Johan Vos wrote: > > >>>>> > > >>>>> After spending lots of time optimizing JavaFX on iOS, I am > now > > >>>>> at the point > > >>>>> where scrolling is 10 times faster on iOS than on Android. > > >>>>> The scrolling in the iOS version of the Gluon JavaOne mobile > > >>>>> schedule > > >>>>> builder is pretty good imho. On Android, it is much slower. I > > >>>>> profiled and > > >>>>> compared both, and it turns out that on Android, we spend > lots > > >>>>> of time in > > >>>>> the native implementation of > > >>>>> NativePiscesRasterizer.produceFillAlphas > > >>>>> (implemented in native-prism/NativePiscesRasterizer.c) > > >>>>> > > >>>>> On average, calling this native function on an iPhone 6 takes > > >>>>> 40,000ns > > >>>>> whereas on a Nexus 6, this takes about 800,000ns. > > >>>>> > > >>>>> If anyone has a suggestion on how to improve or avoid this, > I'm > > >>>>> all ears. > > >>>>> > > >>>>> Thanks, > > >>>>> > > >>>>> - Johan > > >>> > > > From kevin.rushforth at oracle.com Mon Feb 8 21:05:32 2016 From: kevin.rushforth at oracle.com (Kevin Rushforth) Date: Mon, 08 Feb 2016 13:05:32 -0800 Subject: 9-dev unlocked following sanity testing Message-ID: <56B9031C.4070006@oracle.com> From morris.meyer at oracle.com Tue Feb 9 22:01:47 2016 From: morris.meyer at oracle.com (Morris Meyer) Date: Tue, 9 Feb 2016 17:01:47 -0500 Subject: [9] RFR-XL: 8091485: Ensemble8: Review each sample Message-ID: <56BA61CB.2090609@oracle.com> Folks, Enclosed is my very large webrev for Ensemble8 that has visual appearance changes for each and every sample file. Every sample was gone through and checked for appearance, related docs and links. Every sample code file was scrubbed for bad variable names, long-lines, readability, clarity, and comment format. Every sample now has a link to the JavaFX documentation relevant to that sample, an ordered list of API links for the sample and a populated list of related samples. Each link in each sample was tested to verify correct linkage and accuracy. All changes were to the samples source code and not Samples.java file. Every import statement in each sample was tested to see if the source code actually used it. Lots of imports were culled. After these changes Ensemble8 would be much more ready for the Apple App Store. I apologize in advance for the length of this webrev and will buy lunch for anyone that actually goes through it next time I'm in Santa Clara. Use the follow to test out the changes: ant -Dplatforms.JDK_1.8.home=`/usr/libexec/java_home` ensemble-generate-samples-class run Thanks! --morris meyer WEBREV - http://cr.openjdk.java.net/~morris/JDK-8091485.03/ BUG - https://bugs.openjdk.java.net/browse/JDK-8091485 From David.Hill at Oracle.com Wed Feb 10 13:56:56 2016 From: David.Hill at Oracle.com (David Hill) Date: Wed, 10 Feb 2016 08:56:56 -0500 Subject: review: checkrepo should suggest -a Message-ID: <56BB41A8.1020208@Oracle.com> Kevin, diff is inline in: https://bugs.openjdk.java.net/browse/JDK-8149547 -- David Hill Java Embedded Development "A man's feet should be planted in his country, but his eyes should survey the world." -- George Santayana (1863 - 1952) From David.Hill at Oracle.com Thu Feb 11 16:02:53 2016 From: David.Hill at Oracle.com (David Hill) Date: Thu, 11 Feb 2016 11:02:53 -0500 Subject: Fwd: [JBS] {Commented} (JDK-8149490) Null pointer exception in print logger In-Reply-To: References: Message-ID: <56BCB0AD.4030105@Oracle.com> Hi all, I got a bit diverted chasing an NPE when I turned on -Djavafx.pulseLogger=true with a test app. It took me a bit longer to untangle what was going on, but now that I have a clue, I need to get back to other stuff for a bit. I do need some feedback from some of you that have been in the pulse/repaint/logger code though..... below is the conclusion I made after my dig. I would appreciate any comments/thoughts on it added into the bug. Dave David Hill *commented* on Bug JDK-8149490 Re: Null pointer exception in print logger The core issue here: There is an expectation in Printlogger that you will have a sequence of: pulseStart renderStart pulseEnd renderEnd << missing The failing case is when we have a pulse that does not have a renderEnd. This seems to be possible as there are at least one places where we may exit the repaint early, and so do not call PaintCollector.done(). See ViewScene.repaint() right at the beginning for a good example. It seems like we could workaround the issue in PrintLogger - but there is at least one other consumer of these messages (JFR). So the probable likely fix is either a) detecting the "no repaint" case earlier and not calling repaint at all. b) changing the repaint paths so we always notify PaintCollector.done(). Also note: there are some real logic problems in PrintLogger related to the PulseData linked list. The case where the head is not available will lead to a case where we always add a new member to the list, which is an obvious memory leak. Add Comment Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) Atlassian logo From kevin.rushforth at oracle.com Thu Feb 11 18:09:23 2016 From: kevin.rushforth at oracle.com (Kevin Rushforth) Date: Thu, 11 Feb 2016 10:09:23 -0800 Subject: [9] review request: Message-ID: <56BCCE53.3090404@oracle.com> Chien & Dave, Please review the following: https://bugs.openjdk.java.net/browse/JDK-8148969 http://cr.openjdk.java.net/~kcr/8148969/webrev.00/ Note to all: JavaFX developers will need to be aware that jfxrt.jar has moved. Instead of it being in build/sdk/rt/lib/ext/jfxrt.jar it is in build/sdk/lib/jfxrt.jar. Most of the changes in this webrev are to account for this. If any of you have scripts to run an app using your just-built jfxrt.jar (I know I do), you will need to adjust your scripts once this goes in. -- Kevin From kevin.rushforth at oracle.com Thu Feb 11 18:10:29 2016 From: kevin.rushforth at oracle.com (Kevin Rushforth) Date: Thu, 11 Feb 2016 10:10:29 -0800 Subject: [9] review request: 8148969: Reorganize FX SDK layout to match JDK 9 layout In-Reply-To: <56BCCE53.3090404@oracle.com> References: <56BCCE53.3090404@oracle.com> Message-ID: <56BCCE95.8010603@oracle.com> [resend with correct subject line] Chien & Dave, Please review the following: https://bugs.openjdk.java.net/browse/JDK-8148969 http://cr.openjdk.java.net/~kcr/8148969/webrev.00/ Note to all: JavaFX developers will need to be aware that jfxrt.jar has moved. Instead of it being in build/sdk/rt/lib/ext/jfxrt.jar it is in build/sdk/lib/jfxrt.jar. Most of the changes in this webrev are to account for this. If any of you have scripts to run an app using your just-built jfxrt.jar (I know I do), you will need to adjust your scripts once this goes in. -- Kevin From vadim.pakhnushev at oracle.com Fri Feb 12 14:30:00 2016 From: vadim.pakhnushev at oracle.com (Vadim Pakhnushev) Date: Fri, 12 Feb 2016 17:30:00 +0300 Subject: In(Sanity) Testing Mondays Message-ID: <56BDEC68.5080607@oracle.com> Reminder, Monday is our weekly sanity testing. You can find your testing assignment at: https://wiki.openjdk.java.net/display/OpenJFX/Sanity+Testing Also please remember that the repo will be locked from 1am PST until 1pm PST. Happy testing! Thanks, Vadim From kevin.rushforth at oracle.com Mon Feb 15 21:00:31 2016 From: kevin.rushforth at oracle.com (Kevin Rushforth) Date: Mon, 15 Feb 2016 13:00:31 -0800 Subject: 9-dev unlocked following sanity testing Message-ID: <56C23C6F.60707@oracle.com> From elina.kleyman at oracle.com Tue Feb 16 10:29:13 2016 From: elina.kleyman at oracle.com (Elina Kleyman Matok) Date: Tue, 16 Feb 2016 02:29:13 -0800 (PST) Subject: [9] Review request for 8130381 - KeyEvents lost when focused node is removed from the Scene Message-ID: <7b04e9bd-524a-4754-83bb-569c7ea69a42@default> Chien, Kevin, guys, Please review fix for next issue: JIRA: https://bugs.openjdk.java.net/browse/JDK-8130381 WEBREV: http://cr.openjdk.java.net/~ekleyman/8130381/ Thanks, Elina From David.Hill at Oracle.com Tue Feb 16 21:49:54 2016 From: David.Hill at Oracle.com (David Hill) Date: Tue, 16 Feb 2016 16:49:54 -0500 Subject: please review: refactor test launchers to make common the building of the command Message-ID: <56C39982.8000907@Oracle.com> Kevin, could you please review: webrev: http://cr.openjdk.java.net/~ddhill/8147427 bug: https://bugs.openjdk.java.net/browse/JDK-8147427 -- David Hill Java Embedded Development "A man's feet should be planted in his country, but his eyes should survey the world." -- George Santayana (1863 - 1952) From herve.girod at gmail.com Tue Feb 16 22:10:46 2016 From: herve.girod at gmail.com (=?utf-8?Q?Herv=C3=A9_Girod?=) Date: Tue, 16 Feb 2016 23:10:46 +0100 Subject: Traversal sub-system Message-ID: <69DE0C92-1DE1-4718-88C4-AB61764541B4@gmail.com> Hello, I'm sure this has already been answered before in this list, but is it planned to move the existing traversal sub-system (focus system) to a public API for JDK 9? Herv? Sent from my iPad From jonathan.giles at oracle.com Tue Feb 16 22:13:45 2016 From: jonathan.giles at oracle.com (Jonathan Giles) Date: Wed, 17 Feb 2016 11:13:45 +1300 Subject: Traversal sub-system In-Reply-To: <69DE0C92-1DE1-4718-88C4-AB61764541B4@gmail.com> References: <69DE0C92-1DE1-4718-88C4-AB61764541B4@gmail.com> Message-ID: <56C39F19.2030603@oracle.com> Yes, it is something that Leif is exploring for JDK 9. It is not a hard commitment, but is something we are trying to get into JDK 9. See here: https://bugs.openjdk.java.net/browse/JDK-8091673 -- Jonathan On 17/02/16 11:10 AM, Herv? Girod wrote: > Hello, I'm sure this has already been answered before in this list, but is it planned to move the existing traversal sub-system (focus system) to a public API for JDK 9? > > Herv? > > Sent from my iPad From james.graham at oracle.com Tue Feb 16 22:22:49 2016 From: james.graham at oracle.com (Jim Graham) Date: Tue, 16 Feb 2016 14:22:49 -0800 Subject: [Review request] 8088853: Applying dashed border to separator makes whole application hang In-Reply-To: <56C1AD80.6010501@oracle.com> References: <5695316A.7070902@oracle.com> <56953A82.7020901@oracle.com> <56955219.8070200@oracle.com> <56C1AD80.6010501@oracle.com> Message-ID: <56C3A139.6070702@oracle.com> [I believe you sent this to the wrong mailing list - the "-request" list is for changing your membership to the mailing list, not for sending mail to the list itself. I fixed it here in my reply...] That looks fine. I'll note that the "dashCumulative" variable does not need to be computed if you don't recompute the gapLength at line 1580, so that line (#1578) can be moved inside the if statement. Other than that, it looks good... ...jim On 2/15/2016 2:50 AM, Andrey Rusakov wrote: > Hello, everyone! Could you look at my fix for JDK-8147944? > http://cr.openjdk.java.net/~arusakov/8088853/webrev.00 From herve.girod at gmail.com Tue Feb 16 23:14:17 2016 From: herve.girod at gmail.com (Herve Girod) Date: Wed, 17 Feb 2016 00:14:17 +0100 Subject: Traversal sub-system In-Reply-To: <56C39F19.2030603@oracle.com> References: <69DE0C92-1DE1-4718-88C4-AB61764541B4@gmail.com> <56C39F19.2030603@oracle.com> Message-ID: Thanks for the information! Cet e-mail a ?t? envoy? depuis un ordinateur prot?g? par Avast. www.avast.com <#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2> 2016-02-16 23:13 GMT+01:00 Jonathan Giles : > Yes, it is something that Leif is exploring for JDK 9. It is not a hard > commitment, but is something we are trying to get into JDK 9. See here: > > https://bugs.openjdk.java.net/browse/JDK-8091673 > > -- Jonathan > > > On 17/02/16 11:10 AM, Herv? Girod wrote: > >> Hello, I'm sure this has already been answered before in this list, but >> is it planned to move the existing traversal sub-system (focus system) to a >> public API for JDK 9? >> >> Herv? >> >> Sent from my iPad >> > > From kevin.rushforth at oracle.com Tue Feb 16 23:48:32 2016 From: kevin.rushforth at oracle.com (Kevin Rushforth) Date: Tue, 16 Feb 2016 15:48:32 -0800 Subject: [9] review request: Message-ID: <56C3B550.4000705@oracle.com> Jim and Alexander, Please review the following fix to allow JFXPanel to compile (and run) again on JDK 9. https://bugs.openjdk.java.net/browse/JDK-8149967 http://cr.openjdk.java.net/~kcr/8149967/webrev.00/ Note that I did not provide a fallback to the existing JDK 8 method, since we are going to require JDK 9 soon anyway. Note also that there is still one more bug fix needed before we can compile everything with JDK 9, so this is necessary but not sufficient. -- Kevin From kevin.rushforth at oracle.com Tue Feb 16 23:49:39 2016 From: kevin.rushforth at oracle.com (Kevin Rushforth) Date: Tue, 16 Feb 2016 15:49:39 -0800 Subject: [9] review request: 8149967: Cannot compile JFXPanel with JDK 9: SurfaceData::getDefaultScale not found In-Reply-To: <56C3B550.4000705@oracle.com> References: <56C3B550.4000705@oracle.com> Message-ID: <56C3B593.9090502@oracle.com> [resend with correct subject line] Jim and Alexander, Please review the following fix to allow JFXPanel to compile (and run) again on JDK 9. https://bugs.openjdk.java.net/browse/JDK-8149967 http://cr.openjdk.java.net/~kcr/8149967/webrev.00/ Note that I did not provide a fallback to the existing JDK 8 method, since we are going to require JDK 9 soon anyway. Note also that there is still one more bug fix needed before we can compile everything with JDK 9, so this is necessary but not sufficient. -- Kevin From james.graham at oracle.com Tue Feb 16 23:53:49 2016 From: james.graham at oracle.com (Jim Graham) Date: Tue, 16 Feb 2016 15:53:49 -0800 Subject: [9] review request: 8149967: Cannot compile JFXPanel with JDK 9: SurfaceData::getDefaultScale not found In-Reply-To: <56C3B593.9090502@oracle.com> References: <56C3B550.4000705@oracle.com> <56C3B593.9090502@oracle.com> Message-ID: <56C3B68D.5070301@oracle.com> I added a comment on the bug about BC, but it sounds like you already considered it. I'm fine with this as is, but would push for moving to JDK9 ASAP... ...jim On 2/16/2016 3:49 PM, Kevin Rushforth wrote: > [resend with correct subject line] > > Jim and Alexander, > > Please review the following fix to allow JFXPanel to compile (and run) > again on JDK 9. > > https://bugs.openjdk.java.net/browse/JDK-8149967 > http://cr.openjdk.java.net/~kcr/8149967/webrev.00/ > > Note that I did not provide a fallback to the existing JDK 8 method, > since we are going to require JDK 9 soon anyway. > > Note also that there is still one more bug fix needed before we can > compile everything with JDK 9, so this is necessary but not sufficient. > > -- Kevin > From chien.yang at oracle.com Wed Feb 17 01:24:58 2016 From: chien.yang at oracle.com (Chien Yang) Date: Tue, 16 Feb 2016 17:24:58 -0800 Subject: Code Review Request For 8137252: JavaFX StackPane bounds not updated Message-ID: <56C3CBEA.9060001@oracle.com> Hi Kevin and Jonathan, Please review the proposed fix and the detail of the fix is recorded in the JIRA: JIRA: https://bugs.openjdk.java.net/browse/JDK-8137252 Webrev: http://cr.openjdk.java.net/~ckyang/JDK-8137252/webrev.00/ Thanks, - Chien From andrey.rusakov at oracle.com Wed Feb 17 09:11:49 2016 From: andrey.rusakov at oracle.com (Andrey Rusakov) Date: Wed, 17 Feb 2016 12:11:49 +0300 Subject: [Review request] 8088853: Applying dashed border to separator makes whole application hang In-Reply-To: <56C3A139.6070702@oracle.com> References: <5695316A.7070902@oracle.com> <56953A82.7020901@oracle.com> <56955219.8070200@oracle.com> <56C1AD80.6010501@oracle.com> <56C3A139.6070702@oracle.com> Message-ID: <56C43955.7050209@oracle.com> Updated that: http://cr.openjdk.java.net/~arusakov/8088853/webrev.01 17.02.2016 01:22, Jim Graham ?????: > [I believe you sent this to the wrong mailing list - the "-request" > list is for changing your membership to the mailing list, not for > sending mail to the list itself. I fixed it here in my reply...] > > That looks fine. I'll note that the "dashCumulative" variable does > not need to be computed if you don't recompute the gapLength at line > 1580, so that line (#1578) can be moved inside the if statement. > > Other than that, it looks good... > > ...jim > > On 2/15/2016 2:50 AM, Andrey Rusakov wrote: >> Hello, everyone! Could you look at my fix for JDK-8147944? >> http://cr.openjdk.java.net/~arusakov/8088853/webrev.00 From Sergey.Bylokhov at oracle.com Wed Feb 17 13:17:59 2016 From: Sergey.Bylokhov at oracle.com (Sergey Bylokhov) Date: Wed, 17 Feb 2016 16:17:59 +0300 Subject: [9] review request: 8149967: Cannot compile JFXPanel with JDK 9: SurfaceData::getDefaultScale not found In-Reply-To: <56C3B68D.5070301@oracle.com> References: <56C3B550.4000705@oracle.com> <56C3B593.9090502@oracle.com> <56C3B68D.5070301@oracle.com> Message-ID: <56C47307.2050109@oracle.com> Note that in jdk9 the same data can be obtained via GraphicsConfiguration.getDefaultTransform(); On 17.02.16 2:53, Jim Graham wrote: > I added a comment on the bug about BC, but it sounds like you already > considered it. I'm fine with this as is, but would push for moving to > JDK9 ASAP... > > ...jim > > On 2/16/2016 3:49 PM, Kevin Rushforth wrote: >> [resend with correct subject line] >> >> Jim and Alexander, >> >> Please review the following fix to allow JFXPanel to compile (and run) >> again on JDK 9. >> >> https://bugs.openjdk.java.net/browse/JDK-8149967 >> http://cr.openjdk.java.net/~kcr/8149967/webrev.00/ >> >> Note that I did not provide a fallback to the existing JDK 8 method, >> since we are going to require JDK 9 soon anyway. >> >> Note also that there is still one more bug fix needed before we can >> compile everything with JDK 9, so this is necessary but not sufficient. >> >> -- Kevin >> -- Best regards, Sergey. From kevin.rushforth at oracle.com Wed Feb 17 14:41:14 2016 From: kevin.rushforth at oracle.com (Kevin Rushforth) Date: Wed, 17 Feb 2016 06:41:14 -0800 Subject: [9] review request: 8149967: Cannot compile JFXPanel with JDK 9: SurfaceData::getDefaultScale not found In-Reply-To: <56C3B68D.5070301@oracle.com> References: <56C3B550.4000705@oracle.com> <56C3B593.9090502@oracle.com> <56C3B68D.5070301@oracle.com> Message-ID: <56C4868A.6080708@oracle.com> Thanks. I'll send out a formal "heads-up" later today about moving to JDK 9 as the boot JDK. I hope to do this within two weeks if no issues arise. -- Kevin Jim Graham wrote: > I added a comment on the bug about BC, but it sounds like you already > considered it. I'm fine with this as is, but would push for moving to > JDK9 ASAP... > > ...jim > > On 2/16/2016 3:49 PM, Kevin Rushforth wrote: >> [resend with correct subject line] >> >> Jim and Alexander, >> >> Please review the following fix to allow JFXPanel to compile (and run) >> again on JDK 9. >> >> https://bugs.openjdk.java.net/browse/JDK-8149967 >> http://cr.openjdk.java.net/~kcr/8149967/webrev.00/ >> >> Note that I did not provide a fallback to the existing JDK 8 method, >> since we are going to require JDK 9 soon anyway. >> >> Note also that there is still one more bug fix needed before we can >> compile everything with JDK 9, so this is necessary but not sufficient. >> >> -- Kevin >> From kevin.rushforth at oracle.com Wed Feb 17 14:52:47 2016 From: kevin.rushforth at oracle.com (Kevin Rushforth) Date: Wed, 17 Feb 2016 06:52:47 -0800 Subject: [9] review request: 8149967: Cannot compile JFXPanel with JDK 9: SurfaceData::getDefaultScale not found In-Reply-To: <56C47307.2050109@oracle.com> References: <56C3B550.4000705@oracle.com> <56C3B593.9090502@oracle.com> <56C3B68D.5070301@oracle.com> <56C47307.2050109@oracle.com> Message-ID: <56C4893F.4090305@oracle.com> Thanks, Sergey. I will file a follow-up issue to remove the reflection code and provide a suitable replacement. -- Kevin Sergey Bylokhov wrote: > Note that in jdk9 the same data can be obtained via > GraphicsConfiguration.getDefaultTransform(); > > On 17.02.16 2:53, Jim Graham wrote: >> I added a comment on the bug about BC, but it sounds like you already >> considered it. I'm fine with this as is, but would push for moving to >> JDK9 ASAP... >> >> ...jim >> >> On 2/16/2016 3:49 PM, Kevin Rushforth wrote: >>> [resend with correct subject line] >>> >>> Jim and Alexander, >>> >>> Please review the following fix to allow JFXPanel to compile (and run) >>> again on JDK 9. >>> >>> https://bugs.openjdk.java.net/browse/JDK-8149967 >>> http://cr.openjdk.java.net/~kcr/8149967/webrev.00/ >>> >>> Note that I did not provide a fallback to the existing JDK 8 method, >>> since we are going to require JDK 9 soon anyway. >>> >>> Note also that there is still one more bug fix needed before we can >>> compile everything with JDK 9, so this is necessary but not sufficient. >>> >>> -- Kevin >>> > > From kevin.rushforth at oracle.com Wed Feb 17 15:01:02 2016 From: kevin.rushforth at oracle.com (Kevin Rushforth) Date: Wed, 17 Feb 2016 07:01:02 -0800 Subject: [9] review request: 8149967: Cannot compile JFXPanel with JDK 9: SurfaceData::getDefaultScale not found In-Reply-To: <56C4868A.6080708@oracle.com> References: <56C3B550.4000705@oracle.com> <56C3B593.9090502@oracle.com> <56C3B68D.5070301@oracle.com> <56C4868A.6080708@oracle.com> Message-ID: <56C48B2E.5050206@oracle.com> Also, I plan to fix all remaining issues in the next day or two such that developers could switch to a JDK 9 boot JDK by the end of this week, which should make the fact that the JFXPanel scale is wrong when testing with JDK 8 less of a concern. -- Kevin Kevin Rushforth wrote: > Thanks. I'll send out a formal "heads-up" later today about moving to > JDK 9 as the boot JDK. I hope to do this within two weeks if no issues > arise. > > -- Kevin > > > Jim Graham wrote: >> I added a comment on the bug about BC, but it sounds like you already >> considered it. I'm fine with this as is, but would push for moving >> to JDK9 ASAP... >> >> ...jim >> >> On 2/16/2016 3:49 PM, Kevin Rushforth wrote: >>> [resend with correct subject line] >>> >>> Jim and Alexander, >>> >>> Please review the following fix to allow JFXPanel to compile (and run) >>> again on JDK 9. >>> >>> https://bugs.openjdk.java.net/browse/JDK-8149967 >>> http://cr.openjdk.java.net/~kcr/8149967/webrev.00/ >>> >>> Note that I did not provide a fallback to the existing JDK 8 method, >>> since we are going to require JDK 9 soon anyway. >>> >>> Note also that there is still one more bug fix needed before we can >>> compile everything with JDK 9, so this is necessary but not sufficient. >>> >>> -- Kevin >>> From robert.fisher.ext at zeiss.com Wed Feb 17 15:43:19 2016 From: robert.fisher.ext at zeiss.com (Fisher, Robert) Date: Wed, 17 Feb 2016 15:43:19 +0000 Subject: MOVE cursor not visible on Mac OS Message-ID: <025E25CA98F8AE46BE306AB33F6A38D5012A3A24@ADEFUE01SMS003.cznet.zeiss.org> Hello, It seems the MOVE cursor is not displayed on Mac OS. You just get the default cursor. You can reproduce this easily e.g. using a ScrollPane with setPannable(true). Is this a bug or a restriction of Mac OS itself? I think there is an appropriate cursor available somehow, because in Google maps you get the correct cursor and it looks just like a native one. Cheers, Rob From stefan at endrullis.de Wed Feb 17 17:19:40 2016 From: stefan at endrullis.de (Stefan Endrullis) Date: Wed, 17 Feb 2016 18:19:40 +0100 Subject: plans to make JavaFX 8 platform independent again? Message-ID: <56C4ABAC.3090304@endrullis.de> Dear JavaFX team, over years one of the key features of Java was its platform independence. A Java application would run under Windows, Mac OS, and Linux (if well programmed). Since https://bugs.openjdk.java.net/browse/JDK-8146325 this is no longer the case. Once you use the JavaFX Spinner component your application will still work under Windows, but will crash under Linux. Since this bug attacks a fundamental feature of Java we expected it to be fixed quite fast and definitely in Java 8. But now we discover that it's planned to be fixed in Java 9 only. Does this mean that Java 8 is not considered to be platform independent anymore? Do we have to start deploying different jars for different platforms now? Best regards, Stefan Endrullis -- Stefan Endrullis Wissenschaftlicher Mitarbeiter FB MINT Institut f?r Angewandte Trainingswissenschaft Fachbereich MINT Marschnerstra?e 29 04109 Leipzig www.sport-iat.de Tel.: 0341 4945 217 Fax: 0341 4945 400 E-Mail: endrullis at iat.uni-leipzig.de From kevin.rushforth at oracle.com Wed Feb 17 17:30:50 2016 From: kevin.rushforth at oracle.com (Kevin Rushforth) Date: Wed, 17 Feb 2016 09:30:50 -0800 Subject: plans to make JavaFX 8 platform independent again? In-Reply-To: <56C4ABAC.3090304@endrullis.de> References: <56C4ABAC.3090304@endrullis.de> Message-ID: <56C4AE4A.9010708@oracle.com> Hi Stefan, Java and JavaFX are platform-independent, so asking whether we will "make it platform-independent again" is asking the wrong question. Really, your question should be: can a fix for a serious bug be backported to JDK 8 after it is fixed in JDK 9. The answer to that question is "yes" for serious bugs and regressions. What you have discovered in this case is a serious bug that happens to affect a single platform. In fact, my reading of the bug is that we are just getting lucky on the other platforms. If this turns out to be as serious as it seems, then I will bump the priority to P2 and we will consider a backport to a JDK 8 update release. -- Kevin Stefan Endrullis wrote: > Dear JavaFX team, > > over years one of the key features of Java was its platform > independence. A Java application would run under Windows, Mac OS, and > Linux (if well programmed). > > Since https://bugs.openjdk.java.net/browse/JDK-8146325 this is no > longer the case. Once you use the JavaFX Spinner component > your application will still work under Windows, but will crash under > Linux. > > Since this bug attacks a fundamental feature of Java we expected it to > be fixed quite fast and definitely in Java 8. But now we discover > that it's planned to be fixed in Java 9 only. > Does this mean that Java 8 is not considered to be platform > independent anymore? Do we have to start deploying different jars for > different platforms now? > > Best regards, > Stefan Endrullis > From tom.schindl at bestsolution.at Wed Feb 17 18:30:00 2016 From: tom.schindl at bestsolution.at (Tom Schindl) Date: Wed, 17 Feb 2016 19:30:00 +0100 Subject: plans to make JavaFX 8 platform independent again? In-Reply-To: <56C4AE4A.9010708@oracle.com> References: <56C4ABAC.3090304@endrullis.de> <56C4AE4A.9010708@oracle.com> Message-ID: <56C4BC28.8010805@bestsolution.at> Hi, In general I think this whole Spinner thing is completely bogus!!!! Suppose the following: > Spinner s = new Spinner<>(0.0, 1.0, 0.0); > s.valueProperty().addListener( new ChangeListener() { > > @Override > public void changed(ObservableValue observable, Integer oldValue, Integer newValue) { > System.err.println("HELLO WORLD"); > } > }); > s.increment(); This will naturally give you a CCE. Those constructurs should have never ever be supplied but what should have be provided is Spinner.createDouble( double, double, double ) : Spinner; Spinner.createInt( int, int, int ); I have not tried but the work around is to explicitly public Spinner(@NamedArg("valueFactory") SpinnerValueFactory valueFactory)! a) You need your own SpinnerValueFactory because one can not reference inner classes in FXML > package application; > > import javafx.beans.NamedArg; > import javafx.scene.control.SpinnerValueFactory.IntegerSpinnerValueFactory; > > public class MyWrapperFactory extends IntegerSpinnerValueFactory { > > public MyWrapperFactory(@NamedArg("min") int min, > @NamedArg("max") int max, > @NamedArg("initialValue") int initialValue) { > super(min, max, initialValue); > } > > } b) make your FXML look like this So IMHO action items are: * deprecate those constructors * provide static factory methods The order in which constructors are provided by reflection is not guaranteed and BTW you can make your sample break on windows. Change Spinner to Spinner! Tom On 17.02.16 18:30, Kevin Rushforth wrote: > Hi Stefan, > > Java and JavaFX are platform-independent, so asking whether we will > "make it platform-independent again" is asking the wrong question. > Really, your question should be: can a fix for a serious bug be > backported to JDK 8 after it is fixed in JDK 9. The answer to that > question is "yes" for serious bugs and regressions. > > What you have discovered in this case is a serious bug that happens to > affect a single platform. In fact, my reading of the bug is that we are > just getting lucky on the other platforms. If this turns out to be as > serious as it seems, then I will bump the priority to P2 and we will > consider a backport to a JDK 8 update release. > > -- Kevin > > > Stefan Endrullis wrote: >> Dear JavaFX team, >> >> over years one of the key features of Java was its platform >> independence. A Java application would run under Windows, Mac OS, and >> Linux (if well programmed). >> >> Since https://bugs.openjdk.java.net/browse/JDK-8146325 this is no >> longer the case. Once you use the JavaFX Spinner component >> your application will still work under Windows, but will crash under >> Linux. >> >> Since this bug attacks a fundamental feature of Java we expected it to >> be fixed quite fast and definitely in Java 8. But now we discover >> that it's planned to be fixed in Java 9 only. >> Does this mean that Java 8 is not considered to be platform >> independent anymore? Do we have to start deploying different jars for >> different platforms now? >> >> Best regards, >> Stefan Endrullis >> -- Thomas Schindl, CTO BestSolution.at EDV Systemhaus GmbH Eduard-Bodem-Gasse 5-7, A-6020 Innsbruck http://www.bestsolution.at/ Reg. Nr. FN 222302s am Firmenbuchgericht Innsbruck From james.graham at oracle.com Wed Feb 17 20:05:04 2016 From: james.graham at oracle.com (Jim Graham) Date: Wed, 17 Feb 2016 12:05:04 -0800 Subject: [Review request] 8088853: Applying dashed border to separator makes whole application hang In-Reply-To: <56C43955.7050209@oracle.com> References: <5695316A.7070902@oracle.com> <56953A82.7020901@oracle.com> <56955219.8070200@oracle.com> <56C1AD80.6010501@oracle.com> <56C3A139.6070702@oracle.com> <56C43955.7050209@oracle.com> Message-ID: <56C4D270.7000205@oracle.com> Looks great. Approved... ...jim On 2/17/2016 1:11 AM, Andrey Rusakov wrote: > Updated that: > http://cr.openjdk.java.net/~arusakov/8088853/webrev.01 > > 17.02.2016 01:22, Jim Graham ?????: >> [I believe you sent this to the wrong mailing list - the "-request" >> list is for changing your membership to the mailing list, not for >> sending mail to the list itself. I fixed it here in my reply...] >> >> That looks fine. I'll note that the "dashCumulative" variable does >> not need to be computed if you don't recompute the gapLength at line >> 1580, so that line (#1578) can be moved inside the if statement. >> >> Other than that, it looks good... >> >> ...jim >> >> On 2/15/2016 2:50 AM, Andrey Rusakov wrote: >>> Hello, everyone! Could you look at my fix for JDK-8147944? >>> http://cr.openjdk.java.net/~arusakov/8088853/webrev.00 > From james.graham at oracle.com Wed Feb 17 20:07:32 2016 From: james.graham at oracle.com (Jim Graham) Date: Wed, 17 Feb 2016 12:07:32 -0800 Subject: [9] review request: 8149967: Cannot compile JFXPanel with JDK 9: SurfaceData::getDefaultScale not found In-Reply-To: <56C4893F.4090305@oracle.com> References: <56C3B550.4000705@oracle.com> <56C3B593.9090502@oracle.com> <56C3B68D.5070301@oracle.com> <56C47307.2050109@oracle.com> <56C4893F.4090305@oracle.com> Message-ID: <56C4D304.7070509@oracle.com> I think what Sergey was getting at is that in the short term you could use GC.getDefaultTransform() without any reflection as a workaround, but if you've already done the reflection work and it's going away shortly it doesn't really matter. In the end you would want to use the getScaleXY() methods anyway as that avoids having to construct a transform as in the getDefaultTX() case... ...jim On 2/17/2016 6:52 AM, Kevin Rushforth wrote: > Thanks, Sergey. > > I will file a follow-up issue to remove the reflection code and provide > a suitable replacement. > > -- Kevin > > > Sergey Bylokhov wrote: >> Note that in jdk9 the same data can be obtained via >> GraphicsConfiguration.getDefaultTransform(); >> >> On 17.02.16 2:53, Jim Graham wrote: >>> I added a comment on the bug about BC, but it sounds like you already >>> considered it. I'm fine with this as is, but would push for moving to >>> JDK9 ASAP... >>> >>> ...jim >>> >>> On 2/16/2016 3:49 PM, Kevin Rushforth wrote: >>>> [resend with correct subject line] >>>> >>>> Jim and Alexander, >>>> >>>> Please review the following fix to allow JFXPanel to compile (and run) >>>> again on JDK 9. >>>> >>>> https://bugs.openjdk.java.net/browse/JDK-8149967 >>>> http://cr.openjdk.java.net/~kcr/8149967/webrev.00/ >>>> >>>> Note that I did not provide a fallback to the existing JDK 8 method, >>>> since we are going to require JDK 9 soon anyway. >>>> >>>> Note also that there is still one more bug fix needed before we can >>>> compile everything with JDK 9, so this is necessary but not sufficient. >>>> >>>> -- Kevin >>>> >> >> From kevin.rushforth at oracle.com Wed Feb 17 20:51:28 2016 From: kevin.rushforth at oracle.com (Kevin Rushforth) Date: Wed, 17 Feb 2016 12:51:28 -0800 Subject: [9] review request: 8149967: Cannot compile JFXPanel with JDK 9: SurfaceData::getDefaultScale not found In-Reply-To: <56C4D304.7070509@oracle.com> References: <56C3B550.4000705@oracle.com> <56C3B593.9090502@oracle.com> <56C3B68D.5070301@oracle.com> <56C47307.2050109@oracle.com> <56C4893F.4090305@oracle.com> <56C4D304.7070509@oracle.com> Message-ID: <56C4DD50.9030106@oracle.com> Ah, I see. I missed that point. -- Kevin Jim Graham wrote: > I think what Sergey was getting at is that in the short term you could > use GC.getDefaultTransform() without any reflection as a workaround, > but if you've already done the reflection work and it's going away > shortly it doesn't really matter. > > In the end you would want to use the getScaleXY() methods anyway as > that avoids having to construct a transform as in the getDefaultTX() > case... > > ...jim > > On 2/17/2016 6:52 AM, Kevin Rushforth wrote: >> Thanks, Sergey. >> >> I will file a follow-up issue to remove the reflection code and provide >> a suitable replacement. >> >> -- Kevin >> >> >> Sergey Bylokhov wrote: >>> Note that in jdk9 the same data can be obtained via >>> GraphicsConfiguration.getDefaultTransform(); >>> >>> On 17.02.16 2:53, Jim Graham wrote: >>>> I added a comment on the bug about BC, but it sounds like you already >>>> considered it. I'm fine with this as is, but would push for moving to >>>> JDK9 ASAP... >>>> >>>> ...jim >>>> >>>> On 2/16/2016 3:49 PM, Kevin Rushforth wrote: >>>>> [resend with correct subject line] >>>>> >>>>> Jim and Alexander, >>>>> >>>>> Please review the following fix to allow JFXPanel to compile (and >>>>> run) >>>>> again on JDK 9. >>>>> >>>>> https://bugs.openjdk.java.net/browse/JDK-8149967 >>>>> http://cr.openjdk.java.net/~kcr/8149967/webrev.00/ >>>>> >>>>> Note that I did not provide a fallback to the existing JDK 8 method, >>>>> since we are going to require JDK 9 soon anyway. >>>>> >>>>> Note also that there is still one more bug fix needed before we can >>>>> compile everything with JDK 9, so this is necessary but not >>>>> sufficient. >>>>> >>>>> -- Kevin >>>>> >>> >>> From kevin.rushforth at oracle.com Thu Feb 18 01:19:38 2016 From: kevin.rushforth at oracle.com (Kevin Rushforth) Date: Wed, 17 Feb 2016 17:19:38 -0800 Subject: [9] review request: 8134709 Message-ID: <56C51C2A.9080004@oracle.com> Sergey & Alexander, Please review the following, which will allow the FX sdk to build with JDK 9. https://bugs.openjdk.java.net/browse/JDK-8134709 http://cr.openjdk.java.net/~kcr/8150109/webrev.00/ The premise of the fix, which just comments out the calls to the removed methods, is that since the existing FX / Swing Drag & Drop functionality has been broken for all users of JDK 9 ea for the last several months, we can live with it broken for a little while longer; I doubt any FX developer who is current testing it with JDK 8u as a boot JDK and their own build of FX will notice. I will file a follow-on JIRA to fix it after we move to JDK 9 as a boot JDK. I didn't think it was worth putting in reflection code for this case, but if you feel otherwise, then let me know. -- Kevin From kevin.rushforth at oracle.com Thu Feb 18 01:22:31 2016 From: kevin.rushforth at oracle.com (Kevin Rushforth) Date: Wed, 17 Feb 2016 17:22:31 -0800 Subject: [9] review request: 8134709: Cannot compile FXDnD with JDK 9: DropTargetContext::addNotify, removeNotify not found In-Reply-To: <56C51C2A.9080004@oracle.com> References: <56C51C2A.9080004@oracle.com> Message-ID: <56C51CD7.4050603@oracle.com> [fixed cut-and-paste error in the URL of the webrev and added bug description to subject line] Sergey & Alexander, Please review the following, which will allow the FX sdk to build with JDK 9. https://bugs.openjdk.java.net/browse/JDK-8134709 http://cr.openjdk.java.net/~kcr/8134709/webrev.00/ The premise of the fix, which just comments out the calls to the removed methods, is that since the existing FX / Swing Drag & Drop functionality has been broken for all users of JDK 9 ea for the last several months, we can live with it broken for a little while longer; I doubt any FX developer who is current testing it with JDK 8u as a boot JDK and their own build of FX will notice. I will file a follow-on JIRA to fix it after we move to JDK 9 as a boot JDK. I didn't think it was worth putting in reflection code for this case, but if you feel otherwise, then let me know. -- Kevin From kevin.rushforth at oracle.com Thu Feb 18 01:32:37 2016 From: kevin.rushforth at oracle.com (Kevin Rushforth) Date: Wed, 17 Feb 2016 17:32:37 -0800 Subject: [9] review request: 8150109: Cannot build FX apps or tests with JDK 9 Message-ID: <56C51F35.2060202@oracle.com> Chien & Dave, Please review the following webrev to fix "gradle apps" and "gradle test" so they can compile when using JDK 9 as the boot JDK. https://bugs.openjdk.java.net/browse/JDK-8150109 http://cr.openjdk.java.net/~kcr/8150109/webrev.00/ Most of these are a result of old NB-generated build.xml files that won't work with the JDK 9 layout (e.g., it thinks it needs tools.jar which no longer exists). I regenerated the NB projects and it should now build fine with either JDK 8 or JDK 9 (please test if you can). -- Kevin From steve at winnall.ch Thu Feb 18 14:38:25 2016 From: steve at winnall.ch (Stephen Winnall) Date: Thu, 18 Feb 2016 15:38:25 +0100 Subject: JFX as an OSGi service? Message-ID: <4C4D64B8-8432-47A2-998C-C2E0B199F2F6@winnall.ch> I am trying to make JavaFX 8 work with OSGi Declarative Services. My preferred solution would be to instantiate javafx.application.Application as an OSGi service. As I understand it, there are two ways of activating JavaFX: 1) sub-class javafx.application.Application or 2) call javafx.application.Application.launch() However, both of these approaches give me a POJO, which makes interaction with OSGi services and bundles very difficult. Is there a ?proper? way of starting JavaFX as an OSGi service? If not, are there any plans to support this? Regards, Steve From chris.bensen at oracle.com Thu Feb 18 15:21:21 2016 From: chris.bensen at oracle.com (Chris Bensen) Date: Thu, 18 Feb 2016 07:21:21 -0800 Subject: Review Request: 8149966 [packager] JLINK API changes Message-ID: Hi Kevin, Please review this fix for the changes to the JLINK API that the packager uses: JIRA: https://bugs.openjdk.java.net/browse/JDK-8149966 Webrev: http://cr.openjdk.java.net/~cbensen/JDK-8149966/webrev.00/ Thanks, Chris From derijcke.erik at gmail.com Thu Feb 18 16:40:39 2016 From: derijcke.erik at gmail.com (Erik De Rijcke) Date: Thu, 18 Feb 2016 17:40:39 +0100 Subject: JFX as an OSGi service? In-Reply-To: <4C4D64B8-8432-47A2-998C-C2E0B199F2F6@winnall.ch> References: <4C4D64B8-8432-47A2-998C-C2E0B199F2F6@winnall.ch> Message-ID: Hi Stephen, We use JavaFX in an OSGi container, as a service component, in production, so it's perfectly possible. However there are a few gotcha's you need to take into account (I can not c/p the code for obvious reasons...) which makes using it in osgi... quite horrible :) When triggering a javafx application in say, your component activate method (as we do), you're actually creating a new javafx application instance, a whole new identical object but without any scr dependency injection. This is problematic as your osgi object has all the dependencies injected from the osgi container while the javafx object does not. What we do is this: in our activate we copy all our osgi dependencies, as well as our ourself (this) to static fields, this makes them accessible in the start method of the javafx object. When start is called, we store the javafx object in a static field (which we access by calling 'this' in the start method). We now have access to all dependencies and both objects at any time. Now it's just matter of delegating calls from one instance to another if needed... btw, don't forget to call launch in a separate thread in your activate, else you'll block your bundle activator thread indefinitely oh *and* sync (block) your osgi component activate until the start method of your javafx has finished else your component will announce itself activated while javafx is still busy initializing. Oh another gotcha, try to avoid using Platform.runLater, as that will only work *after* your application component was activated, instead make a non static runLater method in your osgi javafx application component and use that. That will ensure that javafx was initialized before invoking any platform run later. Unfortunately javafx has a lot of static { Platform.RunLater} calls spread out in different classes, so don't try to load those classes before your javafx application was started... OUCH! Didn't I say it was hairy and messy? JavaFX and OSGi is quite a bad match unfortunately. On Thu, Feb 18, 2016 at 3:38 PM, Stephen Winnall wrote: > I am trying to make JavaFX 8 work with OSGi Declarative Services. My > preferred solution would be to instantiate javafx.application.Application > as an OSGi service. > > As I understand it, there are two ways of activating JavaFX: > > 1) sub-class javafx.application.Application or > 2) call javafx.application.Application.launch() > > However, both of these approaches give me a POJO, which makes interaction > with OSGi services and bundles very difficult. > > Is there a ?proper? way of starting JavaFX as an OSGi service? If not, are > there any plans to support this? > > Regards, > Steve From steve at winnall.ch Thu Feb 18 17:33:37 2016 From: steve at winnall.ch (Stephen Winnall) Date: Thu, 18 Feb 2016 18:33:37 +0100 Subject: JFX as an OSGi service? In-Reply-To: References: <4C4D64B8-8432-47A2-998C-C2E0B199F2F6@winnall.ch> Message-ID: <47B876AF-93CE-45B3-AC0D-967F4B080F08@winnall.ch> Hi Erik Thanks for this - it makes sense. I was wondering about 1) getting the sub-class of javafx.application.Application to register itself at runtime as an OSGi service; or 2) trying to create a ServiceFactory that creates an instance of javafx.application.Application (perhaps decorated or proxied); or 3) cloning javafx.application.Application and making a version compatible with declarative services. Your approach is no. 4 and has the advantage that it is known to work! It seems a pity that JavaFX has such a closed/proprietary approach to starting a javafx.application.Application. Cheers, Steve > On 18 Feb 2016, at 17:40, Erik De Rijcke wrote: > > Hi Stephen, > > We use JavaFX in an OSGi container, as a service component, in production, so it's perfectly possible. > > However there are a few gotcha's you need to take into account (I can not c/p the code for obvious reasons...) which makes using it in osgi... quite horrible :) > > When triggering a javafx application in say, your component activate method (as we do), you're actually creating a new javafx application instance, a whole new identical object but without any scr dependency injection. > > This is problematic as your osgi object has all the dependencies injected from the osgi container while the javafx object does not. > > What we do is this: in our activate we copy all our osgi dependencies, as well as our ourself (this) to static fields, this makes them accessible in the start method of the javafx object. When start is called, we store the javafx object in a static field (which we access by calling 'this' in the start method). We now have access to all dependencies and both objects at any time. Now it's just matter of delegating calls from one instance to another if needed... > > btw, don't forget to call launch in a separate thread in your activate, else you'll block your bundle activator thread indefinitely oh *and* sync (block) your osgi component activate until the start method of your javafx has finished else your component will announce itself activated while javafx is still busy initializing. > > Oh another gotcha, try to avoid using Platform.runLater, as that will only work *after* your application component was activated, instead make a non static runLater method in your osgi javafx application component and use that. That will ensure that javafx was initialized before invoking any platform run later. > > Unfortunately javafx has a lot of static { Platform.RunLater} calls spread out in different classes, so don't try to load those classes before your javafx application was started... OUCH! > > Didn't I say it was hairy and messy? JavaFX and OSGi is quite a bad match unfortunately. > > On Thu, Feb 18, 2016 at 3:38 PM, Stephen Winnall > wrote: > I am trying to make JavaFX 8 work with OSGi Declarative Services. My preferred solution would be to instantiate javafx.application.Application as an OSGi service. > > As I understand it, there are two ways of activating JavaFX: > > 1) sub-class javafx.application.Application or > 2) call javafx.application.Application.launch() > > However, both of these approaches give me a POJO, which makes interaction with OSGi services and bundles very difficult. > > Is there a ?proper? way of starting JavaFX as an OSGi service? If not, are there any plans to support this? > > Regards, > Steve > From alexander.matveev at oracle.com Fri Feb 19 01:37:04 2016 From: alexander.matveev at oracle.com (Alexander Matveev) Date: Thu, 18 Feb 2016 17:37:04 -0800 Subject: [8u, 9] Review request for 8136920: Provide media support for libav version 55 and 56 Message-ID: <56C671C0.6070708@oracle.com> Hi Kevin and Kirill, Please review the following: https://bugs.openjdk.java.net/browse/JDK-8136920 http://cr.openjdk.java.net/~almatvee/8136920/webrev.9.00/ 8u backport: http://cr.openjdk.java.net/~almatvee/8136920/webrev.8u.00/ Added support for libavcodec55, libavcodec56 and libavcodec-ffmpeg56. Thanks, Alexander From mark.reinhold at oracle.com Fri Feb 19 01:41:48 2016 From: mark.reinhold at oracle.com (mark.reinhold at oracle.com) Date: Thu, 18 Feb 2016 17:41:48 -0800 (PST) Subject: JEP 283: Enable GTK 3 on Linux Message-ID: <20160219014148.103A499C4F@eggemoggin.niobe.net> New JEP Candidate: http://openjdk.java.net/jeps/283 - Mark From powers.anirvan at gmail.com Fri Feb 19 11:52:15 2016 From: powers.anirvan at gmail.com (Anirvan Sarkar) Date: Fri, 19 Feb 2016 17:22:15 +0530 Subject: JFX as an OSGi service? In-Reply-To: <4C4D64B8-8432-47A2-998C-C2E0B199F2F6@winnall.ch> References: <4C4D64B8-8432-47A2-998C-C2E0B199F2F6@winnall.ch> Message-ID: Hi Stephen, FYI, there is another way of initializing JavaFX runtime. Just use: new JFXPanel(); It is documented[1] that FX runtime is initialized when the first JFXPanel instance is constructed. Also JavaFX 9 will provide an official API to start the FX platform [2] [3]. [1] https://docs.oracle.com/javase/8/javafx/api/javafx/application/Platform.html#runLater-java.lang.Runnable- [2] https://bugs.openjdk.java.net/browse/JDK-8090585 [3] http://download.java.net/jdk9/jfxdocs/javafx/application/Platform.html#startup-java.lang.Runnable- On 18 February 2016 at 20:08, Stephen Winnall wrote: > As I understand it, there are two ways of activating JavaFX: > > 1) sub-class javafx.application.Application or > 2) call javafx.application.Application.launch() > -- Anirvan From powers.anirvan at gmail.com Fri Feb 19 12:22:19 2016 From: powers.anirvan at gmail.com (Anirvan Sarkar) Date: Fri, 19 Feb 2016 17:52:19 +0530 Subject: JEP 283: Enable GTK 3 on Linux In-Reply-To: <20160219014148.103A499C4F@eggemoggin.niobe.net> References: <20160219014148.103A499C4F@eggemoggin.niobe.net> Message-ID: Hi, One of the sub-task of this JEP is to 'Rework Swing GTK LnF to support GTK-3'. This seems something in common with another submitted JEP [1]: 'Modernize the GTK3 Look and Feel implementation'. So will these two JEP complement each other or will the other one be now redundant ? [1] https://bugs.openjdk.java.net/browse/JDK-8065658 On 19 February 2016 at 07:11, wrote: > New JEP Candidate: http://openjdk.java.net/jeps/283 > > - Mark > -- Anirvan From info at cuhka.com Fri Feb 19 13:30:59 2016 From: info at cuhka.com (Maurice) Date: Fri, 19 Feb 2016 14:30:59 +0100 Subject: NPE in PrismFontLoader.java: Loading primary font factory failed Message-ID: <56C71913.7080502@cuhka.com> I'm building a Yocto Embedded Linux image for the ARM based Udoo Board Quad. At the moment the build is good enough that JavaFX seems to see the Vivante GPU, but my small test program fails with a NullPointerException: at com.sun.javafx.font.PrismFontLoader.font(PrismFontLoader.java:172) at javafx.scene.text.Font.font(Font.java:148) at javafx.scene.text.Font.font(Font.java:228) at com.cuhka.Sample.start(Sample.java:18) I tried several steps from the OpenJFX Font Setup page, I checked the presence of the ${java.home}/lib/fonts folder and it does exist. Running the program with -Dprism.debugfonts=true shows some error: Loading FontFactory com.sun.javafx.font.freetype.FTFactory Subpixel: enabled Loading font factory failed com.sun.javafx.font.freetype.FTFactory Loading font factory failed com.sun.javafx.font.t2k.T2KFactory *** Loading primary font factory failed. *** *** Fallbacking to com.sun.javafx.font.t2k.T2KFactory *** What should be added to the platform for this to be fixed? Maurice. From vadim.pakhnushev at oracle.com Fri Feb 19 14:30:17 2016 From: vadim.pakhnushev at oracle.com (Vadim Pakhnushev) Date: Fri, 19 Feb 2016 17:30:17 +0300 Subject: In(Sanity) Testing Mondays Message-ID: <56C726F9.8000409@oracle.com> Reminder, Monday is our weekly sanity testing. You can find your testing assignment at: https://wiki.openjdk.java.net/display/OpenJFX/Sanity+Testing Also please remember that the repo will be locked from 1am PST until 1pm PST. Happy testing! Thanks, Vadim From kevin.rushforth at oracle.com Fri Feb 19 15:41:45 2016 From: kevin.rushforth at oracle.com (Kevin Rushforth) Date: Fri, 19 Feb 2016 07:41:45 -0800 Subject: JFX as an OSGi service? In-Reply-To: References: <4C4D64B8-8432-47A2-998C-C2E0B199F2F6@winnall.ch> Message-ID: <56C737B9.6000506@oracle.com> And for JDK 9 there is now: Platform.startup(Runnable); -- Kevin Anirvan Sarkar wrote: > Hi Stephen, > > FYI, there is another way of initializing JavaFX runtime. Just use: > > new JFXPanel(); > > It is documented[1] that FX runtime is initialized when the first JFXPanel > instance is constructed. > > Also JavaFX 9 will provide an official API to start the FX platform [2] [3]. > > > [1] > https://docs.oracle.com/javase/8/javafx/api/javafx/application/Platform.html#runLater-java.lang.Runnable- > [2] https://bugs.openjdk.java.net/browse/JDK-8090585 > [3] > http://download.java.net/jdk9/jfxdocs/javafx/application/Platform.html#startup-java.lang.Runnable- > > > On 18 February 2016 at 20:08, Stephen Winnall wrote: > > >> As I understand it, there are two ways of activating JavaFX: >> >> 1) sub-class javafx.application.Application or >> 2) call javafx.application.Application.launch() >> >> > > > > From kevin.rushforth at oracle.com Fri Feb 19 15:43:29 2016 From: kevin.rushforth at oracle.com (Kevin Rushforth) Date: Fri, 19 Feb 2016 07:43:29 -0800 Subject: JEP 283: Enable GTK 3 on Linux In-Reply-To: References: <20160219014148.103A499C4F@eggemoggin.niobe.net> Message-ID: <56C73821.7030808@oracle.com> Current plan is to track all of the work for both JavaFX and Swing with this JEP. -- Kevin Anirvan Sarkar wrote: > Hi, > > One of the sub-task of this JEP is to 'Rework Swing GTK LnF to support > GTK-3'. > This seems something in common with another submitted JEP [1]: 'Modernize > the GTK3 Look and Feel implementation'. > > So will these two JEP complement each other or will the other one be now > redundant ? > > > [1] https://bugs.openjdk.java.net/browse/JDK-8065658 > > On 19 February 2016 at 07:11, wrote: > > >> New JEP Candidate: http://openjdk.java.net/jeps/283 >> >> - Mark >> >> > > > > From kevin.rushforth at oracle.com Fri Feb 19 15:49:50 2016 From: kevin.rushforth at oracle.com (Kevin Rushforth) Date: Fri, 19 Feb 2016 07:49:50 -0800 Subject: NPE in PrismFontLoader.java: Loading primary font factory failed In-Reply-To: <56C71913.7080502@cuhka.com> References: <56C71913.7080502@cuhka.com> Message-ID: <56C7399E.6010006@oracle.com> Do you have the pango and freetype libraries installed on your platform? One thing to check is whether any dependent libraries are missing for the following .so files: ldd libjavafx_font.so ldd libjavafx_font_freetype.so ldd libjavafx_font_pango.so -- Kevin Maurice wrote: > I'm building a Yocto Embedded Linux image for the ARM based Udoo Board > Quad. At the moment the build is good enough that JavaFX seems to see > the Vivante GPU, but my small test program fails with a > NullPointerException: > at com.sun.javafx.font.PrismFontLoader.font(PrismFontLoader.java:172) > at javafx.scene.text.Font.font(Font.java:148) > at javafx.scene.text.Font.font(Font.java:228) > at com.cuhka.Sample.start(Sample.java:18) > > I tried several steps from the OpenJFX Font Setup > page, I > checked the presence of the ${java.home}/lib/fonts folder and it does > exist. Running the program with -Dprism.debugfonts=true shows some error: > > Loading FontFactory com.sun.javafx.font.freetype.FTFactory > Subpixel: enabled > Loading font factory failed com.sun.javafx.font.freetype.FTFactory > Loading font factory failed com.sun.javafx.font.t2k.T2KFactory > *** Loading primary font factory failed. *** > *** Fallbacking to com.sun.javafx.font.t2k.T2KFactory *** > > What should be added to the platform for this to be fixed? > > Maurice. > From kevin.rushforth at oracle.com Fri Feb 19 15:54:03 2016 From: kevin.rushforth at oracle.com (Kevin Rushforth) Date: Fri, 19 Feb 2016 07:54:03 -0800 Subject: NPE in PrismFontLoader.java: Loading primary font factory failed In-Reply-To: <56C7399E.6010006@oracle.com> References: <56C71913.7080502@cuhka.com> <56C7399E.6010006@oracle.com> Message-ID: <56C73A9B.9070003@oracle.com> Another thing that might help diagnose which library has the problem is to run with "java -Djavafx.verbose=true ..." -- that option will print each native library as it is being loaded and print the exception message if one fails. -- Kevin Kevin Rushforth wrote: > Do you have the pango and freetype libraries installed on your > platform? One thing to check is whether any dependent libraries are > missing for the following .so files: > > ldd libjavafx_font.so > ldd libjavafx_font_freetype.so > ldd libjavafx_font_pango.so > > -- Kevin > > > Maurice wrote: >> I'm building a Yocto Embedded Linux image for the ARM based Udoo >> Board Quad. At the moment the build is good enough that JavaFX seems >> to see the Vivante GPU, but my small test program fails with a >> NullPointerException: >> at >> com.sun.javafx.font.PrismFontLoader.font(PrismFontLoader.java:172) >> at javafx.scene.text.Font.font(Font.java:148) >> at javafx.scene.text.Font.font(Font.java:228) >> at com.cuhka.Sample.start(Sample.java:18) >> >> I tried several steps from the OpenJFX Font Setup >> page, I >> checked the presence of the ${java.home}/lib/fonts folder and it does >> exist. Running the program with -Dprism.debugfonts=true shows some >> error: >> >> Loading FontFactory com.sun.javafx.font.freetype.FTFactory >> Subpixel: enabled >> Loading font factory failed com.sun.javafx.font.freetype.FTFactory >> Loading font factory failed com.sun.javafx.font.t2k.T2KFactory >> *** Loading primary font factory failed. *** >> *** Fallbacking to com.sun.javafx.font.t2k.T2KFactory *** >> >> What should be added to the platform for this to be fixed? >> >> Maurice. >> From info at cuhka.com Fri Feb 19 15:55:40 2016 From: info at cuhka.com (Maurice) Date: Fri, 19 Feb 2016 16:55:40 +0100 Subject: NPE in PrismFontLoader.java: Loading primary font factory failed In-Reply-To: <56C7399E.6010006@oracle.com> References: <56C71913.7080502@cuhka.com> <56C7399E.6010006@oracle.com> Message-ID: <56C73AFC.90306@cuhka.com> Kevin, Yes, in lib/arm these libraries are present. I'm using the Oracle ARM JDK 1.8.0_33 fwiw. On the default ubuntu based image I can run JavaFX with this Java setup, but without HW acceleration. Maurice. root at udooqdl:/# find / -name "*javafx_font*.so" /opt/jdk1.8.0_33/lib/arm/libjavafx_font_freetype.so /opt/jdk1.8.0_33/lib/arm/libjavafx_font_pango.so /opt/jdk1.8.0_33/lib/arm/libjavafx_font.so /opt/jdk1.8.0_33/jre/lib/arm/libjavafx_font_freetype.so /opt/jdk1.8.0_33/jre/lib/arm/libjavafx_font_pango.so /opt/jdk1.8.0_33/jre/lib/arm/libjavafx_font.so Op 19-02-16 om 16:49 schreef Kevin Rushforth: > Do you have the pango and freetype libraries installed on your > platform? One thing to check is whether any dependent libraries are > missing for the following .so files: > > ldd libjavafx_font.so > ldd libjavafx_font_freetype.so > ldd libjavafx_font_pango.so > > -- Kevin > > > Maurice wrote: >> I'm building a Yocto Embedded Linux image for the ARM based Udoo >> Board Quad. At the moment the build is good enough that JavaFX seems >> to see the Vivante GPU, but my small test program fails with a >> NullPointerException: >> at >> com.sun.javafx.font.PrismFontLoader.font(PrismFontLoader.java:172) >> at javafx.scene.text.Font.font(Font.java:148) >> at javafx.scene.text.Font.font(Font.java:228) >> at com.cuhka.Sample.start(Sample.java:18) >> >> I tried several steps from the OpenJFX Font Setup >> page, I >> checked the presence of the ${java.home}/lib/fonts folder and it does >> exist. Running the program with -Dprism.debugfonts=true shows some >> error: >> >> Loading FontFactory com.sun.javafx.font.freetype.FTFactory >> Subpixel: enabled >> Loading font factory failed com.sun.javafx.font.freetype.FTFactory >> Loading font factory failed com.sun.javafx.font.t2k.T2KFactory >> *** Loading primary font factory failed. *** >> *** Fallbacking to com.sun.javafx.font.t2k.T2KFactory *** >> >> What should be added to the platform for this to be fixed? >> >> Maurice. >> From kevin.rushforth at oracle.com Fri Feb 19 16:00:41 2016 From: kevin.rushforth at oracle.com (Kevin Rushforth) Date: Fri, 19 Feb 2016 08:00:41 -0800 Subject: NPE in PrismFontLoader.java: Loading primary font factory failed In-Reply-To: <56C73AFC.90306@cuhka.com> References: <56C71913.7080502@cuhka.com> <56C7399E.6010006@oracle.com> <56C73AFC.90306@cuhka.com> Message-ID: <56C73C29.1030108@oracle.com> What I meant was for you to find out whether the system pango library that javafx_font_pango.so depends upon is present. Run the "ldd" commands and make sure there are no missing dependencies. Also, I hadn't noticed you were trying to use the ARM bits. Maybe Dave Hill has some additional thoughts on this. -- Kevin Maurice wrote: > Kevin, > > Yes, in lib/arm these libraries are present. I'm using the Oracle ARM > JDK 1.8.0_33 fwiw. On the default ubuntu based image I can run JavaFX > with this Java setup, but without HW acceleration. > > Maurice. > > root at udooqdl:/# find / -name "*javafx_font*.so" > /opt/jdk1.8.0_33/lib/arm/libjavafx_font_freetype.so > /opt/jdk1.8.0_33/lib/arm/libjavafx_font_pango.so > /opt/jdk1.8.0_33/lib/arm/libjavafx_font.so > /opt/jdk1.8.0_33/jre/lib/arm/libjavafx_font_freetype.so > /opt/jdk1.8.0_33/jre/lib/arm/libjavafx_font_pango.so > /opt/jdk1.8.0_33/jre/lib/arm/libjavafx_font.so > > > Op 19-02-16 om 16:49 schreef Kevin Rushforth: >> Do you have the pango and freetype libraries installed on your >> platform? One thing to check is whether any dependent libraries are >> missing for the following .so files: >> >> ldd libjavafx_font.so >> ldd libjavafx_font_freetype.so >> ldd libjavafx_font_pango.so >> >> -- Kevin >> >> >> Maurice wrote: >>> I'm building a Yocto Embedded Linux image for the ARM based Udoo >>> Board Quad. At the moment the build is good enough that JavaFX seems >>> to see the Vivante GPU, but my small test program fails with a >>> NullPointerException: >>> at >>> com.sun.javafx.font.PrismFontLoader.font(PrismFontLoader.java:172) >>> at javafx.scene.text.Font.font(Font.java:148) >>> at javafx.scene.text.Font.font(Font.java:228) >>> at com.cuhka.Sample.start(Sample.java:18) >>> >>> I tried several steps from the OpenJFX Font Setup >>> page, I >>> checked the presence of the ${java.home}/lib/fonts folder and it >>> does exist. Running the program with -Dprism.debugfonts=true shows >>> some error: >>> >>> Loading FontFactory com.sun.javafx.font.freetype.FTFactory >>> Subpixel: enabled >>> Loading font factory failed com.sun.javafx.font.freetype.FTFactory >>> Loading font factory failed com.sun.javafx.font.t2k.T2KFactory >>> *** Loading primary font factory failed. *** >>> *** Fallbacking to com.sun.javafx.font.t2k.T2KFactory *** >>> >>> What should be added to the platform for this to be fixed? >>> >>> Maurice. >>> > From info at cuhka.com Fri Feb 19 17:10:28 2016 From: info at cuhka.com (Maurice) Date: Fri, 19 Feb 2016 18:10:28 +0100 Subject: NPE in PrismFontLoader.java: Loading primary font factory failed In-Reply-To: <56C73C29.1030108@oracle.com> References: <56C71913.7080502@cuhka.com> <56C7399E.6010006@oracle.com> <56C73AFC.90306@cuhka.com> <56C73C29.1030108@oracle.com> Message-ID: <56C74C84.2000103@cuhka.com> It seems that pango isn't present on the system. Given that we have a fairly naked Yocto image, is there another way than trail and error to know all dependencies needed by Java and JavaFX? Maurice. Op 19-02-16 om 17:00 schreef Kevin Rushforth: > What I meant was for you to find out whether the system pango library > that javafx_font_pango.so depends upon is present. Run the "ldd" > commands and make sure there are no missing dependencies. > > Also, I hadn't noticed you were trying to use the ARM bits. Maybe Dave > Hill has some additional thoughts on this. > > -- Kevin > > > Maurice wrote: >> Kevin, >> >> Yes, in lib/arm these libraries are present. I'm using the Oracle ARM >> JDK 1.8.0_33 fwiw. On the default ubuntu based image I can run JavaFX >> with this Java setup, but without HW acceleration. >> >> Maurice. >> >> root at udooqdl:/# find / -name "*javafx_font*.so" >> /opt/jdk1.8.0_33/lib/arm/libjavafx_font_freetype.so >> /opt/jdk1.8.0_33/lib/arm/libjavafx_font_pango.so >> /opt/jdk1.8.0_33/lib/arm/libjavafx_font.so >> /opt/jdk1.8.0_33/jre/lib/arm/libjavafx_font_freetype.so >> /opt/jdk1.8.0_33/jre/lib/arm/libjavafx_font_pango.so >> /opt/jdk1.8.0_33/jre/lib/arm/libjavafx_font.so >> >> >> Op 19-02-16 om 16:49 schreef Kevin Rushforth: >>> Do you have the pango and freetype libraries installed on your >>> platform? One thing to check is whether any dependent libraries are >>> missing for the following .so files: >>> >>> ldd libjavafx_font.so >>> ldd libjavafx_font_freetype.so >>> ldd libjavafx_font_pango.so >>> >>> -- Kevin >>> >>> >>> Maurice wrote: >>>> I'm building a Yocto Embedded Linux image for the ARM based Udoo >>>> Board Quad. At the moment the build is good enough that JavaFX >>>> seems to see the Vivante GPU, but my small test program fails with >>>> a NullPointerException: >>>> at >>>> com.sun.javafx.font.PrismFontLoader.font(PrismFontLoader.java:172) >>>> at javafx.scene.text.Font.font(Font.java:148) >>>> at javafx.scene.text.Font.font(Font.java:228) >>>> at com.cuhka.Sample.start(Sample.java:18) >>>> >>>> I tried several steps from the OpenJFX Font Setup >>>> page, I >>>> checked the presence of the ${java.home}/lib/fonts folder and it >>>> does exist. Running the program with -Dprism.debugfonts=true shows >>>> some error: >>>> >>>> Loading FontFactory com.sun.javafx.font.freetype.FTFactory >>>> Subpixel: enabled >>>> Loading font factory failed com.sun.javafx.font.freetype.FTFactory >>>> Loading font factory failed com.sun.javafx.font.t2k.T2KFactory >>>> *** Loading primary font factory failed. *** >>>> *** Fallbacking to com.sun.javafx.font.t2k.T2KFactory *** >>>> >>>> What should be added to the platform for this to be fixed? >>>> >>>> Maurice. >>>> >> From philip.race at oracle.com Fri Feb 19 18:10:28 2016 From: philip.race at oracle.com (Phil Race) Date: Fri, 19 Feb 2016 10:10:28 -0800 Subject: JEP 283: Enable GTK 3 on Linux In-Reply-To: <56C73821.7030808@oracle.com> References: <20160219014148.103A499C4F@eggemoggin.niobe.net> <56C73821.7030808@oracle.com> Message-ID: <56C75A94.8040504@oracle.com> We had not forgotten that the other JEP was there (as a draft) but the new JEP started with a pure FX focus on allowing FX to use either GTK2 or GTK3 depending on what you needed. It was extended (feature creep) whilst being drafted to include doing the same for AWT/Swing but the focus was still on interoperability. Making the Swing L&F fully GTK3 based is the later stretch goal whereas the original JEP is much more focused on that and also not at all on FX. It would be good for Mario to take a look at the new JEP and identify any areas in which it falls short of the previous JEP, which would be one reason to leave the "old" JEP open for now. Another is that it is unclear how much of JEP 283 we will actually be able to deliver for JDK 9 and it is written in a way which is intended to allow for that. In which case the previous JEP may yet be needed to complete that work, so we don't know yet it if it will be completely subsumed by that work. -phil. On 02/19/2016 07:43 AM, Kevin Rushforth wrote: > Current plan is to track all of the work for both JavaFX and Swing > with this JEP. > > -- Kevin > > > Anirvan Sarkar wrote: >> Hi, >> >> One of the sub-task of this JEP is to 'Rework Swing GTK LnF to support >> GTK-3'. >> This seems something in common with another submitted JEP [1]: >> 'Modernize >> the GTK3 Look and Feel implementation'. >> >> So will these two JEP complement each other or will the other one be now >> redundant ? >> >> >> [1] https://bugs.openjdk.java.net/browse/JDK-8065658 >> >> On 19 February 2016 at 07:11, wrote: >> >>> New JEP Candidate: http://openjdk.java.net/jeps/283 >>> >>> - Mark >>> >> >> >> From chris.bensen at oracle.com Fri Feb 19 20:28:33 2016 From: chris.bensen at oracle.com (Chris Bensen) Date: Fri, 19 Feb 2016 12:28:33 -0800 Subject: Review Request: 8150294 [packager] Netbeans Packager Project Message-ID: <8F7FFB0C-9983-40DB-860F-0882A84B528C@oracle.com> Hi Kevin, Please review this change to add a Netbeans project for the Java Packager jdk.packager module: JIRA: https://bugs.openjdk.java.net/browse/JDK-8150294 Webrev: http://cr.openjdk.java.net/~cbensen/JDK-8150294/webrev.00 Thanks, Chris From steve at winnall.ch Sat Feb 20 00:28:07 2016 From: steve at winnall.ch (Stephen Winnall) Date: Sat, 20 Feb 2016 01:28:07 +0100 Subject: JFX as an OSGi service? In-Reply-To: <56C737B9.6000506@oracle.com> References: <4C4D64B8-8432-47A2-998C-C2E0B199F2F6@winnall.ch> <56C737B9.6000506@oracle.com> Message-ID: <51A9248B-7749-4A6E-BC3E-B36D7526FA0F@winnall.ch> Anirvan, Kevin Thanks for this. I?m an expert neither in JavaFX nor in OSGi, but I think the basis of the JavaFX/OSGi incompatibility is control. To work with OSGi, JavaFX has to relinquish control of its startup sequence to OSGi in such a way that javafx.application.Application (or its proxy) is instantiated by OSGi and submits to OSGi?s bundle/service lifecycle. AN OSGi expert can probably formulate this better? Platform.startup(runnable) /might/ do it. Platform.launch(class) doesn?t because the object thereby instantiated is always under the control of JavaFX - and thus not of OSGi. I?m not comfortable using JFXPanel: if I wanted to use Swing I wouldn?t be trying to use JavaFX. But thank you for the hint. Steve > On 19 Feb 2016, at 16:41, Kevin Rushforth wrote: > > And for JDK 9 there is now: > > Platform.startup(Runnable); > > -- Kevin > > > Anirvan Sarkar wrote: >> >> Hi Stephen, >> >> FYI, there is another way of initializing JavaFX runtime. Just use: >> >> new JFXPanel(); >> >> It is documented[1] that FX runtime is initialized when the first JFXPanel >> instance is constructed. >> >> Also JavaFX 9 will provide an official API to start the FX platform [2] [3]. >> >> >> [1] >> https://docs.oracle.com/javase/8/javafx/api/javafx/application/Platform.html#runLater-java.lang.Runnable - >> [2] https://bugs.openjdk.java.net/browse/JDK-8090585 >> [3] >> http://download.java.net/jdk9/jfxdocs/javafx/application/Platform.html#startup-java.lang.Runnable - >> >> >> On 18 February 2016 at 20:08, Stephen Winnall wrote: >> >> >>> As I understand it, there are two ways of activating JavaFX: >>> >>> 1) sub-class javafx.application.Application or >>> 2) call javafx.application.Application.launch() >>> >>> >> >> >> >> From info at cuhka.com Sat Feb 20 13:33:41 2016 From: info at cuhka.com (Maurice) Date: Sat, 20 Feb 2016 14:33:41 +0100 Subject: JFX as an OSGi service? In-Reply-To: <51A9248B-7749-4A6E-BC3E-B36D7526FA0F@winnall.ch> References: <4C4D64B8-8432-47A2-998C-C2E0B199F2F6@winnall.ch> <56C737B9.6000506@oracle.com> <51A9248B-7749-4A6E-BC3E-B36D7526FA0F@winnall.ch> Message-ID: <56C86B35.1010706@cuhka.com> For my OSGi based JavaFX solution on the Udoo Quad (ARM based Linux) I created a service that publishes the application in the context.The application does as little as possible. It sets up the primary stage as fullscreen and puts a stackpane in it. Initially the stackpane displays a 'boot logo', until the actual desktop bundle is started and registered with the application. Note that you have to start the application on a separate thread, as the thread will be blocked. On Java 8 this means that although the application bundle can't be updated in a running OSGi container, but that is why the desktop exists. On startup it registers itself, and thus the application content, with the application, and when it is stopped it removes the content from the application. The application has thus rarely to be updated itself. Regards, Maurice. public class UdooActivator implements BundleActivator { private static UdooActivator activator; private BundleContext context; static UdooActivator bundleActivator() { return requireNonNull(activator, "activator not set"); } @Override public void start(BundleContext context) throws Exception { this.context = context; activator = this; new Thread(() -> Application.launch(Udoo15App.class), "JavaFX Desktop launcher").start(); } @Override public void stop(BundleContext context) throws Exception { Platform.exit(); } public BundleContext getBundleContext() { return context; } } Op 20-02-16 om 01:28 schreef Stephen Winnall: > Anirvan, Kevin > > Thanks for this. > > I?m an expert neither in JavaFX nor in OSGi, but I think the basis of the JavaFX/OSGi incompatibility is control. To work with OSGi, JavaFX has to relinquish control of its startup sequence to OSGi in such a way that javafx.application.Application (or its proxy) is instantiated by OSGi and submits to OSGi?s bundle/service lifecycle. AN OSGi expert can probably formulate this better? > > Platform.startup(runnable) /might/ do it. Platform.launch(class) doesn?t because the object thereby instantiated is always under the control of JavaFX - and thus not of OSGi. > > I?m not comfortable using JFXPanel: if I wanted to use Swing I wouldn?t be trying to use JavaFX. But thank you for the hint. > > Steve > >> On 19 Feb 2016, at 16:41, Kevin Rushforth wrote: >> >> And for JDK 9 there is now: >> >> Platform.startup(Runnable); >> >> -- Kevin >> >> >> Anirvan Sarkar wrote: >>> Hi Stephen, >>> >>> FYI, there is another way of initializing JavaFX runtime. Just use: >>> >>> new JFXPanel(); >>> >>> It is documented[1] that FX runtime is initialized when the first JFXPanel >>> instance is constructed. >>> >>> Also JavaFX 9 will provide an official API to start the FX platform [2] [3]. >>> >>> >>> [1] >>> https://docs.oracle.com/javase/8/javafx/api/javafx/application/Platform.html#runLater-java.lang.Runnable - >>> [2]https://bugs.openjdk.java.net/browse/JDK-8090585 >>> [3] >>> http://download.java.net/jdk9/jfxdocs/javafx/application/Platform.html#startup-java.lang.Runnable - >>> >>> >>> On 18 February 2016 at 20:08, Stephen Winnall wrote: >>> >>> >>>> As I understand it, there are two ways of activating JavaFX: >>>> >>>> 1) sub-class javafx.application.Application or >>>> 2) call javafx.application.Application.launch() >>>> >>>> >>> Op 20-02-16 om 01:28 schreef Stephen Winnall: > Anirvan, Kevin > > Thanks for this. > > I?m an expert neither in JavaFX nor in OSGi, but I think the basis of the JavaFX/OSGi incompatibility is control. To work with OSGi, JavaFX has to relinquish control of its startup sequence to OSGi in such a way that javafx.application.Application (or its proxy) is instantiated by OSGi and submits to OSGi?s bundle/service lifecycle. AN OSGi expert can probably formulate this better? > > Platform.startup(runnable) /might/ do it. Platform.launch(class) doesn?t because the object thereby instantiated is always under the control of JavaFX - and thus not of OSGi. > > I?m not comfortable using JFXPanel: if I wanted to use Swing I wouldn?t be trying to use JavaFX. But thank you for the hint. > > Steve > >> On 19 Feb 2016, at 16:41, Kevin Rushforth wrote: >> >> And for JDK 9 there is now: >> >> Platform.startup(Runnable); >> >> -- Kevin >> >> >> Anirvan Sarkar wrote: >>> Hi Stephen, >>> >>> FYI, there is another way of initializing JavaFX runtime. Just use: >>> >>> new JFXPanel(); >>> >>> It is documented[1] that FX runtime is initialized when the first JFXPanel >>> instance is constructed. >>> >>> Also JavaFX 9 will provide an official API to start the FX platform [2] [3]. >>> >>> >>> [1] >>> https://docs.oracle.com/javase/8/javafx/api/javafx/application/Platform.html#runLater-java.lang.Runnable - >>> [2] https://bugs.openjdk.java.net/browse/JDK-8090585 >>> [3] >>> http://download.java.net/jdk9/jfxdocs/javafx/application/Platform.html#startup-java.lang.Runnable - >>> >>> >>> On 18 February 2016 at 20:08, Stephen Winnall wrote: >>> >>> >>>> As I understand it, there are two ways of activating JavaFX: >>>> >>>> 1) sub-class javafx.application.Application or >>>> 2) call javafx.application.Application.launch() >>>> >>>> >>> >>> >>> From steve at winnall.ch Sat Feb 20 14:08:44 2016 From: steve at winnall.ch (Stephen Winnall) Date: Sat, 20 Feb 2016 15:08:44 +0100 Subject: JFX as an OSGi service? In-Reply-To: <56C86B35.1010706@cuhka.com> References: <4C4D64B8-8432-47A2-998C-C2E0B199F2F6@winnall.ch> <56C737B9.6000506@oracle.com> <51A9248B-7749-4A6E-BC3E-B36D7526FA0F@winnall.ch> <56C86B35.1010706@cuhka.com> Message-ID: <6510BC25-B97A-4787-A142-920F459817C1@winnall.ch> Hi Maurice I have done something similar, but it has the following drawback in my view: the class launched (Udoo15App in your case) does not run under OSGi control, so it has no access to OSGi bundles or services, nor is it accessible by them. If you don?t need that, you're OK. But I need that class to be part of the OSGi world because other bundles/services are going to add parts to the UI as they are instantiated. Steve > On 20 Feb 2016, at 14:33, Maurice wrote: > > > For my OSGi based JavaFX solution on the Udoo Quad (ARM based Linux) I created a service that publishes the application in the context.The application does as little as possible. It sets up the primary stage as fullscreen and puts a stackpane in it. Initially the stackpane displays a 'boot logo', until the actual desktop bundle is started and registered with the application. Note that you have to start the application on a separate thread, as the thread will be blocked. > > On Java 8 this means that although the application bundle can't be updated in a running OSGi container, but that is why the desktop exists. On startup it registers itself, and thus the application content, with the application, and when it is stopped it removes the content from the application. The application has thus rarely to be updated itself. > > Regards, > Maurice. > > > > public class UdooActivator implements BundleActivator { > private static UdooActivator activator; > private BundleContext context; > > static UdooActivator bundleActivator() { > return requireNonNull(activator, "activator not set"); > } > > @Override > public void start(BundleContext context) throws Exception { > this.context = context; > activator = this; > new Thread(() -> Application.launch(Udoo15App.class), "JavaFX Desktop launcher").start(); > } > > @Override > public void stop(BundleContext context) throws Exception { > Platform.exit(); > } > > public BundleContext getBundleContext() { > return context; > } > } > > Op 20-02-16 om 01:28 schreef Stephen Winnall: >> Anirvan, Kevin >> >> Thanks for this. >> >> I?m an expert neither in JavaFX nor in OSGi, but I think the basis of the JavaFX/OSGi incompatibility is control. To work with OSGi, JavaFX has to relinquish control of its startup sequence to OSGi in such a way that javafx.application.Application (or its proxy) is instantiated by OSGi and submits to OSGi?s bundle/service lifecycle. AN OSGi expert can probably formulate this better? >> >> Platform.startup(runnable) /might/ do it. Platform.launch(class) doesn?t because the object thereby instantiated is always under the control of JavaFX - and thus not of OSGi. >> >> I?m not comfortable using JFXPanel: if I wanted to use Swing I wouldn?t be trying to use JavaFX. But thank you for the hint. >> >> Steve >> >>> On 19 Feb 2016, at 16:41, Kevin Rushforth wrote: >>> >>> And for JDK 9 there is now: >>> >>> Platform.startup(Runnable); >>> >>> -- Kevin >>> >>> >>> Anirvan Sarkar wrote: >>>> Hi Stephen, >>>> >>>> FYI, there is another way of initializing JavaFX runtime. Just use: >>>> >>>> new JFXPanel(); >>>> >>>> It is documented[1] that FX runtime is initialized when the first JFXPanel >>>> instance is constructed. >>>> >>>> Also JavaFX 9 will provide an official API to start the FX platform [2] [3]. >>>> >>>> >>>> [1] >>>> https://docs.oracle.com/javase/8/javafx/api/javafx/application/Platform.html#runLater-java.lang.Runnable - >>>> [2]https://bugs.openjdk.java.net/browse/JDK-8090585 >>>> [3] >>>> http://download.java.net/jdk9/jfxdocs/javafx/application/Platform.html#startup-java.lang.Runnable - >>>> >>>> >>>> On 18 February 2016 at 20:08, Stephen Winnall wrote: >>>> >>>> >>>>> As I understand it, there are two ways of activating JavaFX: >>>>> >>>>> 1) sub-class javafx.application.Application or >>>>> 2) call javafx.application.Application.launch() >>>>> >>>>> >>>> > > > > Op 20-02-16 om 01:28 schreef Stephen Winnall: >> Anirvan, Kevin >> >> Thanks for this. >> >> I?m an expert neither in JavaFX nor in OSGi, but I think the basis of the JavaFX/OSGi incompatibility is control. To work with OSGi, JavaFX has to relinquish control of its startup sequence to OSGi in such a way that javafx.application.Application (or its proxy) is instantiated by OSGi and submits to OSGi?s bundle/service lifecycle. AN OSGi expert can probably formulate this better? >> >> Platform.startup(runnable) /might/ do it. Platform.launch(class) doesn?t because the object thereby instantiated is always under the control of JavaFX - and thus not of OSGi. >> >> I?m not comfortable using JFXPanel: if I wanted to use Swing I wouldn?t be trying to use JavaFX. But thank you for the hint. >> >> Steve >> >>> On 19 Feb 2016, at 16:41, Kevin Rushforth wrote: >>> >>> And for JDK 9 there is now: >>> >>> Platform.startup(Runnable); >>> >>> -- Kevin >>> >>> >>> Anirvan Sarkar wrote: >>>> Hi Stephen, >>>> >>>> FYI, there is another way of initializing JavaFX runtime. Just use: >>>> >>>> new JFXPanel(); >>>> >>>> It is documented[1] that FX runtime is initialized when the first JFXPanel >>>> instance is constructed. >>>> >>>> Also JavaFX 9 will provide an official API to start the FX platform [2] [3]. >>>> >>>> >>>> [1] >>>> https://docs.oracle.com/javase/8/javafx/api/javafx/application/Platform.html#runLater-java.lang.Runnable - >>>> [2] https://bugs.openjdk.java.net/browse/JDK-8090585 >>>> [3] >>>> http://download.java.net/jdk9/jfxdocs/javafx/application/Platform.html#startup-java.lang.Runnable - >>>> >>>> >>>> On 18 February 2016 at 20:08, Stephen Winnall wrote: >>>> >>>> >>>>> As I understand it, there are two ways of activating JavaFX: >>>>> >>>>> 1) sub-class javafx.application.Application or >>>>> 2) call javafx.application.Application.launch() >>>>> >>>>> >>>> >>>> >>>> > From info at cuhka.com Sat Feb 20 14:27:47 2016 From: info at cuhka.com (Maurice) Date: Sat, 20 Feb 2016 15:27:47 +0100 Subject: JFX as an OSGi service? In-Reply-To: <6510BC25-B97A-4787-A142-920F459817C1@winnall.ch> References: <4C4D64B8-8432-47A2-998C-C2E0B199F2F6@winnall.ch> <56C737B9.6000506@oracle.com> <51A9248B-7749-4A6E-BC3E-B36D7526FA0F@winnall.ch> <56C86B35.1010706@cuhka.com> <6510BC25-B97A-4787-A142-920F459817C1@winnall.ch> Message-ID: <56C877E3.1090904@cuhka.com> That is why the bundle activator creates a bundle-singleton of itself, that way the app can access the OSGi world. In my case to register itself as a service. @Override public void start(Stage primaryStage) throws Exception { .... primaryStage.show(); Dictionary properties = createDictionary(); BundleContext bundleContext = UdooActivator.bundleActivator().getBundleContext(); bundleContext.registerService(com.cuhka.home.application.Application.class, this, properties); } Maurice. Op 20-02-16 om 15:08 schreef Stephen Winnall: > Hi Maurice > > I have done something similar, but it has the following drawback in my view: the class launched (Udoo15App in your case) does not run under OSGi control, so it has no access to OSGi bundles or services, nor is it accessible by them. If you don?t need that, you're OK. But I need that class to be part of the OSGi world because other bundles/services are going to add parts to the UI as they are instantiated. > > Steve > >> On 20 Feb 2016, at 14:33, Maurice wrote: >> >> >> For my OSGi based JavaFX solution on the Udoo Quad (ARM based Linux) I created a service that publishes the application in the context.The application does as little as possible. It sets up the primary stage as fullscreen and puts a stackpane in it. Initially the stackpane displays a 'boot logo', until the actual desktop bundle is started and registered with the application. Note that you have to start the application on a separate thread, as the thread will be blocked. >> >> On Java 8 this means that although the application bundle can't be updated in a running OSGi container, but that is why the desktop exists. On startup it registers itself, and thus the application content, with the application, and when it is stopped it removes the content from the application. The application has thus rarely to be updated itself. >> >> Regards, >> Maurice. >> >> >> >> public class UdooActivator implements BundleActivator { >> private static UdooActivator activator; >> private BundleContext context; >> >> static UdooActivator bundleActivator() { >> return requireNonNull(activator, "activator not set"); >> } >> >> @Override >> public void start(BundleContext context) throws Exception { >> this.context = context; >> activator = this; >> new Thread(() -> Application.launch(Udoo15App.class), "JavaFX Desktop launcher").start(); >> } >> >> @Override >> public void stop(BundleContext context) throws Exception { >> Platform.exit(); >> } >> >> public BundleContext getBundleContext() { >> return context; >> } >> } >> >> Op 20-02-16 om 01:28 schreef Stephen Winnall: >>> Anirvan, Kevin >>> >>> Thanks for this. >>> >>> I?m an expert neither in JavaFX nor in OSGi, but I think the basis of the JavaFX/OSGi incompatibility is control. To work with OSGi, JavaFX has to relinquish control of its startup sequence to OSGi in such a way that javafx.application.Application (or its proxy) is instantiated by OSGi and submits to OSGi?s bundle/service lifecycle. AN OSGi expert can probably formulate this better? >>> >>> Platform.startup(runnable) /might/ do it. Platform.launch(class) doesn?t because the object thereby instantiated is always under the control of JavaFX - and thus not of OSGi. >>> >>> I?m not comfortable using JFXPanel: if I wanted to use Swing I wouldn?t be trying to use JavaFX. But thank you for the hint. >>> >>> Steve >>> >>>> On 19 Feb 2016, at 16:41, Kevin Rushforth wrote: >>>> >>>> And for JDK 9 there is now: >>>> >>>> Platform.startup(Runnable); >>>> >>>> -- Kevin >>>> >>>> >>>> Anirvan Sarkar wrote: >>>>> Hi Stephen, >>>>> >>>>> FYI, there is another way of initializing JavaFX runtime. Just use: >>>>> >>>>> new JFXPanel(); >>>>> >>>>> It is documented[1] that FX runtime is initialized when the first JFXPanel >>>>> instance is constructed. >>>>> >>>>> Also JavaFX 9 will provide an official API to start the FX platform [2] [3]. >>>>> >>>>> >>>>> [1] >>>>> https://docs.oracle.com/javase/8/javafx/api/javafx/application/Platform.html#runLater-java.lang.Runnable - >>>>> [2]https://bugs.openjdk.java.net/browse/JDK-8090585 >>>>> [3] >>>>> http://download.java.net/jdk9/jfxdocs/javafx/application/Platform.html#startup-java.lang.Runnable - >>>>> >>>>> >>>>> On 18 February 2016 at 20:08, Stephen Winnall wrote: >>>>> >>>>> >>>>>> As I understand it, there are two ways of activating JavaFX: >>>>>> >>>>>> 1) sub-class javafx.application.Application or >>>>>> 2) call javafx.application.Application.launch() >>>>>> >>>>>> >>>>> >> >> >> Op 20-02-16 om 01:28 schreef Stephen Winnall: >>> Anirvan, Kevin >>> >>> Thanks for this. >>> >>> I?m an expert neither in JavaFX nor in OSGi, but I think the basis of the JavaFX/OSGi incompatibility is control. To work with OSGi, JavaFX has to relinquish control of its startup sequence to OSGi in such a way that javafx.application.Application (or its proxy) is instantiated by OSGi and submits to OSGi?s bundle/service lifecycle. AN OSGi expert can probably formulate this better? >>> >>> Platform.startup(runnable) /might/ do it. Platform.launch(class) doesn?t because the object thereby instantiated is always under the control of JavaFX - and thus not of OSGi. >>> >>> I?m not comfortable using JFXPanel: if I wanted to use Swing I wouldn?t be trying to use JavaFX. But thank you for the hint. >>> >>> Steve >>> >>>> On 19 Feb 2016, at 16:41, Kevin Rushforth wrote: >>>> >>>> And for JDK 9 there is now: >>>> >>>> Platform.startup(Runnable); >>>> >>>> -- Kevin >>>> >>>> >>>> Anirvan Sarkar wrote: >>>>> Hi Stephen, >>>>> >>>>> FYI, there is another way of initializing JavaFX runtime. Just use: >>>>> >>>>> new JFXPanel(); >>>>> >>>>> It is documented[1] that FX runtime is initialized when the first JFXPanel >>>>> instance is constructed. >>>>> >>>>> Also JavaFX 9 will provide an official API to start the FX platform [2] [3]. >>>>> >>>>> >>>>> [1] >>>>> https://docs.oracle.com/javase/8/javafx/api/javafx/application/Platform.html#runLater-java.lang.Runnable - >>>>> [2] https://bugs.openjdk.java.net/browse/JDK-8090585 >>>>> [3] >>>>> http://download.java.net/jdk9/jfxdocs/javafx/application/Platform.html#startup-java.lang.Runnable - >>>>> >>>>> >>>>> On 18 February 2016 at 20:08, Stephen Winnall wrote: >>>>> >>>>> >>>>>> As I understand it, there are two ways of activating JavaFX: >>>>>> >>>>>> 1) sub-class javafx.application.Application or >>>>>> 2) call javafx.application.Application.launch() >>>>>> >>>>>> >>>>> >>>>> From steve at winnall.ch Sat Feb 20 14:50:24 2016 From: steve at winnall.ch (Stephen Winnall) Date: Sat, 20 Feb 2016 15:50:24 +0100 Subject: JFX as an OSGi service? In-Reply-To: <56C877E3.1090904@cuhka.com> References: <4C4D64B8-8432-47A2-998C-C2E0B199F2F6@winnall.ch> <56C737B9.6000506@oracle.com> <51A9248B-7749-4A6E-BC3E-B36D7526FA0F@winnall.ch> <56C86B35.1010706@cuhka.com> <6510BC25-B97A-4787-A142-920F459817C1@winnall.ch> <56C877E3.1090904@cuhka.com> Message-ID: I have been trying a similar approach. I?m using declarative services and I have some @References to other services in the Application, but I haven?t managed to get these instantiated. Do you have an approach for that? I suppose I can just write some code and instantiate them manually? Steve > On 20 Feb 2016, at 15:27, Maurice wrote: > > That is why the bundle activator creates a bundle-singleton of itself, that way the app can access the OSGi world. In my case to register itself as a service. > > > @Override > public void start(Stage primaryStage) throws Exception { > .... > primaryStage.show(); > > Dictionary properties = createDictionary(); > BundleContext bundleContext = UdooActivator.bundleActivator().getBundleContext(); > bundleContext.registerService(com.cuhka.home.application.Application.class, this, properties); > } > > Maurice. > Op 20-02-16 om 15:08 schreef Stephen Winnall: >> Hi Maurice >> >> I have done something similar, but it has the following drawback in my view: the class launched (Udoo15App in your case) does not run under OSGi control, so it has no access to OSGi bundles or services, nor is it accessible by them. If you don?t need that, you're OK. But I need that class to be part of the OSGi world because other bundles/services are going to add parts to the UI as they are instantiated. >> >> Steve >> >>> On 20 Feb 2016, at 14:33, Maurice wrote: >>> >>> >>> For my OSGi based JavaFX solution on the Udoo Quad (ARM based Linux) I created a service that publishes the application in the context.The application does as little as possible. It sets up the primary stage as fullscreen and puts a stackpane in it. Initially the stackpane displays a 'boot logo', until the actual desktop bundle is started and registered with the application. Note that you have to start the application on a separate thread, as the thread will be blocked. >>> >>> On Java 8 this means that although the application bundle can't be updated in a running OSGi container, but that is why the desktop exists. On startup it registers itself, and thus the application content, with the application, and when it is stopped it removes the content from the application. The application has thus rarely to be updated itself. >>> >>> Regards, >>> Maurice. >>> >>> >>> >>> public class UdooActivator implements BundleActivator { >>> private static UdooActivator activator; >>> private BundleContext context; >>> >>> static UdooActivator bundleActivator() { >>> return requireNonNull(activator, "activator not set"); >>> } >>> >>> @Override >>> public void start(BundleContext context) throws Exception { >>> this.context = context; >>> activator = this; >>> new Thread(() -> Application.launch(Udoo15App.class), "JavaFX Desktop launcher").start(); >>> } >>> >>> @Override >>> public void stop(BundleContext context) throws Exception { >>> Platform.exit(); >>> } >>> >>> public BundleContext getBundleContext() { >>> return context; >>> } >>> } >>> >>> Op 20-02-16 om 01:28 schreef Stephen Winnall: >>>> Anirvan, Kevin >>>> >>>> Thanks for this. >>>> >>>> I?m an expert neither in JavaFX nor in OSGi, but I think the basis of the JavaFX/OSGi incompatibility is control. To work with OSGi, JavaFX has to relinquish control of its startup sequence to OSGi in such a way that javafx.application.Application (or its proxy) is instantiated by OSGi and submits to OSGi?s bundle/service lifecycle. AN OSGi expert can probably formulate this better? >>>> >>>> Platform.startup(runnable) /might/ do it. Platform.launch(class) doesn?t because the object thereby instantiated is always under the control of JavaFX - and thus not of OSGi. >>>> >>>> I?m not comfortable using JFXPanel: if I wanted to use Swing I wouldn?t be trying to use JavaFX. But thank you for the hint. >>>> >>>> Steve >>>> >>>>> On 19 Feb 2016, at 16:41, Kevin Rushforth wrote: >>>>> >>>>> And for JDK 9 there is now: >>>>> >>>>> Platform.startup(Runnable); >>>>> >>>>> -- Kevin >>>>> >>>>> >>>>> Anirvan Sarkar wrote: >>>>>> Hi Stephen, >>>>>> >>>>>> FYI, there is another way of initializing JavaFX runtime. Just use: >>>>>> >>>>>> new JFXPanel(); >>>>>> >>>>>> It is documented[1] that FX runtime is initialized when the first JFXPanel >>>>>> instance is constructed. >>>>>> >>>>>> Also JavaFX 9 will provide an official API to start the FX platform [2] [3]. >>>>>> >>>>>> >>>>>> [1] >>>>>> https://docs.oracle.com/javase/8/javafx/api/javafx/application/Platform.html#runLater-java.lang.Runnable - >>>>>> [2]https://bugs.openjdk.java.net/browse/JDK-8090585 >>>>>> [3] >>>>>> http://download.java.net/jdk9/jfxdocs/javafx/application/Platform.html#startup-java.lang.Runnable - >>>>>> >>>>>> >>>>>> On 18 February 2016 at 20:08, Stephen Winnall wrote: >>>>>> >>>>>> >>>>>>> As I understand it, there are two ways of activating JavaFX: >>>>>>> >>>>>>> 1) sub-class javafx.application.Application or >>>>>>> 2) call javafx.application.Application.launch() >>>>>>> >>>>>>> >>>>>> >>> >>> >>> Op 20-02-16 om 01:28 schreef Stephen Winnall: >>>> Anirvan, Kevin >>>> >>>> Thanks for this. >>>> >>>> I?m an expert neither in JavaFX nor in OSGi, but I think the basis of the JavaFX/OSGi incompatibility is control. To work with OSGi, JavaFX has to relinquish control of its startup sequence to OSGi in such a way that javafx.application.Application (or its proxy) is instantiated by OSGi and submits to OSGi?s bundle/service lifecycle. AN OSGi expert can probably formulate this better? >>>> >>>> Platform.startup(runnable) /might/ do it. Platform.launch(class) doesn?t because the object thereby instantiated is always under the control of JavaFX - and thus not of OSGi. >>>> >>>> I?m not comfortable using JFXPanel: if I wanted to use Swing I wouldn?t be trying to use JavaFX. But thank you for the hint. >>>> >>>> Steve >>>> >>>>> On 19 Feb 2016, at 16:41, Kevin Rushforth wrote: >>>>> >>>>> And for JDK 9 there is now: >>>>> >>>>> Platform.startup(Runnable); >>>>> >>>>> -- Kevin >>>>> >>>>> >>>>> Anirvan Sarkar wrote: >>>>>> Hi Stephen, >>>>>> >>>>>> FYI, there is another way of initializing JavaFX runtime. Just use: >>>>>> >>>>>> new JFXPanel(); >>>>>> >>>>>> It is documented[1] that FX runtime is initialized when the first JFXPanel >>>>>> instance is constructed. >>>>>> >>>>>> Also JavaFX 9 will provide an official API to start the FX platform [2] [3]. >>>>>> >>>>>> >>>>>> [1] >>>>>> https://docs.oracle.com/javase/8/javafx/api/javafx/application/Platform.html#runLater-java.lang.Runnable - >>>>>> [2] https://bugs.openjdk.java.net/browse/JDK-8090585 >>>>>> [3] >>>>>> http://download.java.net/jdk9/jfxdocs/javafx/application/Platform.html#startup-java.lang.Runnable - >>>>>> >>>>>> >>>>>> On 18 February 2016 at 20:08, Stephen Winnall wrote: >>>>>> >>>>>> >>>>>>> As I understand it, there are two ways of activating JavaFX: >>>>>>> >>>>>>> 1) sub-class javafx.application.Application or >>>>>>> 2) call javafx.application.Application.launch() >>>>>>> >>>>>>> >>>>>> >>>>>> > From info at cuhka.com Sat Feb 20 15:50:27 2016 From: info at cuhka.com (Maurice) Date: Sat, 20 Feb 2016 16:50:27 +0100 Subject: JFX as an OSGi service? In-Reply-To: References: <4C4D64B8-8432-47A2-998C-C2E0B199F2F6@winnall.ch> <56C737B9.6000506@oracle.com> <51A9248B-7749-4A6E-BC3E-B36D7526FA0F@winnall.ch> <56C86B35.1010706@cuhka.com> <6510BC25-B97A-4787-A142-920F459817C1@winnall.ch> <56C877E3.1090904@cuhka.com> Message-ID: <56C88B43.7040408@cuhka.com> I make sure that the application is basically only the primary stage, therefore it only needs to publish itself. All other UI and business logic is done by other bundles. Op 20-02-16 om 15:50 schreef Stephen Winnall: > I have been trying a similar approach. I?m using declarative services > and I have some @References to other services in the Application, but > I haven?t managed to get these instantiated. Do you have an approach > for that? I suppose I can just write some code and instantiate them > manually? > > Steve > From derijcke.erik at gmail.com Sat Feb 20 19:37:22 2016 From: derijcke.erik at gmail.com (Erik De Rijcke) Date: Sat, 20 Feb 2016 20:37:22 +0100 Subject: JFX as an OSGi service? In-Reply-To: <56C877E3.1090904@cuhka.com> References: <4C4D64B8-8432-47A2-998C-C2E0B199F2F6@winnall.ch> <56C737B9.6000506@oracle.com> <51A9248B-7749-4A6E-BC3E-B36D7526FA0F@winnall.ch> <56C86B35.1010706@cuhka.com> <6510BC25-B97A-4787-A142-920F459817C1@winnall.ch> <56C877E3.1090904@cuhka.com> Message-ID: This way only the app will be accessible by other components through the service registry. The app itself can not have any @reference because it it is javafx itself that instantiates the app object and not the osgi declarative services framework (which also takes care of injecting your dependencies). The way to work around this in java8 is to take the approach I describe, as far as I know that is the only workaround to get scr and javafx glued together. In javafx 9 this would be fixed by having your service component implement runnable and use the api described by kevin, as you can reuse the object created by the osgi framework. On Sat, Feb 20, 2016 at 3:27 PM, Maurice wrote: > That is why the bundle activator creates a bundle-singleton of itself, > that way the app can access the OSGi world. In my case to register itself > as a service. > > > @Override > public void start(Stage primaryStage) throws Exception { > .... > primaryStage.show(); > > Dictionary properties = createDictionary(); > BundleContext bundleContext = > UdooActivator.bundleActivator().getBundleContext(); > bundleContext.registerService(com.cuhka.home.application.Application.class, > this, properties); > } > > Maurice. > Op 20-02-16 om 15:08 schreef Stephen Winnall: > > Hi Maurice >> >> I have done something similar, but it has the following drawback in my >> view: the class launched (Udoo15App in your case) does not run under OSGi >> control, so it has no access to OSGi bundles or services, nor is it >> accessible by them. If you don?t need that, you're OK. But I need that >> class to be part of the OSGi world because other bundles/services are going >> to add parts to the UI as they are instantiated. >> >> Steve >> >> On 20 Feb 2016, at 14:33, Maurice wrote: >>> >>> >>> For my OSGi based JavaFX solution on the Udoo Quad (ARM based Linux) I >>> created a service that publishes the application in the context.The >>> application does as little as possible. It sets up the primary stage as >>> fullscreen and puts a stackpane in it. Initially the stackpane displays a >>> 'boot logo', until the actual desktop bundle is started and registered with >>> the application. Note that you have to start the application on a separate >>> thread, as the thread will be blocked. >>> >>> On Java 8 this means that although the application bundle can't be >>> updated in a running OSGi container, but that is why the desktop exists. On >>> startup it registers itself, and thus the application content, with the >>> application, and when it is stopped it removes the content from the >>> application. The application has thus rarely to be updated itself. >>> >>> Regards, >>> Maurice. >>> >>> >>> >>> public class UdooActivator implements BundleActivator { >>> private static UdooActivator activator; >>> private BundleContext context; >>> >>> static UdooActivator bundleActivator() { >>> return requireNonNull(activator, "activator not set"); >>> } >>> >>> @Override >>> public void start(BundleContext context) throws Exception { >>> this.context = context; >>> activator = this; >>> new Thread(() -> Application.launch(Udoo15App.class), "JavaFX >>> Desktop launcher").start(); >>> } >>> >>> @Override >>> public void stop(BundleContext context) throws Exception { >>> Platform.exit(); >>> } >>> >>> public BundleContext getBundleContext() { >>> return context; >>> } >>> } >>> >>> Op 20-02-16 om 01:28 schreef Stephen Winnall: >>> >>>> Anirvan, Kevin >>>> >>>> Thanks for this. >>>> >>>> I?m an expert neither in JavaFX nor in OSGi, but I think the basis of >>>> the JavaFX/OSGi incompatibility is control. To work with OSGi, JavaFX has >>>> to relinquish control of its startup sequence to OSGi in such a way that >>>> javafx.application.Application (or its proxy) is instantiated by OSGi and >>>> submits to OSGi?s bundle/service lifecycle. AN OSGi expert can probably >>>> formulate this better? >>>> >>>> Platform.startup(runnable) /might/ do it. Platform.launch(class) >>>> doesn?t because the object thereby instantiated is always under the control >>>> of JavaFX - and thus not of OSGi. >>>> >>>> I?m not comfortable using JFXPanel: if I wanted to use Swing I wouldn?t >>>> be trying to use JavaFX. But thank you for the hint. >>>> >>>> Steve >>>> >>>> On 19 Feb 2016, at 16:41, Kevin Rushforth >>>>> wrote: >>>>> >>>>> And for JDK 9 there is now: >>>>> >>>>> Platform.startup(Runnable); >>>>> >>>>> -- Kevin >>>>> >>>>> >>>>> Anirvan Sarkar wrote: >>>>> >>>>>> Hi Stephen, >>>>>> >>>>>> FYI, there is another way of initializing JavaFX runtime. Just use: >>>>>> >>>>>> new JFXPanel(); >>>>>> >>>>>> It is documented[1] that FX runtime is initialized when the first >>>>>> JFXPanel >>>>>> instance is constructed. >>>>>> >>>>>> Also JavaFX 9 will provide an official API to start the FX platform >>>>>> [2] [3]. >>>>>> >>>>>> >>>>>> [1] >>>>>> >>>>>> https://docs.oracle.com/javase/8/javafx/api/javafx/application/Platform.html#runLater-java.lang.Runnable >>>>>> < >>>>>> https://docs.oracle.com/javase/8/javafx/api/javafx/application/Platform.html#runLater-java.lang.Runnable >>>>>> >- >>>>>> [2]https://bugs.openjdk.java.net/browse/JDK-8090585 < >>>>>> https://bugs.openjdk.java.net/browse/JDK-8090585> >>>>>> [3] >>>>>> >>>>>> http://download.java.net/jdk9/jfxdocs/javafx/application/Platform.html#startup-java.lang.Runnable >>>>>> < >>>>>> http://download.java.net/jdk9/jfxdocs/javafx/application/Platform.html#startup-java.lang.Runnable >>>>>> >- >>>>>> >>>>>> >>>>>> On 18 February 2016 at 20:08, Stephen Winnall >>>>>> wrote: >>>>>> >>>>>> >>>>>> >>>>>>> As I understand it, there are two ways of activating JavaFX: >>>>>>> >>>>>>> 1) sub-class javafx.application.Application or >>>>>>> 2) call javafx.application.Application.launch() >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>> >>> Op 20-02-16 om 01:28 schreef Stephen Winnall: >>> >>>> Anirvan, Kevin >>>> >>>> Thanks for this. >>>> >>>> I?m an expert neither in JavaFX nor in OSGi, but I think the basis of >>>> the JavaFX/OSGi incompatibility is control. To work with OSGi, JavaFX has >>>> to relinquish control of its startup sequence to OSGi in such a way that >>>> javafx.application.Application (or its proxy) is instantiated by OSGi and >>>> submits to OSGi?s bundle/service lifecycle. AN OSGi expert can probably >>>> formulate this better? >>>> >>>> Platform.startup(runnable) /might/ do it. Platform.launch(class) >>>> doesn?t because the object thereby instantiated is always under the control >>>> of JavaFX - and thus not of OSGi. >>>> >>>> I?m not comfortable using JFXPanel: if I wanted to use Swing I wouldn?t >>>> be trying to use JavaFX. But thank you for the hint. >>>> >>>> Steve >>>> >>>> On 19 Feb 2016, at 16:41, Kevin Rushforth >>>>> wrote: >>>>> >>>>> And for JDK 9 there is now: >>>>> >>>>> Platform.startup(Runnable); >>>>> >>>>> -- Kevin >>>>> >>>>> >>>>> Anirvan Sarkar wrote: >>>>> >>>>>> Hi Stephen, >>>>>> >>>>>> FYI, there is another way of initializing JavaFX runtime. Just use: >>>>>> >>>>>> new JFXPanel(); >>>>>> >>>>>> It is documented[1] that FX runtime is initialized when the first >>>>>> JFXPanel >>>>>> instance is constructed. >>>>>> >>>>>> Also JavaFX 9 will provide an official API to start the FX platform >>>>>> [2] [3]. >>>>>> >>>>>> >>>>>> [1] >>>>>> >>>>>> https://docs.oracle.com/javase/8/javafx/api/javafx/application/Platform.html#runLater-java.lang.Runnable >>>>>> < >>>>>> https://docs.oracle.com/javase/8/javafx/api/javafx/application/Platform.html#runLater-java.lang.Runnable >>>>>> >- >>>>>> [2] https://bugs.openjdk.java.net/browse/JDK-8090585 < >>>>>> https://bugs.openjdk.java.net/browse/JDK-8090585> >>>>>> [3] >>>>>> >>>>>> http://download.java.net/jdk9/jfxdocs/javafx/application/Platform.html#startup-java.lang.Runnable >>>>>> < >>>>>> http://download.java.net/jdk9/jfxdocs/javafx/application/Platform.html#startup-java.lang.Runnable >>>>>> >- >>>>>> >>>>>> >>>>>> On 18 February 2016 at 20:08, Stephen Winnall >>>>>> wrote: >>>>>> >>>>>> >>>>>> >>>>>>> As I understand it, there are two ways of activating JavaFX: >>>>>>> >>>>>>> 1) sub-class javafx.application.Application or >>>>>>> 2) call javafx.application.Application.launch() >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> >>>>> > From guru.hb at oracle.com Sun Feb 21 04:22:43 2016 From: guru.hb at oracle.com (Guru Hb) Date: Sat, 20 Feb 2016 20:22:43 -0800 (PST) Subject: [9] Review request for 8139114: WebView crashes on Yahoo login page In-Reply-To: <15a2a081-054d-4d82-8fff-632d43936d90@default> References: <2efd6ecd-2204-4d66-8ecc-0bb2977f1a09@default> <15a2a081-054d-4d82-8fff-632d43936d90@default> Message-ID: <7a5277de-8860-490f-9c63-ec6893df449c@default> Hi Alexander, Kevin and Arun JBS : https://bugs.openjdk.java.net/browse/JDK-8139114 Webrev : http://cr.openjdk.java.net/~ghb/8139114/webrev.00/ RC and Solution updated in JIRA. Thanks, Guru From steve at winnall.ch Sun Feb 21 19:22:54 2016 From: steve at winnall.ch (Stephen Winnall) Date: Sun, 21 Feb 2016 20:22:54 +0100 Subject: JFX as an OSGi service? In-Reply-To: References: <4C4D64B8-8432-47A2-998C-C2E0B199F2F6@winnall.ch> <56C737B9.6000506@oracle.com> <51A9248B-7749-4A6E-BC3E-B36D7526FA0F@winnall.ch> <56C86B35.1010706@cuhka.com> <6510BC25-B97A-4787-A142-920F459817C1@winnall.ch> <56C877E3.1090904@cuhka.com> Message-ID: I?ve now got a subclass of javafx.application.Application that runs as an OSGi service and references other OSGi services under Java 8SE. I?ve tried to document it on Github (see https://github.com/winnall/OSGiJavaFXUsage) for the benefit of posterity. Let me know if there are any mistakes or improvements required in the - sparse - documentation. I?m also not very good at Git :-( Thanks to Erik de Rijcke, Maurice, Anirvan Sardar and Kevin Rushforth for their comments, all of which guided me - bouncing off the walls - to the goal. Steve > On 20 Feb 2016, at 20:37, Erik De Rijcke wrote: > > This way only the app will be accessible by other components through the service registry. The app itself can not have any @reference because it it is javafx itself that instantiates the app object and not the osgi declarative services framework (which also takes care of injecting your dependencies). > > The way to work around this in java8 is to take the approach I describe, as far as I know that is the only workaround to get scr and javafx glued together. > > In javafx 9 this would be fixed by having your service component implement runnable and use the api described by kevin, as you can reuse the object created by the osgi framework. > > On Sat, Feb 20, 2016 at 3:27 PM, Maurice > wrote: > That is why the bundle activator creates a bundle-singleton of itself, that way the app can access the OSGi world. In my case to register itself as a service. > > > @Override > public void start(Stage primaryStage) throws Exception { > .... > primaryStage.show(); > > Dictionary properties = createDictionary(); > BundleContext bundleContext = UdooActivator.bundleActivator().getBundleContext(); > bundleContext.registerService(com.cuhka.home.application.Application.class, this, properties); > } > > Maurice. > Op 20-02-16 om 15:08 schreef Stephen Winnall: > > Hi Maurice > > I have done something similar, but it has the following drawback in my view: the class launched (Udoo15App in your case) does not run under OSGi control, so it has no access to OSGi bundles or services, nor is it accessible by them. If you don?t need that, you're OK. But I need that class to be part of the OSGi world because other bundles/services are going to add parts to the UI as they are instantiated. > > Steve > > On 20 Feb 2016, at 14:33, Maurice > wrote: > > > For my OSGi based JavaFX solution on the Udoo Quad (ARM based Linux) I created a service that publishes the application in the context.The application does as little as possible. It sets up the primary stage as fullscreen and puts a stackpane in it. Initially the stackpane displays a 'boot logo', until the actual desktop bundle is started and registered with the application. Note that you have to start the application on a separate thread, as the thread will be blocked. > > On Java 8 this means that although the application bundle can't be updated in a running OSGi container, but that is why the desktop exists. On startup it registers itself, and thus the application content, with the application, and when it is stopped it removes the content from the application. The application has thus rarely to be updated itself. > > Regards, > Maurice. > > > > public class UdooActivator implements BundleActivator { > private static UdooActivator activator; > private BundleContext context; > > static UdooActivator bundleActivator() { > return requireNonNull(activator, "activator not set"); > } > > @Override > public void start(BundleContext context) throws Exception { > this.context = context; > activator = this; > new Thread(() -> Application.launch(Udoo15App.class), "JavaFX Desktop launcher").start(); > } > > @Override > public void stop(BundleContext context) throws Exception { > Platform.exit(); > } > > public BundleContext getBundleContext() { > return context; > } > } > > Op 20-02-16 om 01:28 schreef Stephen Winnall: > Anirvan, Kevin > > Thanks for this. > > I?m an expert neither in JavaFX nor in OSGi, but I think the basis of the JavaFX/OSGi incompatibility is control. To work with OSGi, JavaFX has to relinquish control of its startup sequence to OSGi in such a way that javafx.application.Application (or its proxy) is instantiated by OSGi and submits to OSGi?s bundle/service lifecycle. AN OSGi expert can probably formulate this better? > > Platform.startup(runnable) /might/ do it. Platform.launch(class) doesn?t because the object thereby instantiated is always under the control of JavaFX - and thus not of OSGi. > > I?m not comfortable using JFXPanel: if I wanted to use Swing I wouldn?t be trying to use JavaFX. But thank you for the hint. > > Steve > > On 19 Feb 2016, at 16:41, Kevin Rushforth> wrote: > > And for JDK 9 there is now: > > Platform.startup(Runnable); > > -- Kevin > > > Anirvan Sarkar wrote: > Hi Stephen, > > FYI, there is another way of initializing JavaFX runtime. Just use: > > new JFXPanel(); > > It is documented[1] that FX runtime is initialized when the first JFXPanel > instance is constructed. > > Also JavaFX 9 will provide an official API to start the FX platform [2] [3]. > > > [1] > https://docs.oracle.com/javase/8/javafx/api/javafx/application/Platform.html#runLater-java.lang.Runnable >- > [2]https://bugs.openjdk.java.net/browse/JDK-8090585 > > [3] > http://download.java.net/jdk9/jfxdocs/javafx/application/Platform.html#startup-java.lang.Runnable >- > > > On 18 February 2016 at 20:08, Stephen Winnall> > wrote: > > > As I understand it, there are two ways of activating JavaFX: > > 1) sub-class javafx.application.Application or > 2) call javafx.application.Application.launch() > > > > > > Op 20-02-16 om 01:28 schreef Stephen Winnall: > Anirvan, Kevin > > Thanks for this. > > I?m an expert neither in JavaFX nor in OSGi, but I think the basis of the JavaFX/OSGi incompatibility is control. To work with OSGi, JavaFX has to relinquish control of its startup sequence to OSGi in such a way that javafx.application.Application (or its proxy) is instantiated by OSGi and submits to OSGi?s bundle/service lifecycle. AN OSGi expert can probably formulate this better? > > Platform.startup(runnable) /might/ do it. Platform.launch(class) doesn?t because the object thereby instantiated is always under the control of JavaFX - and thus not of OSGi. > > I?m not comfortable using JFXPanel: if I wanted to use Swing I wouldn?t be trying to use JavaFX. But thank you for the hint. > > Steve > > On 19 Feb 2016, at 16:41, Kevin Rushforth > wrote: > > And for JDK 9 there is now: > > Platform.startup(Runnable); > > -- Kevin > > > Anirvan Sarkar wrote: > Hi Stephen, > > FYI, there is another way of initializing JavaFX runtime. Just use: > > new JFXPanel(); > > It is documented[1] that FX runtime is initialized when the first JFXPanel > instance is constructed. > > Also JavaFX 9 will provide an official API to start the FX platform [2] [3]. > > > [1] > https://docs.oracle.com/javase/8/javafx/api/javafx/application/Platform.html#runLater-java.lang.Runnable >- > [2] https://bugs.openjdk.java.net/browse/JDK-8090585 > > [3] > http://download.java.net/jdk9/jfxdocs/javafx/application/Platform.html#startup-java.lang.Runnable >- > > > On 18 February 2016 at 20:08, Stephen Winnall > > wrote: > > > As I understand it, there are two ways of activating JavaFX: > > 1) sub-class javafx.application.Application or > 2) call javafx.application.Application.launch() > > > > > > From rahman.usta.88 at gmail.com Sun Feb 21 19:58:41 2016 From: rahman.usta.88 at gmail.com (Rahman USTA) Date: Sun, 21 Feb 2016 21:58:41 +0200 Subject: JFX as an OSGi service? In-Reply-To: References: <4C4D64B8-8432-47A2-998C-C2E0B199F2F6@winnall.ch> <56C737B9.6000506@oracle.com> <51A9248B-7749-4A6E-BC3E-B36D7526FA0F@winnall.ch> <56C86B35.1010706@cuhka.com> <6510BC25-B97A-4787-A142-920F459817C1@winnall.ch> <56C877E3.1090904@cuhka.com> Message-ID: Hi Stephen; Thanks for the documentationing it. 21 ?ub 2016 21:23 tarihinde "Stephen Winnall" yazd?: > I?ve now got a subclass of javafx.application.Application that runs as an > OSGi service and references other OSGi services under Java 8SE. I?ve tried > to document it on Github (see https://github.com/winnall/OSGiJavaFXUsage) > for the benefit of posterity. > > Let me know if there are any mistakes or improvements required in the - > sparse - documentation. I?m also not very good at Git :-( > > Thanks to Erik de Rijcke, Maurice, Anirvan Sardar and Kevin Rushforth for > their comments, all of which guided me - bouncing off the walls - to the > goal. > > Steve > > > > On 20 Feb 2016, at 20:37, Erik De Rijcke > wrote: > > > > This way only the app will be accessible by other components through the > service registry. The app itself can not have any @reference because it it > is javafx itself that instantiates the app object and not the osgi > declarative services framework (which also takes care of injecting your > dependencies). > > > > The way to work around this in java8 is to take the approach I describe, > as far as I know that is the only workaround to get scr and javafx glued > together. > > > > In javafx 9 this would be fixed by having your service component > implement runnable and use the api described by kevin, as you can reuse the > object created by the osgi framework. > > > > On Sat, Feb 20, 2016 at 3:27 PM, Maurice info at cuhka.com>> wrote: > > That is why the bundle activator creates a bundle-singleton of itself, > that way the app can access the OSGi world. In my case to register itself > as a service. > > > > > > @Override > > public void start(Stage primaryStage) throws Exception { > > .... > > primaryStage.show(); > > > > Dictionary properties = createDictionary(); > > BundleContext bundleContext = > UdooActivator.bundleActivator().getBundleContext(); > > > bundleContext.registerService(com.cuhka.home.application.Application.class, > this, properties); > > } > > > > Maurice. > > Op 20-02-16 om 15:08 schreef Stephen Winnall: > > > > Hi Maurice > > > > I have done something similar, but it has the following drawback in my > view: the class launched (Udoo15App in your case) does not run under OSGi > control, so it has no access to OSGi bundles or services, nor is it > accessible by them. If you don?t need that, you're OK. But I need that > class to be part of the OSGi world because other bundles/services are going > to add parts to the UI as they are instantiated. > > > > Steve > > > > On 20 Feb 2016, at 14:33, Maurice > > wrote: > > > > > > For my OSGi based JavaFX solution on the Udoo Quad (ARM based Linux) I > created a service that publishes the application in the context.The > application does as little as possible. It sets up the primary stage as > fullscreen and puts a stackpane in it. Initially the stackpane displays a > 'boot logo', until the actual desktop bundle is started and registered with > the application. Note that you have to start the application on a separate > thread, as the thread will be blocked. > > > > On Java 8 this means that although the application bundle can't be > updated in a running OSGi container, but that is why the desktop exists. On > startup it registers itself, and thus the application content, with the > application, and when it is stopped it removes the content from the > application. The application has thus rarely to be updated itself. > > > > Regards, > > Maurice. > > > > > > > > public class UdooActivator implements BundleActivator { > > private static UdooActivator activator; > > private BundleContext context; > > > > static UdooActivator bundleActivator() { > > return requireNonNull(activator, "activator not set"); > > } > > > > @Override > > public void start(BundleContext context) throws Exception { > > this.context = context; > > activator = this; > > new Thread(() -> Application.launch(Udoo15App.class), "JavaFX > Desktop launcher").start(); > > } > > > > @Override > > public void stop(BundleContext context) throws Exception { > > Platform.exit(); > > } > > > > public BundleContext getBundleContext() { > > return context; > > } > > } > > > > Op 20-02-16 om 01:28 schreef Stephen Winnall: > > Anirvan, Kevin > > > > Thanks for this. > > > > I?m an expert neither in JavaFX nor in OSGi, but I think the basis of > the JavaFX/OSGi incompatibility is control. To work with OSGi, JavaFX has > to relinquish control of its startup sequence to OSGi in such a way that > javafx.application.Application (or its proxy) is instantiated by OSGi and > submits to OSGi?s bundle/service lifecycle. AN OSGi expert can probably > formulate this better? > > > > Platform.startup(runnable) /might/ do it. Platform.launch(class) doesn?t > because the object thereby instantiated is always under the control of > JavaFX - and thus not of OSGi. > > > > I?m not comfortable using JFXPanel: if I wanted to use Swing I wouldn?t > be trying to use JavaFX. But thank you for the hint. > > > > Steve > > > > On 19 Feb 2016, at 16:41, Kevin Rushforth > wrote: > > > > And for JDK 9 there is now: > > > > Platform.startup(Runnable); > > > > -- Kevin > > > > > > Anirvan Sarkar wrote: > > Hi Stephen, > > > > FYI, there is another way of initializing JavaFX runtime. Just use: > > > > new JFXPanel(); > > > > It is documented[1] that FX runtime is initialized when the first > JFXPanel > > instance is constructed. > > > > Also JavaFX 9 will provide an official API to start the FX platform [2] > [3]. > > > > > > [1] > > > https://docs.oracle.com/javase/8/javafx/api/javafx/application/Platform.html#runLater-java.lang.Runnable > < > https://docs.oracle.com/javase/8/javafx/api/javafx/application/Platform.html#runLater-java.lang.Runnable> > < > https://docs.oracle.com/javase/8/javafx/api/javafx/application/Platform.html#runLater-java.lang.Runnable > < > https://docs.oracle.com/javase/8/javafx/api/javafx/application/Platform.html#runLater-java.lang.Runnable > >>- > > [2]https://bugs.openjdk.java.net/browse/JDK-8090585 < > https://bugs.openjdk.java.net/browse/JDK-8090585> < > https://bugs.openjdk.java.net/browse/JDK-8090585 < > https://bugs.openjdk.java.net/browse/JDK-8090585>> > > [3] > > > http://download.java.net/jdk9/jfxdocs/javafx/application/Platform.html#startup-java.lang.Runnable > < > http://download.java.net/jdk9/jfxdocs/javafx/application/Platform.html#startup-java.lang.Runnable> > < > http://download.java.net/jdk9/jfxdocs/javafx/application/Platform.html#startup-java.lang.Runnable > < > http://download.java.net/jdk9/jfxdocs/javafx/application/Platform.html#startup-java.lang.Runnable > >>- > > > > > > On 18 February 2016 at 20:08, Stephen Winnall steve at winnall.ch>> > > wrote: > > > > > > As I understand it, there are two ways of activating JavaFX: > > > > 1) sub-class javafx.application.Application or > > 2) call javafx.application.Application.launch() > > > > > > > > > > > > Op 20-02-16 om 01:28 schreef Stephen Winnall: > > Anirvan, Kevin > > > > Thanks for this. > > > > I?m an expert neither in JavaFX nor in OSGi, but I think the basis of > the JavaFX/OSGi incompatibility is control. To work with OSGi, JavaFX has > to relinquish control of its startup sequence to OSGi in such a way that > javafx.application.Application (or its proxy) is instantiated by OSGi and > submits to OSGi?s bundle/service lifecycle. AN OSGi expert can probably > formulate this better? > > > > Platform.startup(runnable) /might/ do it. Platform.launch(class) doesn?t > because the object thereby instantiated is always under the control of > JavaFX - and thus not of OSGi. > > > > I?m not comfortable using JFXPanel: if I wanted to use Swing I wouldn?t > be trying to use JavaFX. But thank you for the hint. > > > > Steve > > > > On 19 Feb 2016, at 16:41, Kevin Rushforth > wrote: > > > > And for JDK 9 there is now: > > > > Platform.startup(Runnable); > > > > -- Kevin > > > > > > Anirvan Sarkar wrote: > > Hi Stephen, > > > > FYI, there is another way of initializing JavaFX runtime. Just use: > > > > new JFXPanel(); > > > > It is documented[1] that FX runtime is initialized when the first > JFXPanel > > instance is constructed. > > > > Also JavaFX 9 will provide an official API to start the FX platform [2] > [3]. > > > > > > [1] > > > https://docs.oracle.com/javase/8/javafx/api/javafx/application/Platform.html#runLater-java.lang.Runnable > < > https://docs.oracle.com/javase/8/javafx/api/javafx/application/Platform.html#runLater-java.lang.Runnable> > < > https://docs.oracle.com/javase/8/javafx/api/javafx/application/Platform.html#runLater-java.lang.Runnable > < > https://docs.oracle.com/javase/8/javafx/api/javafx/application/Platform.html#runLater-java.lang.Runnable > >>- > > [2] https://bugs.openjdk.java.net/browse/JDK-8090585 < > https://bugs.openjdk.java.net/browse/JDK-8090585> < > https://bugs.openjdk.java.net/browse/JDK-8090585 < > https://bugs.openjdk.java.net/browse/JDK-8090585>> > > [3] > > > http://download.java.net/jdk9/jfxdocs/javafx/application/Platform.html#startup-java.lang.Runnable > < > http://download.java.net/jdk9/jfxdocs/javafx/application/Platform.html#startup-java.lang.Runnable> > < > http://download.java.net/jdk9/jfxdocs/javafx/application/Platform.html#startup-java.lang.Runnable > < > http://download.java.net/jdk9/jfxdocs/javafx/application/Platform.html#startup-java.lang.Runnable > >>- > > > > > > On 18 February 2016 at 20:08, Stephen Winnall steve at winnall.ch>> > > wrote: > > > > > > As I understand it, there are two ways of activating JavaFX: > > > > 1) sub-class javafx.application.Application or > > 2) call javafx.application.Application.launch() > > > > > > > > > > > > > > From powers.anirvan at gmail.com Mon Feb 22 05:43:05 2016 From: powers.anirvan at gmail.com (Anirvan Sarkar) Date: Mon, 22 Feb 2016 11:13:05 +0530 Subject: JEP 283: Enable GTK 3 on Linux In-Reply-To: <56C75A94.8040504@oracle.com> References: <20160219014148.103A499C4F@eggemoggin.niobe.net> <56C73821.7030808@oracle.com> <56C75A94.8040504@oracle.com> Message-ID: Hi Kevin, Phil, Thanks for the clarification. On 19 February 2016 at 23:40, Phil Race wrote: > We had not forgotten that the other JEP was there (as a draft) > but the new JEP started with a pure FX focus on allowing FX to use either > GTK2 or GTK3 depending on what you needed. > It was extended (feature creep) whilst being drafted to include doing the > same for > AWT/Swing but the focus was still on interoperability. Making the Swing > L&F fully GTK3 based is the later stretch goal whereas the original JEP > is much more focused on that and also not at all on FX. > It would be good for Mario to take a look at the new JEP and identify > any areas in which it falls short of the previous JEP, which would be > one reason to leave the "old" JEP open for now. Another is that it > is unclear how much of JEP 283 we will actually be able to deliver for > JDK 9 and it is written in a way which is intended to allow for that. > In which case the previous JEP may yet be needed to complete that work, > so we don't know yet it if it will be completely subsumed by that work. > > -phil. > > > On 02/19/2016 07:43 AM, Kevin Rushforth wrote: > >> Current plan is to track all of the work for both JavaFX and Swing with >> this JEP. >> >> -- Kevin >> >> >> Anirvan Sarkar wrote: >> >>> Hi, >>> >>> One of the sub-task of this JEP is to 'Rework Swing GTK LnF to support >>> GTK-3'. >>> This seems something in common with another submitted JEP [1]: 'Modernize >>> the GTK3 Look and Feel implementation'. >>> >>> So will these two JEP complement each other or will the other one be now >>> redundant ? >>> >>> >>> [1] https://bugs.openjdk.java.net/browse/JDK-8065658 >>> >>> On 19 February 2016 at 07:11, wrote: >>> >>> New JEP Candidate: http://openjdk.java.net/jeps/283 >>>> >>>> - Mark >>>> >>>> >>> >>> >>> > -- Anirvan From info at cuhka.com Mon Feb 22 13:48:58 2016 From: info at cuhka.com (Maurice) Date: Mon, 22 Feb 2016 14:48:58 +0100 Subject: 0x3003: Could not get EGL surface Message-ID: <56CB11CA.9060400@cuhka.com> Even though the system did not output to my LVDS screen JavaFX seemed to be content initializing with ES2. GLFactory using com.sun.prism.es2.MonocleGLFactory (X) Got class = class com.sun.prism.es2.ES2Pipeline Initialized prism pipeline: com.sun.prism.es2.ES2Pipeline Graphics Vendor: Vivante Corporation Renderer: Vivante GC2000 Version: OpenGL ES 3.0 V5.0.11.p7.33433 vsync: true vpipe: true I've fixed getting output to LVDS, unfortunately, I now get a 0x3003 error when JavaFX starts. Prism pipeline name = com.sun.prism.es2.ES2Pipeline Loading ES2 native library ... prism_es2_monocle succeeded. GLFactory using com.sun.prism.es2.MonocleGLFactory traceConfig: Trying platform MX6 with class com.sun.glass.ui.monocle.MX6Platform Factory traceConfig: Matched MX6 com.sun.glass.ui.monocle.GLException: 0x3003: Could not get EGL surface at com.sun.glass.ui.monocle.AcceleratedScreen.(AcceleratedScreen. Here's somebody who at least got the same error[1], but there is no follow up on the thread. What configuration change should I be paying attention at? [1] https://community.freescale.com/thread/380842 From neugens at redhat.com Tue Feb 23 08:11:28 2016 From: neugens at redhat.com (Mario Torre) Date: Tue, 23 Feb 2016 09:11:28 +0100 Subject: JEP 283: Enable GTK 3 on Linux In-Reply-To: <56C75A94.8040504@oracle.com> References: <20160219014148.103A499C4F@eggemoggin.niobe.net> <56C73821.7030808@oracle.com> <56C75A94.8040504@oracle.com> Message-ID: Hi Phil, Kevin, On Fri, Feb 19, 2016 at 7:10 PM, Phil Race wrote: > We had not forgotten that the other JEP was there (as a draft) > but the new JEP started with a pure FX focus on allowing FX to use either > GTK2 or GTK3 depending on what you needed. > It was extended (feature creep) whilst being drafted to include doing the > same for > AWT/Swing but the focus was still on interoperability. Making the Swing > L&F fully GTK3 based is the later stretch goal whereas the original JEP > is much more focused on that and also not at all on FX. > It would be good for Mario to take a look at the new JEP and identify > any areas in which it falls short of the previous JEP, which would be > one reason to leave the "old" JEP open for now. Another is that it > is unclear how much of JEP 283 we will actually be able to deliver for > JDK 9 and it is written in a way which is intended to allow for that. > In which case the previous JEP may yet be needed to complete that work, > so we don't know yet it if it will be completely subsumed by that work. The fact that you're doing this is an awesome, awesome news! :) I think there's quite some overlap between my proposal and this JEP. I admit I didn't do a lot of progress, but I didn't just write the JEP and forget, so I do have some working code and things start to have something to look at. My take on this was to proceed with a fully clean room implementation and only use cairo+gtk, since there's just too much stuff being deprecate or removed that doesn't make sense to keep around. I've been ld-loading all the functions and redefining the types (most as typedefs to void pointers, sometime copying the enums or constants values) as I touch them. The task is not straightforward and unless you have somebody full time I doubt the GTK3 Laf will be included 9, but since it's entirely possible to get this done as a pluggable laf in fact anyone can benefit as soon as it's ready. A couple of problems that I have are about the choice between gtk2 and gtk3, I wasn't yet able to properly unload and reload the correct version reliably, so the idea of the startup switch is very good, it's also good to coordinate with the javafx team since it's paramount that OpenJDK and JavaFX load the same library under the hood. I'll be happy to talk with who is actually doing this work and sync on my progress and either hand it over or help out myself. As for keeping the "old" JEP around, I don't think it's needed, but it depends on how the 283 turns out, perhaps we can retire mine and revive it if it's needed at a later point, or make it a subtask (like it has been done with jigsaw) of the main one, I leave this up to you I don't have problems either way. One thing, I strongly believe that we should keep GTK2 around for a bit longer. Cheers, Mario From a.ankit.srivastava at oracle.com Tue Feb 23 08:35:45 2016 From: a.ankit.srivastava at oracle.com (Ankit Srivastava) Date: Tue, 23 Feb 2016 00:35:45 -0800 (PST) Subject: FW: [9] Review request for 8133775 : Some WebNode tests crash JVM In-Reply-To: References: Message-ID: <20d71af5-1cf6-4599-8558-3c11b8a4a500@default> Hi Murali, Kevin, Alexander, Please review the webrev : http://cr.openjdk.java.net/~arajkumar/ankit/8133775/webrev.00/ JBS: https://bugs.openjdk.java.net/browse/JDK-8133775 Changes: 1) Made "checkEventThread()" function public to make it accessible to JSObject class which is in different package and is not a derived class of Invoker. 2) Added check to throw exception instead of JVM crash if functions are called from non-jfx thread. Reference : https://docs.oracle.com/javafx/2/api/javafx/scene/web/WebEngine.html Verified on Linux 64 machine with changes , exception is being thrown instead of JVM crash. On Windows 64 JVM doesn't crash previously, with code changes exception will be thrown. Regards, Ankit From chris.bensen at oracle.com Tue Feb 23 21:37:21 2016 From: chris.bensen at oracle.com (Chris Bensen) Date: Tue, 23 Feb 2016 13:37:21 -0800 Subject: Review Request: 8148978 [packager] bootmodules.jimage was renamed to modules Message-ID: Hi David, Please review this change to take into account the recent change to JLINK to rename bootmodules.jimage to modules. There?s a bit more in this change as well to just get the packager CLI working in general. JIRA: https://bugs.openjdk.java.net/browse/JDK-8148978 Webrev: http://cr.openjdk.java.net/~cbensen/JDK-8148978/webrev.00 Thanks, Chris From vadim.pakhnushev at oracle.com Wed Feb 24 14:53:00 2016 From: vadim.pakhnushev at oracle.com (Vadim Pakhnushev) Date: Wed, 24 Feb 2016 17:53:00 +0300 Subject: [9] Review request for 8150536: Cleanup indentation Message-ID: <56CDC3CC.7010000@oracle.com> Kevin, Could you please take a look at the fix: https://bugs.openjdk.java.net/browse/JDK-8150536 http://cr.openjdk.java.net/~vadim/8150536/webrev.00/ Thanks, Vadim From vadim.pakhnushev at oracle.com Wed Feb 24 14:53:39 2016 From: vadim.pakhnushev at oracle.com (Vadim Pakhnushev) Date: Wed, 24 Feb 2016 17:53:39 +0300 Subject: [9] Review request for 8088486: Fix compiler warning related to hlsl files Message-ID: <56CDC3F3.4050801@oracle.com> Jim, Chien, Could you please take a look at the fix: https://bugs.openjdk.java.net/browse/JDK-8088486 http://cr.openjdk.java.net/~vadim/8088486/webrev.00/ Thanks, Vadim From David.Hill at Oracle.com Thu Feb 25 20:30:27 2016 From: David.Hill at Oracle.com (David Hill) Date: Thu, 25 Feb 2016 15:30:27 -0500 Subject: review: enable debugging info in linux shared libs Message-ID: <56CF6463.8070506@Oracle.com> Hi Kevin, There is a simple diff in the bug. https://bugs.openjdk.java.net/browse/JDK-8150673 -- David Hill Java Embedded Development "A man's feet should be planted in his country, but his eyes should survey the world." -- George Santayana (1863 - 1952) From tom.schindl at bestsolution.at Thu Feb 25 22:31:26 2016 From: tom.schindl at bestsolution.at (Tom Schindl) Date: Thu, 25 Feb 2016 23:31:26 +0100 Subject: Mac OSX and German Keyboard Layout (Y/Z) In-Reply-To: <56A220C9.8030104@bestsolution.at> References: <56A220C9.8030104@bestsolution.at> Message-ID: <56CF80BE.3060507@bestsolution.at> Hi, Anyone any insights? Any Swing Savy dev around who knows how Swing manages to deliver the right key? Tom On 22.01.16 13:30, Tom Schindl wrote: > Hi, > > I just discovered that the KeyCode reported by JavaFX on OS-X with a > german keyboard layout (where eg z and y are interchanged) is wrong. > > If you press a Z you get as the KeyCode.Y and for Y you get KeyCode.Z - > this Y/Z problem. I don't think that I as a java-dev need to deal with > that and if you look at other toolkits (swing, swt) they handle this > transparently for me! > > I've attached you a javafx and swing application and you'll notice that > swing reports always the correct keycode (no matter if my keyboard > layout is english or german) and javafx is wrong on german keyboards. > > > FX: >> package application; >> >> import javafx.application.Application; >> import javafx.scene.Scene; >> import javafx.scene.control.TextField; >> import javafx.scene.layout.BorderPane; >> import javafx.stage.Stage; >> >> >> public class Main extends Application { >> @Override >> public void start(Stage primaryStage) { >> try { >> BorderPane root = new BorderPane(); >> >> TextField f = new TextField(); >> f.setOnKeyPressed( e -> { >> System.err.println("KeyCode: " + e.getCode()); >> }); >> >> root.setCenter(f); >> >> Scene scene = new Scene(root,400,400); >> primaryStage.setScene(scene); >> primaryStage.show(); >> } catch(Exception e) { >> e.printStackTrace(); >> } >> } >> >> public static void main(String[] args) { >> launch(args); >> } >> } > > Swing: >> package application; >> >> import java.awt.event.KeyEvent; >> import java.awt.event.KeyListener; >> >> import javax.swing.JFrame; >> import javax.swing.JTextField; >> >> public class SampleSwing extends JFrame { >> public SampleSwing() { >> JTextField textField = new JTextField(); >> textField.addKeyListener(new KeyListener() { >> >> @Override >> public void keyTyped(KeyEvent e) { >> // TODO Auto-generated method stub >> >> } >> >> @Override >> public void keyReleased(KeyEvent e) { >> // TODO Auto-generated method stub >> >> } >> >> @Override >> public void keyPressed(KeyEvent e) { >> System.err.println((char)e.getKeyCode()); >> } >> }); >> getContentPane().add(textField); >> } >> >> public static void main(String[] args) { >> new SampleSwing().setVisible(true); >> >> } >> } > > > > Tom > -- Thomas Schindl, CTO BestSolution.at EDV Systemhaus GmbH Eduard-Bodem-Gasse 5-7, A-6020 Innsbruck http://www.bestsolution.at/ Reg. Nr. FN 222302s am Firmenbuchgericht Innsbruck From hastebrot at gmail.com Thu Feb 25 22:39:13 2016 From: hastebrot at gmail.com (Benjamin Gudehus) Date: Thu, 25 Feb 2016 23:39:13 +0100 Subject: Mac OSX and German Keyboard Layout (Y/Z) In-Reply-To: <56CF80BE.3060507@bestsolution.at> References: <56A220C9.8030104@bestsolution.at> <56CF80BE.3060507@bestsolution.at> Message-ID: FWIW: `KeyEvent` in `keyTyped` should return a String with the right key, i.e. "z" for German keyboard Z key. --Benjamin On Thu, Feb 25, 2016 at 11:31 PM, Tom Schindl wrote: > Hi, > > Anyone any insights? Any Swing Savy dev around who knows how Swing > manages to deliver the right key? > > Tom > > On 22.01.16 13:30, Tom Schindl wrote: > > Hi, > > > > I just discovered that the KeyCode reported by JavaFX on OS-X with a > > german keyboard layout (where eg z and y are interchanged) is wrong. > > > > If you press a Z you get as the KeyCode.Y and for Y you get KeyCode.Z - > > this Y/Z problem. I don't think that I as a java-dev need to deal with > > that and if you look at other toolkits (swing, swt) they handle this > > transparently for me! > > > > I've attached you a javafx and swing application and you'll notice that > > swing reports always the correct keycode (no matter if my keyboard > > layout is english or german) and javafx is wrong on german keyboards. > > > > > > FX: > >> package application; > >> > >> import javafx.application.Application; > >> import javafx.scene.Scene; > >> import javafx.scene.control.TextField; > >> import javafx.scene.layout.BorderPane; > >> import javafx.stage.Stage; > >> > >> > >> public class Main extends Application { > >> @Override > >> public void start(Stage primaryStage) { > >> try { > >> BorderPane root = new BorderPane(); > >> > >> TextField f = new TextField(); > >> f.setOnKeyPressed( e -> { > >> System.err.println("KeyCode: " + > e.getCode()); > >> }); > >> > >> root.setCenter(f); > >> > >> Scene scene = new Scene(root,400,400); > >> primaryStage.setScene(scene); > >> primaryStage.show(); > >> } catch(Exception e) { > >> e.printStackTrace(); > >> } > >> } > >> > >> public static void main(String[] args) { > >> launch(args); > >> } > >> } > > > > Swing: > >> package application; > >> > >> import java.awt.event.KeyEvent; > >> import java.awt.event.KeyListener; > >> > >> import javax.swing.JFrame; > >> import javax.swing.JTextField; > >> > >> public class SampleSwing extends JFrame { > >> public SampleSwing() { > >> JTextField textField = new JTextField(); > >> textField.addKeyListener(new KeyListener() { > >> > >> @Override > >> public void keyTyped(KeyEvent e) { > >> // TODO Auto-generated method stub > >> > >> } > >> > >> @Override > >> public void keyReleased(KeyEvent e) { > >> // TODO Auto-generated method stub > >> > >> } > >> > >> @Override > >> public void keyPressed(KeyEvent e) { > >> System.err.println((char)e.getKeyCode()); > >> } > >> }); > >> getContentPane().add(textField); > >> } > >> > >> public static void main(String[] args) { > >> new SampleSwing().setVisible(true); > >> > >> } > >> } > > > > > > > > Tom > > > > > -- > Thomas Schindl, CTO > BestSolution.at EDV Systemhaus GmbH > Eduard-Bodem-Gasse 5-7, A-6020 Innsbruck > http://www.bestsolution.at/ > Reg. Nr. FN 222302s am Firmenbuchgericht Innsbruck > From kevin.rushforth at oracle.com Fri Feb 26 01:39:10 2016 From: kevin.rushforth at oracle.com (Kevin Rushforth) Date: Fri, 26 Feb 2016 07:09:10 +0530 Subject: Mac OSX and German Keyboard Layout (Y/Z) In-Reply-To: <56CF80BE.3060507@bestsolution.at> References: <56A220C9.8030104@bestsolution.at> <56CF80BE.3060507@bestsolution.at> Message-ID: <56CFACBE.1040505@oracle.com> Hi Tom, Please file a bug so we can look at it. Thanks. -- Kevin Tom Schindl wrote: > Hi, > > Anyone any insights? Any Swing Savy dev around who knows how Swing > manages to deliver the right key? > > Tom > > On 22.01.16 13:30, Tom Schindl wrote: > >> Hi, >> >> I just discovered that the KeyCode reported by JavaFX on OS-X with a >> german keyboard layout (where eg z and y are interchanged) is wrong. >> >> If you press a Z you get as the KeyCode.Y and for Y you get KeyCode.Z - >> this Y/Z problem. I don't think that I as a java-dev need to deal with >> that and if you look at other toolkits (swing, swt) they handle this >> transparently for me! >> >> I've attached you a javafx and swing application and you'll notice that >> swing reports always the correct keycode (no matter if my keyboard >> layout is english or german) and javafx is wrong on german keyboards. >> >> >> FX: >> >>> package application; >>> >>> import javafx.application.Application; >>> import javafx.scene.Scene; >>> import javafx.scene.control.TextField; >>> import javafx.scene.layout.BorderPane; >>> import javafx.stage.Stage; >>> >>> >>> public class Main extends Application { >>> @Override >>> public void start(Stage primaryStage) { >>> try { >>> BorderPane root = new BorderPane(); >>> >>> TextField f = new TextField(); >>> f.setOnKeyPressed( e -> { >>> System.err.println("KeyCode: " + e.getCode()); >>> }); >>> >>> root.setCenter(f); >>> >>> Scene scene = new Scene(root,400,400); >>> primaryStage.setScene(scene); >>> primaryStage.show(); >>> } catch(Exception e) { >>> e.printStackTrace(); >>> } >>> } >>> >>> public static void main(String[] args) { >>> launch(args); >>> } >>> } >>> >> Swing: >> >>> package application; >>> >>> import java.awt.event.KeyEvent; >>> import java.awt.event.KeyListener; >>> >>> import javax.swing.JFrame; >>> import javax.swing.JTextField; >>> >>> public class SampleSwing extends JFrame { >>> public SampleSwing() { >>> JTextField textField = new JTextField(); >>> textField.addKeyListener(new KeyListener() { >>> >>> @Override >>> public void keyTyped(KeyEvent e) { >>> // TODO Auto-generated method stub >>> >>> } >>> >>> @Override >>> public void keyReleased(KeyEvent e) { >>> // TODO Auto-generated method stub >>> >>> } >>> >>> @Override >>> public void keyPressed(KeyEvent e) { >>> System.err.println((char)e.getKeyCode()); >>> } >>> }); >>> getContentPane().add(textField); >>> } >>> >>> public static void main(String[] args) { >>> new SampleSwing().setVisible(true); >>> >>> } >>> } >>> >> >> Tom >> >> > > > From tom.schindl at bestsolution.at Fri Feb 26 08:05:15 2016 From: tom.schindl at bestsolution.at (Tom Schindl) Date: Fri, 26 Feb 2016 09:05:15 +0100 Subject: Mac OSX and German Keyboard Layout (Y/Z) In-Reply-To: <56CFACBE.1040505@oracle.com> References: <56A220C9.8030104@bestsolution.at> <56CF80BE.3060507@bestsolution.at> <56CFACBE.1040505@oracle.com> Message-ID: <56D0073B.3010707@bestsolution.at> Hi Kevin, I filed https://bugs.openjdk.java.net/browse/JDK-8150709 Tom On 26.02.16 02:39, Kevin Rushforth wrote: > Hi Tom, > > Please file a bug so we can look at it. > > Thanks. > > -- Kevin > > > Tom Schindl wrote: >> Hi, >> >> Anyone any insights? Any Swing Savy dev around who knows how Swing >> manages to deliver the right key? >> >> Tom >> >> On 22.01.16 13:30, Tom Schindl wrote: >> >>> Hi, >>> >>> I just discovered that the KeyCode reported by JavaFX on OS-X with a >>> german keyboard layout (where eg z and y are interchanged) is wrong. >>> >>> If you press a Z you get as the KeyCode.Y and for Y you get KeyCode.Z - >>> this Y/Z problem. I don't think that I as a java-dev need to deal with >>> that and if you look at other toolkits (swing, swt) they handle this >>> transparently for me! >>> >>> I've attached you a javafx and swing application and you'll notice that >>> swing reports always the correct keycode (no matter if my keyboard >>> layout is english or german) and javafx is wrong on german keyboards. >>> >>> >>> FX: >>> >>>> package application; >>>> >>>> import javafx.application.Application; >>>> import javafx.scene.Scene; >>>> import javafx.scene.control.TextField; >>>> import javafx.scene.layout.BorderPane; >>>> import javafx.stage.Stage; >>>> >>>> >>>> public class Main extends Application { >>>> @Override >>>> public void start(Stage primaryStage) { >>>> try { >>>> BorderPane root = new BorderPane(); >>>> >>>> TextField f = new TextField(); >>>> f.setOnKeyPressed( e -> { >>>> System.err.println("KeyCode: " + e.getCode()); >>>> }); >>>> >>>> root.setCenter(f); >>>> >>>> Scene scene = new Scene(root,400,400); >>>> primaryStage.setScene(scene); >>>> primaryStage.show(); >>>> } catch(Exception e) { >>>> e.printStackTrace(); >>>> } >>>> } >>>> >>>> public static void main(String[] args) { >>>> launch(args); >>>> } >>>> } >>>> >>> Swing: >>> >>>> package application; >>>> >>>> import java.awt.event.KeyEvent; >>>> import java.awt.event.KeyListener; >>>> >>>> import javax.swing.JFrame; >>>> import javax.swing.JTextField; >>>> >>>> public class SampleSwing extends JFrame { >>>> public SampleSwing() { >>>> JTextField textField = new JTextField(); >>>> textField.addKeyListener(new KeyListener() { >>>> >>>> @Override >>>> public void keyTyped(KeyEvent e) { >>>> // TODO Auto-generated method stub >>>> >>>> } >>>> >>>> @Override >>>> public void keyReleased(KeyEvent e) { >>>> // TODO Auto-generated method stub >>>> >>>> } >>>> >>>> @Override >>>> public void keyPressed(KeyEvent e) { >>>> System.err.println((char)e.getKeyCode()); >>>> } >>>> }); >>>> getContentPane().add(textField); >>>> } >>>> >>>> public static void main(String[] args) { >>>> new SampleSwing().setVisible(true); >>>> >>>> } >>>> } >>>> >>> >>> Tom >>> >>> >> >> >> -- Thomas Schindl, CTO BestSolution.at EDV Systemhaus GmbH Eduard-Bodem-Gasse 5-7, A-6020 Innsbruck http://www.bestsolution.at/ Reg. Nr. FN 222302s am Firmenbuchgericht Innsbruck From kevin.rushforth at oracle.com Fri Feb 26 08:14:38 2016 From: kevin.rushforth at oracle.com (Kevin Rushforth) Date: Fri, 26 Feb 2016 13:44:38 +0530 Subject: Mac OSX and German Keyboard Layout (Y/Z) In-Reply-To: <56D0073B.3010707@bestsolution.at> References: <56A220C9.8030104@bestsolution.at> <56CF80BE.3060507@bestsolution.at> <56CFACBE.1040505@oracle.com> <56D0073B.3010707@bestsolution.at> Message-ID: <56D0096E.8020907@oracle.com> Thanks, Tom. -- Kevin Tom Schindl wrote: > Hi Kevin, > > I filed https://bugs.openjdk.java.net/browse/JDK-8150709 > > Tom > > On 26.02.16 02:39, Kevin Rushforth wrote: > >> Hi Tom, >> >> Please file a bug so we can look at it. >> >> Thanks. >> >> -- Kevin >> >> >> Tom Schindl wrote: >> >>> Hi, >>> >>> Anyone any insights? Any Swing Savy dev around who knows how Swing >>> manages to deliver the right key? >>> >>> Tom >>> >>> On 22.01.16 13:30, Tom Schindl wrote: >>> >>> >>>> Hi, >>>> >>>> I just discovered that the KeyCode reported by JavaFX on OS-X with a >>>> german keyboard layout (where eg z and y are interchanged) is wrong. >>>> >>>> If you press a Z you get as the KeyCode.Y and for Y you get KeyCode.Z - >>>> this Y/Z problem. I don't think that I as a java-dev need to deal with >>>> that and if you look at other toolkits (swing, swt) they handle this >>>> transparently for me! >>>> >>>> I've attached you a javafx and swing application and you'll notice that >>>> swing reports always the correct keycode (no matter if my keyboard >>>> layout is english or german) and javafx is wrong on german keyboards. >>>> >>>> >>>> FX: >>>> >>>> >>>>> package application; >>>>> >>>>> import javafx.application.Application; >>>>> import javafx.scene.Scene; >>>>> import javafx.scene.control.TextField; >>>>> import javafx.scene.layout.BorderPane; >>>>> import javafx.stage.Stage; >>>>> >>>>> >>>>> public class Main extends Application { >>>>> @Override >>>>> public void start(Stage primaryStage) { >>>>> try { >>>>> BorderPane root = new BorderPane(); >>>>> >>>>> TextField f = new TextField(); >>>>> f.setOnKeyPressed( e -> { >>>>> System.err.println("KeyCode: " + e.getCode()); >>>>> }); >>>>> >>>>> root.setCenter(f); >>>>> >>>>> Scene scene = new Scene(root,400,400); >>>>> primaryStage.setScene(scene); >>>>> primaryStage.show(); >>>>> } catch(Exception e) { >>>>> e.printStackTrace(); >>>>> } >>>>> } >>>>> >>>>> public static void main(String[] args) { >>>>> launch(args); >>>>> } >>>>> } >>>>> >>>>> >>>> Swing: >>>> >>>> >>>>> package application; >>>>> >>>>> import java.awt.event.KeyEvent; >>>>> import java.awt.event.KeyListener; >>>>> >>>>> import javax.swing.JFrame; >>>>> import javax.swing.JTextField; >>>>> >>>>> public class SampleSwing extends JFrame { >>>>> public SampleSwing() { >>>>> JTextField textField = new JTextField(); >>>>> textField.addKeyListener(new KeyListener() { >>>>> >>>>> @Override >>>>> public void keyTyped(KeyEvent e) { >>>>> // TODO Auto-generated method stub >>>>> >>>>> } >>>>> >>>>> @Override >>>>> public void keyReleased(KeyEvent e) { >>>>> // TODO Auto-generated method stub >>>>> >>>>> } >>>>> >>>>> @Override >>>>> public void keyPressed(KeyEvent e) { >>>>> System.err.println((char)e.getKeyCode()); >>>>> } >>>>> }); >>>>> getContentPane().add(textField); >>>>> } >>>>> >>>>> public static void main(String[] args) { >>>>> new SampleSwing().setVisible(true); >>>>> >>>>> } >>>>> } >>>>> >>>>> >>>> Tom >>>> >>>> >>>> >>> >>> > > > From vadim.pakhnushev at oracle.com Fri Feb 26 15:19:27 2016 From: vadim.pakhnushev at oracle.com (Vadim Pakhnushev) Date: Fri, 26 Feb 2016 18:19:27 +0300 Subject: In(Sanity) Testing Mondays Message-ID: <56D06CFF.1090900@oracle.com> Reminder, Monday is our weekly sanity testing. You can find your testing assignment at: https://wiki.openjdk.java.net/display/OpenJFX/Sanity+Testing Also please remember that the repo will be locked from 1am PST until 1pm PST. Happy testing! Thanks, Vadim From info at cuhka.com Sat Feb 27 18:10:44 2016 From: info at cuhka.com (Maurice) Date: Sat, 27 Feb 2016 19:10:44 +0100 Subject: Internal error: Error loading stock shader FillRoundRect_LinearGradient,_PAD on Vivante ARM Message-ID: <56D1E6A4.80301@cuhka.com> I'm running into the following exception when I start a simple JavaFX test program on my ARM based board: Shader compile log: (21:0) : error : In declarations of global variables with no storage qualifier or with a const qualifier, any initializer must be a constant expression (103:0) : error : undefined identifier: 'pixcoord' java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at com.sun.prism.es2.ES2ResourceFactory.createStockShader(ES2ResourceFac tory.java:312) at com.sun.prism.impl.ps.BaseShaderContext.getPaintShader(BaseShaderCont ext.java:256) at com.sun.prism.impl.ps.BaseShaderContext.validatePaintOp(BaseShaderCon text.java:477) at com.sun.prism.impl.ps.BaseShaderContext.validatePaintOp(BaseShaderCon text.java:374) at com.sun.prism.impl.ps.BaseShaderGraphics.renderGeneralRoundedPgram(Ba seShaderGraphics.java:842) at com.sun.prism.impl.ps.BaseShaderGraphics.renderGeneralRoundedRect(Bas eShaderGraphics.java:601) at com.sun.prism.impl.ps.BaseShaderGraphics.fillRoundRect(BaseShaderGrap hics.java:1557) at com.sun.javafx.sg.prism.NGRegion.renderBackgroundRectanglesDirectly(N GRegion.java:1119) at com.sun.javafx.sg.prism.NGRegion.renderBackgroundRectangle(NGRegion.j ava:830) at com.sun.javafx.sg.prism.NGRegion.renderAsRectangle(NGRegion.java:751) at com.sun.javafx.sg.prism.NGRegion.renderContent(NGRegion.java:572) at com.sun.javafx.sg.prism.NGNode.doRender(NGNode.java:2053) at com.sun.javafx.sg.prism.NGNode.render(NGNode.java:1945) at com.sun.javafx.sg.prism.NGGroup.renderContent(NGGroup.java:235) at com.sun.javafx.sg.prism.NGNode.doRender(NGNode.java:2053) at com.sun.javafx.sg.prism.NGNode.render(NGNode.java:1945) at com.sun.javafx.tk.quantum.ViewPainter.doPaint(ViewPainter.java:477) at com.sun.javafx.tk.quantum.ViewPainter.paintImpl(ViewPainter.java:330) at com.sun.javafx.tk.quantum.PresentingPainter.run(PresentingPainter.jav a:91) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:51 1) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at com.sun.javafx.tk.RenderJob.run(RenderJob.java:58) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor. java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor .java:617) at com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.run(Quantu mRenderer.java:125) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.RuntimeException: Error creating fragment shader at com.sun.prism.es2.ES2Shader.createFromSource(ES2Shader.java:141) at com.sun.prism.es2.ES2Shader.createFromSource(ES2Shader.java:173) at com.sun.prism.es2.ES2ResourceFactory.createShader(ES2ResourceFactory. java:224) at com.sun.prism.shader.FillRoundRect_LinearGradient_PAD_Loader.loadShad er(FillRoundRect_LinearGradient_PAD_Loader.java:53) ... 30 more java.lang.InternalError: Error loading stock shader FillRoundRect_LinearGradient _PAD at com.sun.prism.es2.ES2ResourceFactory.createStockShader(ES2ResourceFac tory.java:315) at com.sun.prism.impl.ps.BaseShaderContext.getPaintShader(BaseShaderCont ext.java:256) at com.sun.prism.impl.ps.BaseShaderContext.validatePaintOp(BaseShaderCon text.java:477) at com.sun.prism.impl.ps.BaseShaderContext.validatePaintOp(BaseShaderCon text.java:374) at com.sun.prism.impl.ps.BaseShaderGraphics.renderGeneralRoundedPgram(Ba seShaderGraphics.java:842) at com.sun.prism.impl.ps.BaseShaderGraphics.renderGeneralRoundedRect(Bas eShaderGraphics.java:601) at com.sun.prism.impl.ps.BaseShaderGraphics.fillRoundRect(BaseShaderGrap hics.java:1557) at com.sun.javafx.sg.prism.NGRegion.renderBackgroundRectanglesDirectly(N GRegion.java:1119) at com.sun.javafx.sg.prism.NGRegion.renderBackgroundRectangle(NGRegion.j ava:830) at com.sun.javafx.sg.prism.NGRegion.renderAsRectangle(NGRegion.java:751) at com.sun.javafx.sg.prism.NGRegion.renderContent(NGRegion.java:572) at com.sun.javafx.sg.prism.NGNode.doRender(NGNode.java:2053) at com.sun.javafx.sg.prism.NGNode.render(NGNode.java:1945) at com.sun.javafx.sg.prism.NGGroup.renderContent(NGGroup.java:235) at com.sun.javafx.sg.prism.NGNode.doRender(NGNode.java:2053) at com.sun.javafx.sg.prism.NGNode.render(NGNode.java:1945) at com.sun.javafx.tk.quantum.ViewPainter.doPaint(ViewPainter.java:477) at com.sun.javafx.tk.quantum.ViewPainter.paintImpl(ViewPainter.java:330) at com.sun.javafx.tk.quantum.PresentingPainter.run(PresentingPainter.jav a:91) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:51 1) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at com.sun.javafx.tk.RenderJob.run(RenderJob.java:58) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor. java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor .java:617) at com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.run(Quantu mRenderer.java:125) at java.lang.Thread.run(Thread.java:745) Maurice. From info at cuhka.com Sun Feb 28 17:33:53 2016 From: info at cuhka.com (Maurice) Date: Sun, 28 Feb 2016 18:33:53 +0100 Subject: GLS language errors (Was: Internal error: Error loading stock shader FillRoundRect_LinearGradient,_PAD on Vivante ARM) In-Reply-To: <56D1E6A4.80301@cuhka.com> References: <56D1E6A4.80301@cuhka.com> Message-ID: <56D32F81.7060708@cuhka.com> When I run the glslangValidator on FillRoundRect_LinearGradient_PAD.frag it gives the following error: ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es When I move pixcoord's declaration on line 19 into the main() function it gives no errors. This is the full output of find -name "*.frag" -exec glslangValidator {} \; ERROR: 0:53: 'oTexCoords' : undeclared identifier ERROR: 0:53: 'texture2D' : no matching overloaded function found ERROR: 0:53: '=' : cannot convert from 'const float' to 'temp highp 4-component vector of float' ERROR: 3 compilation errors. No code generated. ERROR: 0:55: 'oTexCoords' : undeclared identifier ERROR: 0:55: 'texture2D' : no matching overloaded function found ERROR: 0:55: 'scalar swizzle' : not supported with this profile: es ERROR: 0:55: 'rgb' : vector field selection out of range ERROR: 0:55: '=' : cannot convert from 'const float' to 'temp highp 3-component vector of float' ERROR: 5 compilation errors. No code generated. ERROR: 0:53: 'oTexCoords' : undeclared identifier ERROR: 0:53: 'texture2D' : no matching overloaded function found WARNING: 0:53: 'return' : type conversion on return values was not explicitly allowed until version 420 ERROR: 2 compilation errors. No code generated. ERROR: 0:55: 'oTexCoords' : undeclared identifier ERROR: 0:55: 'texture2D' : no matching overloaded function found ERROR: 0:55: 'scalar swizzle' : not supported with this profile: es ERROR: 0:55: 'rgb' : vector field selection out of range ERROR: 0:55: '=' : cannot convert from 'const float' to 'temp highp 3-component vector of float' ERROR: 5 compilation errors. No code generated. ERROR: 0:18: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:18: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:53: 'oTexCoords' : undeclared identifier ERROR: 0:53: 'texture2D' : no matching overloaded function found ERROR: 0:53: '=' : cannot convert from 'const float' to 'temp highp 4-component vector of float' ERROR: 3 compilation errors. No code generated. ERROR: 0:55: 'oTexCoords' : undeclared identifier ERROR: 0:55: 'texture2D' : no matching overloaded function found ERROR: 0:55: 'scalar swizzle' : not supported with this profile: es ERROR: 0:55: 'rgb' : vector field selection out of range ERROR: 0:55: '=' : cannot convert from 'const float' to 'temp highp 3-component vector of float' ERROR: 5 compilation errors. No code generated. ERROR: 0:53: 'oTexCoords' : undeclared identifier ERROR: 0:53: 'texture2D' : no matching overloaded function found WARNING: 0:53: 'return' : type conversion on return values was not explicitly allowed until version 420 ERROR: 2 compilation errors. No code generated. ERROR: 0:55: 'oTexCoords' : undeclared identifier ERROR: 0:55: 'texture2D' : no matching overloaded function found ERROR: 0:55: 'scalar swizzle' : not supported with this profile: es ERROR: 0:55: 'rgb' : vector field selection out of range ERROR: 0:55: '=' : cannot convert from 'const float' to 'temp highp 3-component vector of float' ERROR: 5 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:17: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:17: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:18: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:17: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:18: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:18: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:18: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:18: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:18: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:18: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:17: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:17: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:18: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:17: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:18: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:17: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:17: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:17: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:17: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:17: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:17: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:18: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:18: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:17: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:18: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:18: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:18: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:17: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:18: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:18: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:17: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:17: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:18: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:17: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:18: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:18: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:18: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:18: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:18: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:18: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:17: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:17: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:18: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:17: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:18: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:17: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:17: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:17: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:17: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:17: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:17: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:18: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:18: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:17: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:18: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:18: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:18: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:17: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. ERROR: 0:19: 'non-constant global initializer' : not supported with this profile: es ERROR: 1 compilation errors. No code generated. Op 27-02-16 om 19:10 schreef Maurice: > I'm running into the following exception when I start a simple JavaFX > test program on my ARM based board: > > Shader compile log: (21:0) : error : In declarations of global > variables with no > storage qualifier or with a const qualifier, any initializer must be > a constant > expression > (103:0) : error : undefined identifier: 'pixcoord' > > java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. > java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > sorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at > com.sun.prism.es2.ES2ResourceFactory.createStockShader(ES2ResourceFac > tory.java:312) > at > com.sun.prism.impl.ps.BaseShaderContext.getPaintShader(BaseShaderCont > ext.java:256) > at > com.sun.prism.impl.ps.BaseShaderContext.validatePaintOp(BaseShaderCon > text.java:477) > at > com.sun.prism.impl.ps.BaseShaderContext.validatePaintOp(BaseShaderCon > text.java:374) > at > com.sun.prism.impl.ps.BaseShaderGraphics.renderGeneralRoundedPgram(Ba > seShaderGraphics.java:842) > at > com.sun.prism.impl.ps.BaseShaderGraphics.renderGeneralRoundedRect(Bas > eShaderGraphics.java:601) > at > com.sun.prism.impl.ps.BaseShaderGraphics.fillRoundRect(BaseShaderGrap > hics.java:1557) > at > com.sun.javafx.sg.prism.NGRegion.renderBackgroundRectanglesDirectly(N > GRegion.java:1119) > at > com.sun.javafx.sg.prism.NGRegion.renderBackgroundRectangle(NGRegion.j > ava:830) > at > com.sun.javafx.sg.prism.NGRegion.renderAsRectangle(NGRegion.java:751) > at > com.sun.javafx.sg.prism.NGRegion.renderContent(NGRegion.java:572) > at com.sun.javafx.sg.prism.NGNode.doRender(NGNode.java:2053) > at com.sun.javafx.sg.prism.NGNode.render(NGNode.java:1945) > at > com.sun.javafx.sg.prism.NGGroup.renderContent(NGGroup.java:235) > at com.sun.javafx.sg.prism.NGNode.doRender(NGNode.java:2053) > at com.sun.javafx.sg.prism.NGNode.render(NGNode.java:1945) > at > com.sun.javafx.tk.quantum.ViewPainter.doPaint(ViewPainter.java:477) > at > com.sun.javafx.tk.quantum.ViewPainter.paintImpl(ViewPainter.java:330) > at > com.sun.javafx.tk.quantum.PresentingPainter.run(PresentingPainter.jav > a:91) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:51 > 1) > at > java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) > at com.sun.javafx.tk.RenderJob.run(RenderJob.java:58) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor. > java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor > .java:617) > at > com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.run(Quantu > mRenderer.java:125) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.RuntimeException: Error creating fragment shader > at > com.sun.prism.es2.ES2Shader.createFromSource(ES2Shader.java:141) > at > com.sun.prism.es2.ES2Shader.createFromSource(ES2Shader.java:173) > at > com.sun.prism.es2.ES2ResourceFactory.createShader(ES2ResourceFactory. > java:224) > at > com.sun.prism.shader.FillRoundRect_LinearGradient_PAD_Loader.loadShad > er(FillRoundRect_LinearGradient_PAD_Loader.java:53) > ... 30 more > java.lang.InternalError: Error loading stock shader > FillRoundRect_LinearGradient > _PAD > at > com.sun.prism.es2.ES2ResourceFactory.createStockShader(ES2ResourceFac > tory.java:315) > at > com.sun.prism.impl.ps.BaseShaderContext.getPaintShader(BaseShaderCont > ext.java:256) > at > com.sun.prism.impl.ps.BaseShaderContext.validatePaintOp(BaseShaderCon > text.java:477) > at > com.sun.prism.impl.ps.BaseShaderContext.validatePaintOp(BaseShaderCon > text.java:374) > at > com.sun.prism.impl.ps.BaseShaderGraphics.renderGeneralRoundedPgram(Ba > seShaderGraphics.java:842) > at > com.sun.prism.impl.ps.BaseShaderGraphics.renderGeneralRoundedRect(Bas > eShaderGraphics.java:601) > at > com.sun.prism.impl.ps.BaseShaderGraphics.fillRoundRect(BaseShaderGrap > hics.java:1557) > at > com.sun.javafx.sg.prism.NGRegion.renderBackgroundRectanglesDirectly(N > GRegion.java:1119) > at > com.sun.javafx.sg.prism.NGRegion.renderBackgroundRectangle(NGRegion.j > ava:830) > at > com.sun.javafx.sg.prism.NGRegion.renderAsRectangle(NGRegion.java:751) > at > com.sun.javafx.sg.prism.NGRegion.renderContent(NGRegion.java:572) > at com.sun.javafx.sg.prism.NGNode.doRender(NGNode.java:2053) > at com.sun.javafx.sg.prism.NGNode.render(NGNode.java:1945) > at > com.sun.javafx.sg.prism.NGGroup.renderContent(NGGroup.java:235) > at com.sun.javafx.sg.prism.NGNode.doRender(NGNode.java:2053) > at com.sun.javafx.sg.prism.NGNode.render(NGNode.java:1945) > at > com.sun.javafx.tk.quantum.ViewPainter.doPaint(ViewPainter.java:477) > at > com.sun.javafx.tk.quantum.ViewPainter.paintImpl(ViewPainter.java:330) > at > com.sun.javafx.tk.quantum.PresentingPainter.run(PresentingPainter.jav > a:91) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:51 > 1) > at > java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) > at com.sun.javafx.tk.RenderJob.run(RenderJob.java:58) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor. > java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor > .java:617) > at > com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.run(Quantu > mRenderer.java:125) > at java.lang.Thread.run(Thread.java:745) > > Maurice. From diego.cirujano-cuesta at zeiss.com Sun Feb 28 20:56:39 2016 From: diego.cirujano-cuesta at zeiss.com (Cirujano Cuesta, Diego) Date: Sun, 28 Feb 2016 20:56:39 +0000 Subject: [Review request] 8090477: Customizable visibility timing for Tooltip Message-ID: Hi Jonathan, I saw that was already reviewed, good!. I tested it also and it works like a charm. Thanks, Diego From diego.cirujano-cuesta at zeiss.com Sun Feb 28 21:49:18 2016 From: diego.cirujano-cuesta at zeiss.com (Cirujano Cuesta, Diego) Date: Sun, 28 Feb 2016 21:49:18 +0000 Subject: ProgressIndicator indeterminate transition bugs Message-ID: Hi all, We found two important bugs in ProgressIndicator that are related with the following tickets: https://bugs.openjdk.java.net/browse/JDK-8094829 https://bugs.openjdk.java.net/browse/JDK-8094078 Now are quite critical because in a 4K monitor may cause OutOfMemoryException. Using the following example: " public class JFXMain extends Application{ @Override public void start(Stage primaryStage) throws Exception { HBox root = new HBox(); ToggleButton toggleButton = new ToggleButton(); ProgressIndicator progressIndicator = new ProgressIndicator(ProgressIndicator.INDETERMINATE_PROGRESS); StackPane stackPane = new StackPane(progressIndicator); stackPane.visibleProperty().bind(toggleButton.selectedProperty()); root.getChildren().addAll(toggleButton, stackPane); primaryStage.setScene(new Scene(root)); primaryStage.show(); } } " ** First bug ** Starting the Progress Indicator with indeterminate progress will trigger: rebuildTimeline by ProgressIndicatorSkin and in line 599 start the animation even is not shown already: indeterminateTransition.playFromStart(); ** Second bug ** With the last commits in ProgressIndicator, as commented in JDK-8094829, the listeners do not care about the real visibility of the node(before it was used impl_treeVisibleProperty()). The consequence is that the ProgressIndicator in the example won?t be stopped. I can imagine that impl_treeVisibleProperty() should not be used and Jonathan G. said: " but I can't reliably fix that without an API such as what I expect the treeVisible API should do." But we did not find such alternative property. The solution we though is the usage of internal tree visible property like this: 1. Modify method: " protected void updateAnimation(boolean isTreeVisible) { " 2. Remove current calls to method in " @Override protected void handleControlPropertyChanged(String p) { super.handleControlPropertyChanged(p); if ("INDETERMINATE".equals(p)) { initialize(); } else if ("PROGRESS".equals(p)) { updateProgress(); } } " 3. Add listener at the end of the IndeterminateSpinner contructor the visibility listener: " private IndeterminateSpinner(boolean spinEnabled, Paint fillOverride) { [...] impl_treeVisibleProperty().addListener((obs, oldVal, newVal) ->{ updateAnimation(newVal); }); } " What do you think? Additional note: I would like to add one more thing. I think that could be very good a property ReadOnlyBooleanProperty treeVisibleProperty() available in all Nodes. Please let me know if we can do something else. Diego From jonathan.giles at oracle.com Sun Feb 28 21:53:30 2016 From: jonathan.giles at oracle.com (Jonathan Giles) Date: Mon, 29 Feb 2016 10:53:30 +1300 Subject: ProgressIndicator indeterminate transition bugs In-Reply-To: References: Message-ID: <56D36C5A.3080500@oracle.com> If you can, are you able to file bug reports for these? -- Jonathan On 29/02/16 10:49 AM, Cirujano Cuesta, Diego wrote: > Hi all, > > We found two important bugs in ProgressIndicator that are related with the following tickets: > > https://bugs.openjdk.java.net/browse/JDK-8094829 > https://bugs.openjdk.java.net/browse/JDK-8094078 > > Now are quite critical because in a 4K monitor may cause OutOfMemoryException. > > Using the following example: > " > public class JFXMain extends Application{ > > @Override > public void start(Stage primaryStage) throws Exception { > HBox root = new HBox(); > ToggleButton toggleButton = new ToggleButton(); > ProgressIndicator progressIndicator = new ProgressIndicator(ProgressIndicator.INDETERMINATE_PROGRESS); > StackPane stackPane = new StackPane(progressIndicator); > stackPane.visibleProperty().bind(toggleButton.selectedProperty()); > root.getChildren().addAll(toggleButton, stackPane); > primaryStage.setScene(new Scene(root)); > primaryStage.show(); > } > } > " > > ** First bug ** > > Starting the Progress Indicator with indeterminate progress will trigger: rebuildTimeline by ProgressIndicatorSkin and in line 599 start the animation even is not shown already: indeterminateTransition.playFromStart(); > > ** Second bug ** > > With the last commits in ProgressIndicator, as commented in JDK-8094829, the listeners do not care about the real visibility of the node(before it was used impl_treeVisibleProperty()). The consequence is that the ProgressIndicator in the example won?t be stopped. > > I can imagine that impl_treeVisibleProperty() should not be used and Jonathan G. said: " but I can't reliably fix that without an API such as what I expect the treeVisible API should do." But we did not find such alternative property. > > The solution we though is the usage of internal tree visible property like this: > > 1. Modify method: > " > protected void updateAnimation(boolean isTreeVisible) { > " > 2. Remove current calls to method in > " > @Override protected void handleControlPropertyChanged(String p) { > super.handleControlPropertyChanged(p); > > if ("INDETERMINATE".equals(p)) { > initialize(); > } else if ("PROGRESS".equals(p)) { > updateProgress(); > } > } > " > 3. Add listener at the end of the IndeterminateSpinner contructor the visibility listener: > " > private IndeterminateSpinner(boolean spinEnabled, Paint fillOverride) { > [...] > impl_treeVisibleProperty().addListener((obs, oldVal, newVal) ->{ > updateAnimation(newVal); > }); > } > " > > What do you think? > > Additional note: I would like to add one more thing. I think that could be very good a property ReadOnlyBooleanProperty treeVisibleProperty() available in all Nodes. > > Please let me know if we can do something else. > > Diego From diego.cirujano-cuesta at zeiss.com Sun Feb 28 22:30:38 2016 From: diego.cirujano-cuesta at zeiss.com (Cirujano Cuesta, Diego) Date: Sun, 28 Feb 2016 22:30:38 +0000 Subject: ProgressIndicator indeterminate transition bugs In-Reply-To: <56D36C5A.3080500@oracle.com> References: <56D36C5A.3080500@oracle.com> Message-ID: Hi Jonathan: I thought they would be reopened that?s why I did not create them. Here there are: JI-9029954 JI-9029955 By the way I also created another one for a few weeks (28.01.2016) JI-9029025 but I did not receive anything else. I do not know if I am creating the bugs in a wrong place or what. I am using: http://bugreport.java.com/ What can I do in order to write comments in the JBS bugs? Thanks, Diego -----Original Message----- From: Jonathan Giles [mailto:jonathan.giles at oracle.com] Sent: Sonntag, 28. Februar 2016 22:54 To: Cirujano Cuesta, Diego; openjfx-dev at openjdk.java.net Subject: Re: ProgressIndicator indeterminate transition bugs If you can, are you able to file bug reports for these? -- Jonathan On 29/02/16 10:49 AM, Cirujano Cuesta, Diego wrote: > Hi all, > > We found two important bugs in ProgressIndicator that are related with the following tickets: > > https://bugs.openjdk.java.net/browse/JDK-8094829 > https://bugs.openjdk.java.net/browse/JDK-8094078 > > Now are quite critical because in a 4K monitor may cause OutOfMemoryException. > > Using the following example: > " > public class JFXMain extends Application{ > > @Override > public void start(Stage primaryStage) throws Exception { > HBox root = new HBox(); > ToggleButton toggleButton = new ToggleButton(); > ProgressIndicator progressIndicator = new ProgressIndicator(ProgressIndicator.INDETERMINATE_PROGRESS); > StackPane stackPane = new StackPane(progressIndicator); > stackPane.visibleProperty().bind(toggleButton.selectedProperty()); > root.getChildren().addAll(toggleButton, stackPane); > primaryStage.setScene(new Scene(root)); > primaryStage.show(); > } > } > " > > ** First bug ** > > Starting the Progress Indicator with indeterminate progress will > trigger: rebuildTimeline by ProgressIndicatorSkin and in line 599 > start the animation even is not shown already: > indeterminateTransition.playFromStart(); > > ** Second bug ** > > With the last commits in ProgressIndicator, as commented in JDK-8094829, the listeners do not care about the real visibility of the node(before it was used impl_treeVisibleProperty()). The consequence is that the ProgressIndicator in the example won?t be stopped. > > I can imagine that impl_treeVisibleProperty() should not be used and Jonathan G. said: " but I can't reliably fix that without an API such as what I expect the treeVisible API should do." But we did not find such alternative property. > > The solution we though is the usage of internal tree visible property like this: > > 1. Modify method: > " > protected void updateAnimation(boolean isTreeVisible) { " > 2. Remove current calls to method in > " > @Override protected void handleControlPropertyChanged(String p) { > super.handleControlPropertyChanged(p); > > if ("INDETERMINATE".equals(p)) { > initialize(); > } else if ("PROGRESS".equals(p)) { > updateProgress(); > } > } > " > 3. Add listener at the end of the IndeterminateSpinner contructor the visibility listener: > " > private IndeterminateSpinner(boolean spinEnabled, Paint fillOverride) { > [...] > impl_treeVisibleProperty().addListener((obs, oldVal, newVal) ->{ > updateAnimation(newVal); > }); > } > " > > What do you think? > > Additional note: I would like to add one more thing. I think that could be very good a property ReadOnlyBooleanProperty treeVisibleProperty() available in all Nodes. > > Please let me know if we can do something else. > > Diego From dalibor.topic at oracle.com Mon Feb 29 11:12:05 2016 From: dalibor.topic at oracle.com (dalibor topic) Date: Mon, 29 Feb 2016 12:12:05 +0100 Subject: ProgressIndicator indeterminate transition bugs In-Reply-To: References: <56D36C5A.3080500@oracle.com> Message-ID: <56D42785.7060901@oracle.com> On 28.02.2016 23:30, Cirujano Cuesta, Diego wrote: > What can I do in order to write comments in the JBS bugs? Start with http://openjdk.java.net/contribute/ -> contribute two sponsored changes into OpenJFX -> ask its Project Lead to appoint you as an Author -> get registered in the Census -> write comments in JBS bugs, open your own, etc. cheers, dalibor topic -- Dalibor Topic | Principal Product Manager Phone: +494089091214 | Mobile: +491737185961 ORACLE Deutschland B.V. & Co. KG | K?hneh?fe 5 | 22761 Hamburg ORACLE Deutschland B.V. & Co. KG Hauptverwaltung: Riesstr. 25, D-80992 M?nchen Registergericht: Amtsgericht M?nchen, HRA 95603 Komplement?rin: ORACLE Deutschland Verwaltung B.V. Hertogswetering 163/167, 3543 AS Utrecht, Niederlande Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697 Gesch?ftsf?hrer: Alexander van der Ven, Jan Schultheiss, Val Maher Oracle is committed to developing practices and products that help protect the environment From info at cuhka.com Mon Feb 29 12:25:34 2016 From: info at cuhka.com (Maurice) Date: Mon, 29 Feb 2016 13:25:34 +0100 Subject: NPE in PrismFontLoader.java: Loading primary font factory failed In-Reply-To: <56C73AFC.90306@cuhka.com> References: <56C71913.7080502@cuhka.com> <56C7399E.6010006@oracle.com> <56C73AFC.90306@cuhka.com> Message-ID: <56D438BE.6070701@cuhka.com> For those searching for an answer, I could fix it by adding pango and fontconfig to the Yocto build. Maurice. From info at cuhka.com Mon Feb 29 15:21:09 2016 From: info at cuhka.com (Maurice) Date: Mon, 29 Feb 2016 16:21:09 +0100 Subject: GLS language errors (Was: Internal error: Error loading stock shader FillRoundRect_LinearGradient,_PAD on Vivante ARM) In-Reply-To: <56D32F81.7060708@cuhka.com> References: <56D1E6A4.80301@cuhka.com> <56D32F81.7060708@cuhka.com> Message-ID: <56D461E5.4020307@cuhka.com> Should I file a bug? I can't determine whether this is a client platform issue or a major bug in the EGL that JavaFX is using. In any case, it does not work on my embedded device. Maurice. Op 28-02-16 om 18:33 schreef Maurice: > When I run the glslangValidator on > FillRoundRect_LinearGradient_PAD.frag it gives the following error: > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > > When I move pixcoord's declaration on line 19 into the main() function > it gives no errors. > > This is the full output of find -name "*.frag" -exec glslangValidator > {} \; > > ERROR: 0:53: 'oTexCoords' : undeclared identifier > ERROR: 0:53: 'texture2D' : no matching overloaded function found > ERROR: 0:53: '=' : cannot convert from 'const float' to 'temp highp > 4-component vector of float' > ERROR: 3 compilation errors. No code generated. > > > ERROR: 0:55: 'oTexCoords' : undeclared identifier > ERROR: 0:55: 'texture2D' : no matching overloaded function found > ERROR: 0:55: 'scalar swizzle' : not supported with this profile: es > ERROR: 0:55: 'rgb' : vector field selection out of range > ERROR: 0:55: '=' : cannot convert from 'const float' to 'temp highp > 3-component vector of float' > ERROR: 5 compilation errors. No code generated. > > > ERROR: 0:53: 'oTexCoords' : undeclared identifier > ERROR: 0:53: 'texture2D' : no matching overloaded function found > WARNING: 0:53: 'return' : type conversion on return values was not > explicitly allowed until version 420 > ERROR: 2 compilation errors. No code generated. > > > ERROR: 0:55: 'oTexCoords' : undeclared identifier > ERROR: 0:55: 'texture2D' : no matching overloaded function found > ERROR: 0:55: 'scalar swizzle' : not supported with this profile: es > ERROR: 0:55: 'rgb' : vector field selection out of range > ERROR: 0:55: '=' : cannot convert from 'const float' to 'temp highp > 3-component vector of float' > ERROR: 5 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:53: 'oTexCoords' : undeclared identifier > ERROR: 0:53: 'texture2D' : no matching overloaded function found > ERROR: 0:53: '=' : cannot convert from 'const float' to 'temp highp > 4-component vector of float' > ERROR: 3 compilation errors. No code generated. > > > ERROR: 0:55: 'oTexCoords' : undeclared identifier > ERROR: 0:55: 'texture2D' : no matching overloaded function found > ERROR: 0:55: 'scalar swizzle' : not supported with this profile: es > ERROR: 0:55: 'rgb' : vector field selection out of range > ERROR: 0:55: '=' : cannot convert from 'const float' to 'temp highp > 3-component vector of float' > ERROR: 5 compilation errors. No code generated. > > > ERROR: 0:53: 'oTexCoords' : undeclared identifier > ERROR: 0:53: 'texture2D' : no matching overloaded function found > WARNING: 0:53: 'return' : type conversion on return values was not > explicitly allowed until version 420 > ERROR: 2 compilation errors. No code generated. > > > ERROR: 0:55: 'oTexCoords' : undeclared identifier > ERROR: 0:55: 'texture2D' : no matching overloaded function found > ERROR: 0:55: 'scalar swizzle' : not supported with this profile: es > ERROR: 0:55: 'rgb' : vector field selection out of range > ERROR: 0:55: '=' : cannot convert from 'const float' to 'temp highp > 3-component vector of float' > ERROR: 5 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with > this profile: es > ERROR: 1 compilation errors. No code generated. > > > > Op 27-02-16 om 19:10 schreef Maurice: >> I'm running into the following exception when I start a simple JavaFX >> test program on my ARM based board: >> >> Shader compile log: (21:0) : error : In declarations of global >> variables with no >> storage qualifier or with a const qualifier, any initializer must be >> a constant >> expression >> (103:0) : error : undefined identifier: 'pixcoord' >> >> java.lang.reflect.InvocationTargetException >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> at >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. >> java:62) >> at >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces >> sorImpl.java:43) >> at java.lang.reflect.Method.invoke(Method.java:483) >> at >> com.sun.prism.es2.ES2ResourceFactory.createStockShader(ES2ResourceFac >> tory.java:312) >> at >> com.sun.prism.impl.ps.BaseShaderContext.getPaintShader(BaseShaderCont >> ext.java:256) >> at >> com.sun.prism.impl.ps.BaseShaderContext.validatePaintOp(BaseShaderCon >> text.java:477) >> at >> com.sun.prism.impl.ps.BaseShaderContext.validatePaintOp(BaseShaderCon >> text.java:374) >> at >> com.sun.prism.impl.ps.BaseShaderGraphics.renderGeneralRoundedPgram(Ba >> seShaderGraphics.java:842) >> at >> com.sun.prism.impl.ps.BaseShaderGraphics.renderGeneralRoundedRect(Bas >> eShaderGraphics.java:601) >> at >> com.sun.prism.impl.ps.BaseShaderGraphics.fillRoundRect(BaseShaderGrap >> hics.java:1557) >> at >> com.sun.javafx.sg.prism.NGRegion.renderBackgroundRectanglesDirectly(N >> GRegion.java:1119) >> at >> com.sun.javafx.sg.prism.NGRegion.renderBackgroundRectangle(NGRegion.j >> ava:830) >> at >> com.sun.javafx.sg.prism.NGRegion.renderAsRectangle(NGRegion.java:751) >> at >> com.sun.javafx.sg.prism.NGRegion.renderContent(NGRegion.java:572) >> at com.sun.javafx.sg.prism.NGNode.doRender(NGNode.java:2053) >> at com.sun.javafx.sg.prism.NGNode.render(NGNode.java:1945) >> at >> com.sun.javafx.sg.prism.NGGroup.renderContent(NGGroup.java:235) >> at com.sun.javafx.sg.prism.NGNode.doRender(NGNode.java:2053) >> at com.sun.javafx.sg.prism.NGNode.render(NGNode.java:1945) >> at >> com.sun.javafx.tk.quantum.ViewPainter.doPaint(ViewPainter.java:477) >> at >> com.sun.javafx.tk.quantum.ViewPainter.paintImpl(ViewPainter.java:330) >> at >> com.sun.javafx.tk.quantum.PresentingPainter.run(PresentingPainter.jav >> a:91) >> at >> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:51 >> 1) >> at >> java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) >> at com.sun.javafx.tk.RenderJob.run(RenderJob.java:58) >> at >> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor. >> java:1142) >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor >> .java:617) >> at >> com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.run(Quantu >> mRenderer.java:125) >> at java.lang.Thread.run(Thread.java:745) >> Caused by: java.lang.RuntimeException: Error creating fragment shader >> at >> com.sun.prism.es2.ES2Shader.createFromSource(ES2Shader.java:141) >> at >> com.sun.prism.es2.ES2Shader.createFromSource(ES2Shader.java:173) >> at >> com.sun.prism.es2.ES2ResourceFactory.createShader(ES2ResourceFactory. >> java:224) >> at >> com.sun.prism.shader.FillRoundRect_LinearGradient_PAD_Loader.loadShad >> er(FillRoundRect_LinearGradient_PAD_Loader.java:53) >> ... 30 more >> java.lang.InternalError: Error loading stock shader >> FillRoundRect_LinearGradient >> _PAD >> at >> com.sun.prism.es2.ES2ResourceFactory.createStockShader(ES2ResourceFac >> tory.java:315) >> at >> com.sun.prism.impl.ps.BaseShaderContext.getPaintShader(BaseShaderCont >> ext.java:256) >> at >> com.sun.prism.impl.ps.BaseShaderContext.validatePaintOp(BaseShaderCon >> text.java:477) >> at >> com.sun.prism.impl.ps.BaseShaderContext.validatePaintOp(BaseShaderCon >> text.java:374) >> at >> com.sun.prism.impl.ps.BaseShaderGraphics.renderGeneralRoundedPgram(Ba >> seShaderGraphics.java:842) >> at >> com.sun.prism.impl.ps.BaseShaderGraphics.renderGeneralRoundedRect(Bas >> eShaderGraphics.java:601) >> at >> com.sun.prism.impl.ps.BaseShaderGraphics.fillRoundRect(BaseShaderGrap >> hics.java:1557) >> at >> com.sun.javafx.sg.prism.NGRegion.renderBackgroundRectanglesDirectly(N >> GRegion.java:1119) >> at >> com.sun.javafx.sg.prism.NGRegion.renderBackgroundRectangle(NGRegion.j >> ava:830) >> at >> com.sun.javafx.sg.prism.NGRegion.renderAsRectangle(NGRegion.java:751) >> at >> com.sun.javafx.sg.prism.NGRegion.renderContent(NGRegion.java:572) >> at com.sun.javafx.sg.prism.NGNode.doRender(NGNode.java:2053) >> at com.sun.javafx.sg.prism.NGNode.render(NGNode.java:1945) >> at >> com.sun.javafx.sg.prism.NGGroup.renderContent(NGGroup.java:235) >> at com.sun.javafx.sg.prism.NGNode.doRender(NGNode.java:2053) >> at com.sun.javafx.sg.prism.NGNode.render(NGNode.java:1945) >> at >> com.sun.javafx.tk.quantum.ViewPainter.doPaint(ViewPainter.java:477) >> at >> com.sun.javafx.tk.quantum.ViewPainter.paintImpl(ViewPainter.java:330) >> at >> com.sun.javafx.tk.quantum.PresentingPainter.run(PresentingPainter.jav >> a:91) >> at >> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:51 >> 1) >> at >> java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) >> at com.sun.javafx.tk.RenderJob.run(RenderJob.java:58) >> at >> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor. >> java:1142) >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor >> .java:617) >> at >> com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.run(Quantu >> mRenderer.java:125) >> at java.lang.Thread.run(Thread.java:745) >> >> Maurice. > From chien.yang at oracle.com Mon Feb 29 16:49:48 2016 From: chien.yang at oracle.com (Chien Yang) Date: Mon, 29 Feb 2016 08:49:48 -0800 Subject: GLS language errors (Was: Internal error: Error loading stock shader FillRoundRect_LinearGradient,_PAD on Vivante ARM) In-Reply-To: <56D461E5.4020307@cuhka.com> References: <56D1E6A4.80301@cuhka.com> <56D32F81.7060708@cuhka.com> <56D461E5.4020307@cuhka.com> Message-ID: <56D476AC.2050901@oracle.com> I have a quick question. Did you get your embedded JavaFX library from Glueon? http://gluonhq.com/open-source/javafxports/downloads/ - Chien On 2/29/16, 7:21 AM, Maurice wrote: > Should I file a bug? I can't determine whether this is a client > platform issue or a major bug in the EGL that JavaFX is using. In any > case, it does not work on my embedded device. > > Maurice. > > Op 28-02-16 om 18:33 schreef Maurice: >> When I run the glslangValidator on >> FillRoundRect_LinearGradient_PAD.frag it gives the following error: >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> >> When I move pixcoord's declaration on line 19 into the main() >> function it gives no errors. >> >> This is the full output of find -name "*.frag" -exec glslangValidator >> {} \; >> >> ERROR: 0:53: 'oTexCoords' : undeclared identifier >> ERROR: 0:53: 'texture2D' : no matching overloaded function found >> ERROR: 0:53: '=' : cannot convert from 'const float' to 'temp highp >> 4-component vector of float' >> ERROR: 3 compilation errors. No code generated. >> >> >> ERROR: 0:55: 'oTexCoords' : undeclared identifier >> ERROR: 0:55: 'texture2D' : no matching overloaded function found >> ERROR: 0:55: 'scalar swizzle' : not supported with this profile: es >> ERROR: 0:55: 'rgb' : vector field selection out of range >> ERROR: 0:55: '=' : cannot convert from 'const float' to 'temp highp >> 3-component vector of float' >> ERROR: 5 compilation errors. No code generated. >> >> >> ERROR: 0:53: 'oTexCoords' : undeclared identifier >> ERROR: 0:53: 'texture2D' : no matching overloaded function found >> WARNING: 0:53: 'return' : type conversion on return values was not >> explicitly allowed until version 420 >> ERROR: 2 compilation errors. No code generated. >> >> >> ERROR: 0:55: 'oTexCoords' : undeclared identifier >> ERROR: 0:55: 'texture2D' : no matching overloaded function found >> ERROR: 0:55: 'scalar swizzle' : not supported with this profile: es >> ERROR: 0:55: 'rgb' : vector field selection out of range >> ERROR: 0:55: '=' : cannot convert from 'const float' to 'temp highp >> 3-component vector of float' >> ERROR: 5 compilation errors. No code generated. >> >> >> ERROR: 0:18: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:18: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:53: 'oTexCoords' : undeclared identifier >> ERROR: 0:53: 'texture2D' : no matching overloaded function found >> ERROR: 0:53: '=' : cannot convert from 'const float' to 'temp highp >> 4-component vector of float' >> ERROR: 3 compilation errors. No code generated. >> >> >> ERROR: 0:55: 'oTexCoords' : undeclared identifier >> ERROR: 0:55: 'texture2D' : no matching overloaded function found >> ERROR: 0:55: 'scalar swizzle' : not supported with this profile: es >> ERROR: 0:55: 'rgb' : vector field selection out of range >> ERROR: 0:55: '=' : cannot convert from 'const float' to 'temp highp >> 3-component vector of float' >> ERROR: 5 compilation errors. No code generated. >> >> >> ERROR: 0:53: 'oTexCoords' : undeclared identifier >> ERROR: 0:53: 'texture2D' : no matching overloaded function found >> WARNING: 0:53: 'return' : type conversion on return values was not >> explicitly allowed until version 420 >> ERROR: 2 compilation errors. No code generated. >> >> >> ERROR: 0:55: 'oTexCoords' : undeclared identifier >> ERROR: 0:55: 'texture2D' : no matching overloaded function found >> ERROR: 0:55: 'scalar swizzle' : not supported with this profile: es >> ERROR: 0:55: 'rgb' : vector field selection out of range >> ERROR: 0:55: '=' : cannot convert from 'const float' to 'temp highp >> 3-component vector of float' >> ERROR: 5 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:17: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:17: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:18: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:17: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:18: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:18: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:18: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:18: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:18: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:18: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:17: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:17: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:18: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:17: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:18: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:17: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:17: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:17: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:17: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:17: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:17: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:18: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:18: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:17: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:18: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:18: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:18: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:17: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:18: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:18: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:17: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:17: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:18: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:17: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:18: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:18: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:18: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:18: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:18: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:18: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:17: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:17: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:18: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:17: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:18: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:17: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:17: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:17: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:17: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:17: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:17: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:18: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:18: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:17: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:18: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:18: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:18: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:17: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> ERROR: 0:19: 'non-constant global initializer' : not supported with >> this profile: es >> ERROR: 1 compilation errors. No code generated. >> >> >> >> Op 27-02-16 om 19:10 schreef Maurice: >>> I'm running into the following exception when I start a simple >>> JavaFX test program on my ARM based board: >>> >>> Shader compile log: (21:0) : error : In declarations of global >>> variables with no >>> storage qualifier or with a const qualifier, any initializer must >>> be a constant >>> expression >>> (103:0) : error : undefined identifier: 'pixcoord' >>> >>> java.lang.reflect.InvocationTargetException >>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>> at >>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. >>> java:62) >>> at >>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces >>> sorImpl.java:43) >>> at java.lang.reflect.Method.invoke(Method.java:483) >>> at >>> com.sun.prism.es2.ES2ResourceFactory.createStockShader(ES2ResourceFac >>> tory.java:312) >>> at >>> com.sun.prism.impl.ps.BaseShaderContext.getPaintShader(BaseShaderCont >>> ext.java:256) >>> at >>> com.sun.prism.impl.ps.BaseShaderContext.validatePaintOp(BaseShaderCon >>> text.java:477) >>> at >>> com.sun.prism.impl.ps.BaseShaderContext.validatePaintOp(BaseShaderCon >>> text.java:374) >>> at >>> com.sun.prism.impl.ps.BaseShaderGraphics.renderGeneralRoundedPgram(Ba >>> seShaderGraphics.java:842) >>> at >>> com.sun.prism.impl.ps.BaseShaderGraphics.renderGeneralRoundedRect(Bas >>> eShaderGraphics.java:601) >>> at >>> com.sun.prism.impl.ps.BaseShaderGraphics.fillRoundRect(BaseShaderGrap >>> hics.java:1557) >>> at >>> com.sun.javafx.sg.prism.NGRegion.renderBackgroundRectanglesDirectly(N >>> GRegion.java:1119) >>> at >>> com.sun.javafx.sg.prism.NGRegion.renderBackgroundRectangle(NGRegion.j >>> ava:830) >>> at >>> com.sun.javafx.sg.prism.NGRegion.renderAsRectangle(NGRegion.java:751) >>> at >>> com.sun.javafx.sg.prism.NGRegion.renderContent(NGRegion.java:572) >>> at com.sun.javafx.sg.prism.NGNode.doRender(NGNode.java:2053) >>> at com.sun.javafx.sg.prism.NGNode.render(NGNode.java:1945) >>> at >>> com.sun.javafx.sg.prism.NGGroup.renderContent(NGGroup.java:235) >>> at com.sun.javafx.sg.prism.NGNode.doRender(NGNode.java:2053) >>> at com.sun.javafx.sg.prism.NGNode.render(NGNode.java:1945) >>> at >>> com.sun.javafx.tk.quantum.ViewPainter.doPaint(ViewPainter.java:477) >>> at >>> com.sun.javafx.tk.quantum.ViewPainter.paintImpl(ViewPainter.java:330) >>> at >>> com.sun.javafx.tk.quantum.PresentingPainter.run(PresentingPainter.jav >>> a:91) >>> at >>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:51 >>> 1) >>> at >>> java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) >>> at com.sun.javafx.tk.RenderJob.run(RenderJob.java:58) >>> at >>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor. >>> java:1142) >>> at >>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor >>> .java:617) >>> at >>> com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.run(Quantu >>> mRenderer.java:125) >>> at java.lang.Thread.run(Thread.java:745) >>> Caused by: java.lang.RuntimeException: Error creating fragment shader >>> at >>> com.sun.prism.es2.ES2Shader.createFromSource(ES2Shader.java:141) >>> at >>> com.sun.prism.es2.ES2Shader.createFromSource(ES2Shader.java:173) >>> at >>> com.sun.prism.es2.ES2ResourceFactory.createShader(ES2ResourceFactory. >>> java:224) >>> at >>> com.sun.prism.shader.FillRoundRect_LinearGradient_PAD_Loader.loadShad >>> er(FillRoundRect_LinearGradient_PAD_Loader.java:53) >>> ... 30 more >>> java.lang.InternalError: Error loading stock shader >>> FillRoundRect_LinearGradient >>> _PAD >>> at >>> com.sun.prism.es2.ES2ResourceFactory.createStockShader(ES2ResourceFac >>> tory.java:315) >>> at >>> com.sun.prism.impl.ps.BaseShaderContext.getPaintShader(BaseShaderCont >>> ext.java:256) >>> at >>> com.sun.prism.impl.ps.BaseShaderContext.validatePaintOp(BaseShaderCon >>> text.java:477) >>> at >>> com.sun.prism.impl.ps.BaseShaderContext.validatePaintOp(BaseShaderCon >>> text.java:374) >>> at >>> com.sun.prism.impl.ps.BaseShaderGraphics.renderGeneralRoundedPgram(Ba >>> seShaderGraphics.java:842) >>> at >>> com.sun.prism.impl.ps.BaseShaderGraphics.renderGeneralRoundedRect(Bas >>> eShaderGraphics.java:601) >>> at >>> com.sun.prism.impl.ps.BaseShaderGraphics.fillRoundRect(BaseShaderGrap >>> hics.java:1557) >>> at >>> com.sun.javafx.sg.prism.NGRegion.renderBackgroundRectanglesDirectly(N >>> GRegion.java:1119) >>> at >>> com.sun.javafx.sg.prism.NGRegion.renderBackgroundRectangle(NGRegion.j >>> ava:830) >>> at >>> com.sun.javafx.sg.prism.NGRegion.renderAsRectangle(NGRegion.java:751) >>> at >>> com.sun.javafx.sg.prism.NGRegion.renderContent(NGRegion.java:572) >>> at com.sun.javafx.sg.prism.NGNode.doRender(NGNode.java:2053) >>> at com.sun.javafx.sg.prism.NGNode.render(NGNode.java:1945) >>> at >>> com.sun.javafx.sg.prism.NGGroup.renderContent(NGGroup.java:235) >>> at com.sun.javafx.sg.prism.NGNode.doRender(NGNode.java:2053) >>> at com.sun.javafx.sg.prism.NGNode.render(NGNode.java:1945) >>> at >>> com.sun.javafx.tk.quantum.ViewPainter.doPaint(ViewPainter.java:477) >>> at >>> com.sun.javafx.tk.quantum.ViewPainter.paintImpl(ViewPainter.java:330) >>> at >>> com.sun.javafx.tk.quantum.PresentingPainter.run(PresentingPainter.jav >>> a:91) >>> at >>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:51 >>> 1) >>> at >>> java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) >>> at com.sun.javafx.tk.RenderJob.run(RenderJob.java:58) >>> at >>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor. >>> java:1142) >>> at >>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor >>> .java:617) >>> at >>> com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.run(Quantu >>> mRenderer.java:125) >>> at java.lang.Thread.run(Thread.java:745) >>> >>> Maurice. >> > From info at cuhka.com Mon Feb 29 18:35:38 2016 From: info at cuhka.com (Maurice) Date: Mon, 29 Feb 2016 19:35:38 +0100 Subject: GLS language errors (Was: Internal error: Error loading stock shader FillRoundRect_LinearGradient,_PAD on Vivante ARM) In-Reply-To: <56D4785E.3050109@cuhka.com> References: <56D4785E.3050109@cuhka.com> Message-ID: <56D48F7A.3060301@cuhka.com> No, I build them myself from the instructions on the Wiki . Maurice. Op 29-02-16 om 17:49 schreef Chien Yang: > I have a quick question. Did you get your embedded JavaFX library from > Glueon? > > http://gluonhq.com/open-source/javafxports/downloads/ > > - Chien > > > On 2/29/16, 7:21 AM, Maurice wrote: >> Should I file a bug? I can't determine whether this is a client >> platform issue or a major bug in the EGL that JavaFX is using. In any >> case, it does not work on my embedded device. >> >> Maurice. >> >> Op 28-02-16 om 18:33 schreef Maurice: >>> When I run the glslangValidator on >>> FillRoundRect_LinearGradient_PAD.frag it gives the following error: >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> >>> When I move pixcoord's declaration on line 19 into the main() >>> function it gives no errors. >>> >>> This is the full output of find -name "*.frag" -exec >>> glslangValidator {} \; >>> >>> ERROR: 0:53: 'oTexCoords' : undeclared identifier >>> ERROR: 0:53: 'texture2D' : no matching overloaded function found >>> ERROR: 0:53: '=' : cannot convert from 'const float' to 'temp highp >>> 4-component vector of float' >>> ERROR: 3 compilation errors. No code generated. >>> >>> >>> ERROR: 0:55: 'oTexCoords' : undeclared identifier >>> ERROR: 0:55: 'texture2D' : no matching overloaded function found >>> ERROR: 0:55: 'scalar swizzle' : not supported with this profile: es >>> ERROR: 0:55: 'rgb' : vector field selection out of range >>> ERROR: 0:55: '=' : cannot convert from 'const float' to 'temp highp >>> 3-component vector of float' >>> ERROR: 5 compilation errors. No code generated. >>> >>> >>> ERROR: 0:53: 'oTexCoords' : undeclared identifier >>> ERROR: 0:53: 'texture2D' : no matching overloaded function found >>> WARNING: 0:53: 'return' : type conversion on return values was not >>> explicitly allowed until version 420 >>> ERROR: 2 compilation errors. No code generated. >>> >>> >>> ERROR: 0:55: 'oTexCoords' : undeclared identifier >>> ERROR: 0:55: 'texture2D' : no matching overloaded function found >>> ERROR: 0:55: 'scalar swizzle' : not supported with this profile: es >>> ERROR: 0:55: 'rgb' : vector field selection out of range >>> ERROR: 0:55: '=' : cannot convert from 'const float' to 'temp highp >>> 3-component vector of float' >>> ERROR: 5 compilation errors. No code generated. >>> >>> >>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:53: 'oTexCoords' : undeclared identifier >>> ERROR: 0:53: 'texture2D' : no matching overloaded function found >>> ERROR: 0:53: '=' : cannot convert from 'const float' to 'temp highp >>> 4-component vector of float' >>> ERROR: 3 compilation errors. No code generated. >>> >>> >>> ERROR: 0:55: 'oTexCoords' : undeclared identifier >>> ERROR: 0:55: 'texture2D' : no matching overloaded function found >>> ERROR: 0:55: 'scalar swizzle' : not supported with this profile: es >>> ERROR: 0:55: 'rgb' : vector field selection out of range >>> ERROR: 0:55: '=' : cannot convert from 'const float' to 'temp highp >>> 3-component vector of float' >>> ERROR: 5 compilation errors. No code generated. >>> >>> >>> ERROR: 0:53: 'oTexCoords' : undeclared identifier >>> ERROR: 0:53: 'texture2D' : no matching overloaded function found >>> WARNING: 0:53: 'return' : type conversion on return values was not >>> explicitly allowed until version 420 >>> ERROR: 2 compilation errors. No code generated. >>> >>> >>> ERROR: 0:55: 'oTexCoords' : undeclared identifier >>> ERROR: 0:55: 'texture2D' : no matching overloaded function found >>> ERROR: 0:55: 'scalar swizzle' : not supported with this profile: es >>> ERROR: 0:55: 'rgb' : vector field selection out of range >>> ERROR: 0:55: '=' : cannot convert from 'const float' to 'temp highp >>> 3-component vector of float' >>> ERROR: 5 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>> this profile: es >>> ERROR: 1 compilation errors. No code generated. >>> >>> >>> >>> Op 27-02-16 om 19:10 schreef Maurice: >>>> I'm running into the following exception when I start a simple >>>> JavaFX test program on my ARM based board: >>>> >>>> Shader compile log: (21:0) : error : In declarations of global >>>> variables with no >>>> storage qualifier or with a const qualifier, any initializer must >>>> be a constant >>>> expression >>>> (103:0) : error : undefined identifier: 'pixcoord' >>>> >>>> java.lang.reflect.InvocationTargetException >>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>>> at >>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. >>>> java:62) >>>> at >>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces >>>> sorImpl.java:43) >>>> at java.lang.reflect.Method.invoke(Method.java:483) >>>> at >>>> com.sun.prism.es2.ES2ResourceFactory.createStockShader(ES2ResourceFac >>>> tory.java:312) >>>> at >>>> com.sun.prism.impl.ps.BaseShaderContext.getPaintShader(BaseShaderCont >>>> ext.java:256) >>>> at >>>> com.sun.prism.impl.ps.BaseShaderContext.validatePaintOp(BaseShaderCon >>>> text.java:477) >>>> at >>>> com.sun.prism.impl.ps.BaseShaderContext.validatePaintOp(BaseShaderCon >>>> text.java:374) >>>> at >>>> com.sun.prism.impl.ps.BaseShaderGraphics.renderGeneralRoundedPgram(Ba >>>> seShaderGraphics.java:842) >>>> at >>>> com.sun.prism.impl.ps.BaseShaderGraphics.renderGeneralRoundedRect(Bas >>>> eShaderGraphics.java:601) >>>> at >>>> com.sun.prism.impl.ps.BaseShaderGraphics.fillRoundRect(BaseShaderGrap >>>> hics.java:1557) >>>> at >>>> com.sun.javafx.sg.prism.NGRegion.renderBackgroundRectanglesDirectly(N >>>> GRegion.java:1119) >>>> at >>>> com.sun.javafx.sg.prism.NGRegion.renderBackgroundRectangle(NGRegion.j >>>> ava:830) >>>> at >>>> com.sun.javafx.sg.prism.NGRegion.renderAsRectangle(NGRegion.java:751) >>>> at >>>> com.sun.javafx.sg.prism.NGRegion.renderContent(NGRegion.java:572) >>>> at com.sun.javafx.sg.prism.NGNode.doRender(NGNode.java:2053) >>>> at com.sun.javafx.sg.prism.NGNode.render(NGNode.java:1945) >>>> at >>>> com.sun.javafx.sg.prism.NGGroup.renderContent(NGGroup.java:235) >>>> at com.sun.javafx.sg.prism.NGNode.doRender(NGNode.java:2053) >>>> at com.sun.javafx.sg.prism.NGNode.render(NGNode.java:1945) >>>> at >>>> com.sun.javafx.tk.quantum.ViewPainter.doPaint(ViewPainter.java:477) >>>> at >>>> com.sun.javafx.tk.quantum.ViewPainter.paintImpl(ViewPainter.java:330) >>>> at >>>> com.sun.javafx.tk.quantum.PresentingPainter.run(PresentingPainter.jav >>>> a:91) >>>> at >>>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:51 >>>> 1) >>>> at >>>> java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) >>>> at com.sun.javafx.tk.RenderJob.run(RenderJob.java:58) >>>> at >>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor. >>>> java:1142) >>>> at >>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor >>>> .java:617) >>>> at >>>> com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.run(Quantu >>>> mRenderer.java:125) >>>> at java.lang.Thread.run(Thread.java:745) >>>> Caused by: java.lang.RuntimeException: Error creating fragment shader >>>> at >>>> com.sun.prism.es2.ES2Shader.createFromSource(ES2Shader.java:141) >>>> at >>>> com.sun.prism.es2.ES2Shader.createFromSource(ES2Shader.java:173) >>>> at >>>> com.sun.prism.es2.ES2ResourceFactory.createShader(ES2ResourceFactory. >>>> java:224) >>>> at >>>> com.sun.prism.shader.FillRoundRect_LinearGradient_PAD_Loader.loadShad >>>> er(FillRoundRect_LinearGradient_PAD_Loader.java:53) >>>> ... 30 more >>>> java.lang.InternalError: Error loading stock shader >>>> FillRoundRect_LinearGradient >>>> _PAD >>>> at >>>> com.sun.prism.es2.ES2ResourceFactory.createStockShader(ES2ResourceFac >>>> tory.java:315) >>>> at >>>> com.sun.prism.impl.ps.BaseShaderContext.getPaintShader(BaseShaderCont >>>> ext.java:256) >>>> at >>>> com.sun.prism.impl.ps.BaseShaderContext.validatePaintOp(BaseShaderCon >>>> text.java:477) >>>> at >>>> com.sun.prism.impl.ps.BaseShaderContext.validatePaintOp(BaseShaderCon >>>> text.java:374) >>>> at >>>> com.sun.prism.impl.ps.BaseShaderGraphics.renderGeneralRoundedPgram(Ba >>>> seShaderGraphics.java:842) >>>> at >>>> com.sun.prism.impl.ps.BaseShaderGraphics.renderGeneralRoundedRect(Bas >>>> eShaderGraphics.java:601) >>>> at >>>> com.sun.prism.impl.ps.BaseShaderGraphics.fillRoundRect(BaseShaderGrap >>>> hics.java:1557) >>>> at >>>> com.sun.javafx.sg.prism.NGRegion.renderBackgroundRectanglesDirectly(N >>>> GRegion.java:1119) >>>> at >>>> com.sun.javafx.sg.prism.NGRegion.renderBackgroundRectangle(NGRegion.j >>>> ava:830) >>>> at >>>> com.sun.javafx.sg.prism.NGRegion.renderAsRectangle(NGRegion.java:751) >>>> at >>>> com.sun.javafx.sg.prism.NGRegion.renderContent(NGRegion.java:572) >>>> at com.sun.javafx.sg.prism.NGNode.doRender(NGNode.java:2053) >>>> at com.sun.javafx.sg.prism.NGNode.render(NGNode.java:1945) >>>> at >>>> com.sun.javafx.sg.prism.NGGroup.renderContent(NGGroup.java:235) >>>> at com.sun.javafx.sg.prism.NGNode.doRender(NGNode.java:2053) >>>> at com.sun.javafx.sg.prism.NGNode.render(NGNode.java:1945) >>>> at >>>> com.sun.javafx.tk.quantum.ViewPainter.doPaint(ViewPainter.java:477) >>>> at >>>> com.sun.javafx.tk.quantum.ViewPainter.paintImpl(ViewPainter.java:330) >>>> at >>>> com.sun.javafx.tk.quantum.PresentingPainter.run(PresentingPainter.jav >>>> a:91) >>>> at >>>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:51 >>>> 1) >>>> at >>>> java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) >>>> at com.sun.javafx.tk.RenderJob.run(RenderJob.java:58) >>>> at >>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor. >>>> java:1142) >>>> at >>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor >>>> .java:617) >>>> at >>>> com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.run(Quantu >>>> mRenderer.java:125) >>>> at java.lang.Thread.run(Thread.java:745) >>>> >>>> Maurice. >>> >> From chien.yang at oracle.com Mon Feb 29 19:17:59 2016 From: chien.yang at oracle.com (Chien Yang) Date: Mon, 29 Feb 2016 11:17:59 -0800 Subject: GLS language errors (Was: Internal error: Error loading stock shader FillRoundRect_LinearGradient,_PAD on Vivante ARM) In-Reply-To: <56D48F7A.3060301@cuhka.com> References: <56D4785E.3050109@cuhka.com> <56D48F7A.3060301@cuhka.com> Message-ID: <56D49967.4040001@oracle.com> Thanks for the information. It is worth filing a JIRA with a detail information of your embedded device at this point. https://wiki.openjdk.java.net/display/OpenJFX/Submitting+a+Bug+Report Thanks, - Chien On 2/29/2016 10:35 AM, Maurice wrote: > No, I build them myself from the instructions on the Wiki > . > > > Maurice. > > Op 29-02-16 om 17:49 schreef Chien Yang: >> I have a quick question. Did you get your embedded JavaFX library >> from Glueon? >> >> http://gluonhq.com/open-source/javafxports/downloads/ >> >> - Chien >> >> >> On 2/29/16, 7:21 AM, Maurice wrote: >>> Should I file a bug? I can't determine whether this is a client >>> platform issue or a major bug in the EGL that JavaFX is using. In >>> any case, it does not work on my embedded device. >>> >>> Maurice. >>> >>> Op 28-02-16 om 18:33 schreef Maurice: >>>> When I run the glslangValidator on >>>> FillRoundRect_LinearGradient_PAD.frag it gives the following error: >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> >>>> When I move pixcoord's declaration on line 19 into the main() >>>> function it gives no errors. >>>> >>>> This is the full output of find -name "*.frag" -exec >>>> glslangValidator {} \; >>>> >>>> ERROR: 0:53: 'oTexCoords' : undeclared identifier >>>> ERROR: 0:53: 'texture2D' : no matching overloaded function found >>>> ERROR: 0:53: '=' : cannot convert from 'const float' to 'temp >>>> highp 4-component vector of float' >>>> ERROR: 3 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:55: 'oTexCoords' : undeclared identifier >>>> ERROR: 0:55: 'texture2D' : no matching overloaded function found >>>> ERROR: 0:55: 'scalar swizzle' : not supported with this profile: es >>>> ERROR: 0:55: 'rgb' : vector field selection out of range >>>> ERROR: 0:55: '=' : cannot convert from 'const float' to 'temp >>>> highp 3-component vector of float' >>>> ERROR: 5 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:53: 'oTexCoords' : undeclared identifier >>>> ERROR: 0:53: 'texture2D' : no matching overloaded function found >>>> WARNING: 0:53: 'return' : type conversion on return values was not >>>> explicitly allowed until version 420 >>>> ERROR: 2 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:55: 'oTexCoords' : undeclared identifier >>>> ERROR: 0:55: 'texture2D' : no matching overloaded function found >>>> ERROR: 0:55: 'scalar swizzle' : not supported with this profile: es >>>> ERROR: 0:55: 'rgb' : vector field selection out of range >>>> ERROR: 0:55: '=' : cannot convert from 'const float' to 'temp >>>> highp 3-component vector of float' >>>> ERROR: 5 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:53: 'oTexCoords' : undeclared identifier >>>> ERROR: 0:53: 'texture2D' : no matching overloaded function found >>>> ERROR: 0:53: '=' : cannot convert from 'const float' to 'temp >>>> highp 4-component vector of float' >>>> ERROR: 3 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:55: 'oTexCoords' : undeclared identifier >>>> ERROR: 0:55: 'texture2D' : no matching overloaded function found >>>> ERROR: 0:55: 'scalar swizzle' : not supported with this profile: es >>>> ERROR: 0:55: 'rgb' : vector field selection out of range >>>> ERROR: 0:55: '=' : cannot convert from 'const float' to 'temp >>>> highp 3-component vector of float' >>>> ERROR: 5 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:53: 'oTexCoords' : undeclared identifier >>>> ERROR: 0:53: 'texture2D' : no matching overloaded function found >>>> WARNING: 0:53: 'return' : type conversion on return values was not >>>> explicitly allowed until version 420 >>>> ERROR: 2 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:55: 'oTexCoords' : undeclared identifier >>>> ERROR: 0:55: 'texture2D' : no matching overloaded function found >>>> ERROR: 0:55: 'scalar swizzle' : not supported with this profile: es >>>> ERROR: 0:55: 'rgb' : vector field selection out of range >>>> ERROR: 0:55: '=' : cannot convert from 'const float' to 'temp >>>> highp 3-component vector of float' >>>> ERROR: 5 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:18: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:17: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> ERROR: 0:19: 'non-constant global initializer' : not supported with >>>> this profile: es >>>> ERROR: 1 compilation errors. No code generated. >>>> >>>> >>>> >>>> Op 27-02-16 om 19:10 schreef Maurice: >>>>> I'm running into the following exception when I start a simple >>>>> JavaFX test program on my ARM based board: >>>>> >>>>> Shader compile log: (21:0) : error : In declarations of global >>>>> variables with no >>>>> storage qualifier or with a const qualifier, any initializer must >>>>> be a constant >>>>> expression >>>>> (103:0) : error : undefined identifier: 'pixcoord' >>>>> >>>>> java.lang.reflect.InvocationTargetException >>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native >>>>> Method) >>>>> at >>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. >>>>> java:62) >>>>> at >>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces >>>>> sorImpl.java:43) >>>>> at java.lang.reflect.Method.invoke(Method.java:483) >>>>> at >>>>> com.sun.prism.es2.ES2ResourceFactory.createStockShader(ES2ResourceFac >>>>> tory.java:312) >>>>> at >>>>> com.sun.prism.impl.ps.BaseShaderContext.getPaintShader(BaseShaderCont >>>>> ext.java:256) >>>>> at >>>>> com.sun.prism.impl.ps.BaseShaderContext.validatePaintOp(BaseShaderCon >>>>> text.java:477) >>>>> at >>>>> com.sun.prism.impl.ps.BaseShaderContext.validatePaintOp(BaseShaderCon >>>>> text.java:374) >>>>> at >>>>> com.sun.prism.impl.ps.BaseShaderGraphics.renderGeneralRoundedPgram(Ba >>>>> seShaderGraphics.java:842) >>>>> at >>>>> com.sun.prism.impl.ps.BaseShaderGraphics.renderGeneralRoundedRect(Bas >>>>> eShaderGraphics.java:601) >>>>> at >>>>> com.sun.prism.impl.ps.BaseShaderGraphics.fillRoundRect(BaseShaderGrap >>>>> hics.java:1557) >>>>> at >>>>> com.sun.javafx.sg.prism.NGRegion.renderBackgroundRectanglesDirectly(N >>>>> GRegion.java:1119) >>>>> at >>>>> com.sun.javafx.sg.prism.NGRegion.renderBackgroundRectangle(NGRegion.j >>>>> ava:830) >>>>> at >>>>> com.sun.javafx.sg.prism.NGRegion.renderAsRectangle(NGRegion.java:751) >>>>> at >>>>> com.sun.javafx.sg.prism.NGRegion.renderContent(NGRegion.java:572) >>>>> at com.sun.javafx.sg.prism.NGNode.doRender(NGNode.java:2053) >>>>> at com.sun.javafx.sg.prism.NGNode.render(NGNode.java:1945) >>>>> at >>>>> com.sun.javafx.sg.prism.NGGroup.renderContent(NGGroup.java:235) >>>>> at com.sun.javafx.sg.prism.NGNode.doRender(NGNode.java:2053) >>>>> at com.sun.javafx.sg.prism.NGNode.render(NGNode.java:1945) >>>>> at >>>>> com.sun.javafx.tk.quantum.ViewPainter.doPaint(ViewPainter.java:477) >>>>> at >>>>> com.sun.javafx.tk.quantum.ViewPainter.paintImpl(ViewPainter.java:330) >>>>> at >>>>> com.sun.javafx.tk.quantum.PresentingPainter.run(PresentingPainter.jav >>>>> a:91) >>>>> at >>>>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:51 >>>>> 1) >>>>> at >>>>> java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) >>>>> at com.sun.javafx.tk.RenderJob.run(RenderJob.java:58) >>>>> at >>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor. >>>>> java:1142) >>>>> at >>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor >>>>> .java:617) >>>>> at >>>>> com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.run(Quantu >>>>> mRenderer.java:125) >>>>> at java.lang.Thread.run(Thread.java:745) >>>>> Caused by: java.lang.RuntimeException: Error creating fragment shader >>>>> at >>>>> com.sun.prism.es2.ES2Shader.createFromSource(ES2Shader.java:141) >>>>> at >>>>> com.sun.prism.es2.ES2Shader.createFromSource(ES2Shader.java:173) >>>>> at >>>>> com.sun.prism.es2.ES2ResourceFactory.createShader(ES2ResourceFactory. >>>>> java:224) >>>>> at >>>>> com.sun.prism.shader.FillRoundRect_LinearGradient_PAD_Loader.loadShad >>>>> er(FillRoundRect_LinearGradient_PAD_Loader.java:53) >>>>> ... 30 more >>>>> java.lang.InternalError: Error loading stock shader >>>>> FillRoundRect_LinearGradient >>>>> _PAD >>>>> at >>>>> com.sun.prism.es2.ES2ResourceFactory.createStockShader(ES2ResourceFac >>>>> tory.java:315) >>>>> at >>>>> com.sun.prism.impl.ps.BaseShaderContext.getPaintShader(BaseShaderCont >>>>> ext.java:256) >>>>> at >>>>> com.sun.prism.impl.ps.BaseShaderContext.validatePaintOp(BaseShaderCon >>>>> text.java:477) >>>>> at >>>>> com.sun.prism.impl.ps.BaseShaderContext.validatePaintOp(BaseShaderCon >>>>> text.java:374) >>>>> at >>>>> com.sun.prism.impl.ps.BaseShaderGraphics.renderGeneralRoundedPgram(Ba >>>>> seShaderGraphics.java:842) >>>>> at >>>>> com.sun.prism.impl.ps.BaseShaderGraphics.renderGeneralRoundedRect(Bas >>>>> eShaderGraphics.java:601) >>>>> at >>>>> com.sun.prism.impl.ps.BaseShaderGraphics.fillRoundRect(BaseShaderGrap >>>>> hics.java:1557) >>>>> at >>>>> com.sun.javafx.sg.prism.NGRegion.renderBackgroundRectanglesDirectly(N >>>>> GRegion.java:1119) >>>>> at >>>>> com.sun.javafx.sg.prism.NGRegion.renderBackgroundRectangle(NGRegion.j >>>>> ava:830) >>>>> at >>>>> com.sun.javafx.sg.prism.NGRegion.renderAsRectangle(NGRegion.java:751) >>>>> at >>>>> com.sun.javafx.sg.prism.NGRegion.renderContent(NGRegion.java:572) >>>>> at com.sun.javafx.sg.prism.NGNode.doRender(NGNode.java:2053) >>>>> at com.sun.javafx.sg.prism.NGNode.render(NGNode.java:1945) >>>>> at >>>>> com.sun.javafx.sg.prism.NGGroup.renderContent(NGGroup.java:235) >>>>> at com.sun.javafx.sg.prism.NGNode.doRender(NGNode.java:2053) >>>>> at com.sun.javafx.sg.prism.NGNode.render(NGNode.java:1945) >>>>> at >>>>> com.sun.javafx.tk.quantum.ViewPainter.doPaint(ViewPainter.java:477) >>>>> at >>>>> com.sun.javafx.tk.quantum.ViewPainter.paintImpl(ViewPainter.java:330) >>>>> at >>>>> com.sun.javafx.tk.quantum.PresentingPainter.run(PresentingPainter.jav >>>>> a:91) >>>>> at >>>>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:51 >>>>> 1) >>>>> at >>>>> java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) >>>>> at com.sun.javafx.tk.RenderJob.run(RenderJob.java:58) >>>>> at >>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor. >>>>> java:1142) >>>>> at >>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor >>>>> .java:617) >>>>> at >>>>> com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.run(Quantu >>>>> mRenderer.java:125) >>>>> at java.lang.Thread.run(Thread.java:745) >>>>> >>>>> Maurice. >>>> >>> > > > From johan.vos at gluonhq.com Mon Feb 29 19:45:13 2016 From: johan.vos at gluonhq.com (Johan Vos) Date: Mon, 29 Feb 2016 20:45:13 +0100 Subject: GLS language errors (Was: Internal error: Error loading stock shader FillRoundRect_LinearGradient,_PAD on Vivante ARM) In-Reply-To: <56D32F81.7060708@cuhka.com> References: <56D1E6A4.80301@cuhka.com> <56D32F81.7060708@cuhka.com> Message-ID: Hi, It seems to me you might be running in the same issue we had on Android with the recent Adreno drivers: http://mail.openjdk.java.net/pipermail/openjfx-dev/2015-July/017575.html See that thread for discussion, and for a fix-proposal here: https://bitbucket.org/javafxports/8u60-rt/commits/595633bbaae36f98d85d47d276294442ea43488c Reading back that thread, I still have a todo on trying to find a generic solution for this... - Johan On Sun, Feb 28, 2016 at 6:33 PM, Maurice wrote: > When I run the glslangValidator on FillRoundRect_LinearGradient_PAD.frag > it gives the following error: > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > > When I move pixcoord's declaration on line 19 into the main() function it > gives no errors. > > This is the full output of find -name "*.frag" -exec glslangValidator {} \; > > ERROR: 0:53: 'oTexCoords' : undeclared identifier > ERROR: 0:53: 'texture2D' : no matching overloaded function found > ERROR: 0:53: '=' : cannot convert from 'const float' to 'temp highp > 4-component vector of float' > ERROR: 3 compilation errors. No code generated. > > > ERROR: 0:55: 'oTexCoords' : undeclared identifier > ERROR: 0:55: 'texture2D' : no matching overloaded function found > ERROR: 0:55: 'scalar swizzle' : not supported with this profile: es > ERROR: 0:55: 'rgb' : vector field selection out of range > ERROR: 0:55: '=' : cannot convert from 'const float' to 'temp highp > 3-component vector of float' > ERROR: 5 compilation errors. No code generated. > > > ERROR: 0:53: 'oTexCoords' : undeclared identifier > ERROR: 0:53: 'texture2D' : no matching overloaded function found > WARNING: 0:53: 'return' : type conversion on return values was not > explicitly allowed until version 420 > ERROR: 2 compilation errors. No code generated. > > > ERROR: 0:55: 'oTexCoords' : undeclared identifier > ERROR: 0:55: 'texture2D' : no matching overloaded function found > ERROR: 0:55: 'scalar swizzle' : not supported with this profile: es > ERROR: 0:55: 'rgb' : vector field selection out of range > ERROR: 0:55: '=' : cannot convert from 'const float' to 'temp highp > 3-component vector of float' > ERROR: 5 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:53: 'oTexCoords' : undeclared identifier > ERROR: 0:53: 'texture2D' : no matching overloaded function found > ERROR: 0:53: '=' : cannot convert from 'const float' to 'temp highp > 4-component vector of float' > ERROR: 3 compilation errors. No code generated. > > > ERROR: 0:55: 'oTexCoords' : undeclared identifier > ERROR: 0:55: 'texture2D' : no matching overloaded function found > ERROR: 0:55: 'scalar swizzle' : not supported with this profile: es > ERROR: 0:55: 'rgb' : vector field selection out of range > ERROR: 0:55: '=' : cannot convert from 'const float' to 'temp highp > 3-component vector of float' > ERROR: 5 compilation errors. No code generated. > > > ERROR: 0:53: 'oTexCoords' : undeclared identifier > ERROR: 0:53: 'texture2D' : no matching overloaded function found > WARNING: 0:53: 'return' : type conversion on return values was not > explicitly allowed until version 420 > ERROR: 2 compilation errors. No code generated. > > > ERROR: 0:55: 'oTexCoords' : undeclared identifier > ERROR: 0:55: 'texture2D' : no matching overloaded function found > ERROR: 0:55: 'scalar swizzle' : not supported with this profile: es > ERROR: 0:55: 'rgb' : vector field selection out of range > ERROR: 0:55: '=' : cannot convert from 'const float' to 'temp highp > 3-component vector of float' > ERROR: 5 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported with this > profile: es > ERROR: 1 compilation errors. No code generated. > > > > Op 27-02-16 om 19:10 schreef Maurice: > >> I'm running into the following exception when I start a simple JavaFX >> test program on my ARM based board: >> >> Shader compile log: (21:0) : error : In declarations of global variables >> with no >> storage qualifier or with a const qualifier, any initializer must be a >> constant >> expression >> (103:0) : error : undefined identifier: 'pixcoord' >> >> java.lang.reflect.InvocationTargetException >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> at >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. >> java:62) >> at >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces >> sorImpl.java:43) >> at java.lang.reflect.Method.invoke(Method.java:483) >> at >> com.sun.prism.es2.ES2ResourceFactory.createStockShader(ES2ResourceFac >> tory.java:312) >> at com.sun.prism.impl.ps >> .BaseShaderContext.getPaintShader(BaseShaderCont >> ext.java:256) >> at com.sun.prism.impl.ps >> .BaseShaderContext.validatePaintOp(BaseShaderCon >> text.java:477) >> at com.sun.prism.impl.ps >> .BaseShaderContext.validatePaintOp(BaseShaderCon >> text.java:374) >> at com.sun.prism.impl.ps >> .BaseShaderGraphics.renderGeneralRoundedPgram(Ba >> seShaderGraphics.java:842) >> at com.sun.prism.impl.ps >> .BaseShaderGraphics.renderGeneralRoundedRect(Bas >> eShaderGraphics.java:601) >> at com.sun.prism.impl.ps >> .BaseShaderGraphics.fillRoundRect(BaseShaderGrap >> hics.java:1557) >> at >> com.sun.javafx.sg.prism.NGRegion.renderBackgroundRectanglesDirectly(N >> GRegion.java:1119) >> at >> com.sun.javafx.sg.prism.NGRegion.renderBackgroundRectangle(NGRegion.j >> ava:830) >> at >> com.sun.javafx.sg.prism.NGRegion.renderAsRectangle(NGRegion.java:751) >> at >> com.sun.javafx.sg.prism.NGRegion.renderContent(NGRegion.java:572) >> at com.sun.javafx.sg.prism.NGNode.doRender(NGNode.java:2053) >> at com.sun.javafx.sg.prism.NGNode.render(NGNode.java:1945) >> at com.sun.javafx.sg.prism.NGGroup.renderContent(NGGroup.java:235) >> at com.sun.javafx.sg.prism.NGNode.doRender(NGNode.java:2053) >> at com.sun.javafx.sg.prism.NGNode.render(NGNode.java:1945) >> at >> com.sun.javafx.tk.quantum.ViewPainter.doPaint(ViewPainter.java:477) >> at >> com.sun.javafx.tk.quantum.ViewPainter.paintImpl(ViewPainter.java:330) >> at >> com.sun.javafx.tk.quantum.PresentingPainter.run(PresentingPainter.jav >> a:91) >> at >> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:51 >> 1) >> at >> java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) >> at com.sun.javafx.tk.RenderJob.run(RenderJob.java:58) >> at >> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor. >> java:1142) >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor >> .java:617) >> at >> com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.run(Quantu >> mRenderer.java:125) >> at java.lang.Thread.run(Thread.java:745) >> Caused by: java.lang.RuntimeException: Error creating fragment shader >> at >> com.sun.prism.es2.ES2Shader.createFromSource(ES2Shader.java:141) >> at >> com.sun.prism.es2.ES2Shader.createFromSource(ES2Shader.java:173) >> at >> com.sun.prism.es2.ES2ResourceFactory.createShader(ES2ResourceFactory. >> java:224) >> at >> com.sun.prism.shader.FillRoundRect_LinearGradient_PAD_Loader.loadShad >> er(FillRoundRect_LinearGradient_PAD_Loader.java:53) >> ... 30 more >> java.lang.InternalError: Error loading stock shader >> FillRoundRect_LinearGradient >> _PAD >> at >> com.sun.prism.es2.ES2ResourceFactory.createStockShader(ES2ResourceFac >> tory.java:315) >> at com.sun.prism.impl.ps >> .BaseShaderContext.getPaintShader(BaseShaderCont >> ext.java:256) >> at com.sun.prism.impl.ps >> .BaseShaderContext.validatePaintOp(BaseShaderCon >> text.java:477) >> at com.sun.prism.impl.ps >> .BaseShaderContext.validatePaintOp(BaseShaderCon >> text.java:374) >> at com.sun.prism.impl.ps >> .BaseShaderGraphics.renderGeneralRoundedPgram(Ba >> seShaderGraphics.java:842) >> at com.sun.prism.impl.ps >> .BaseShaderGraphics.renderGeneralRoundedRect(Bas >> eShaderGraphics.java:601) >> at com.sun.prism.impl.ps >> .BaseShaderGraphics.fillRoundRect(BaseShaderGrap >> hics.java:1557) >> at >> com.sun.javafx.sg.prism.NGRegion.renderBackgroundRectanglesDirectly(N >> GRegion.java:1119) >> at >> com.sun.javafx.sg.prism.NGRegion.renderBackgroundRectangle(NGRegion.j >> ava:830) >> at >> com.sun.javafx.sg.prism.NGRegion.renderAsRectangle(NGRegion.java:751) >> at >> com.sun.javafx.sg.prism.NGRegion.renderContent(NGRegion.java:572) >> at com.sun.javafx.sg.prism.NGNode.doRender(NGNode.java:2053) >> at com.sun.javafx.sg.prism.NGNode.render(NGNode.java:1945) >> at com.sun.javafx.sg.prism.NGGroup.renderContent(NGGroup.java:235) >> at com.sun.javafx.sg.prism.NGNode.doRender(NGNode.java:2053) >> at com.sun.javafx.sg.prism.NGNode.render(NGNode.java:1945) >> at >> com.sun.javafx.tk.quantum.ViewPainter.doPaint(ViewPainter.java:477) >> at >> com.sun.javafx.tk.quantum.ViewPainter.paintImpl(ViewPainter.java:330) >> at >> com.sun.javafx.tk.quantum.PresentingPainter.run(PresentingPainter.jav >> a:91) >> at >> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:51 >> 1) >> at >> java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) >> at com.sun.javafx.tk.RenderJob.run(RenderJob.java:58) >> at >> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor. >> java:1142) >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor >> .java:617) >> at >> com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.run(Quantu >> mRenderer.java:125) >> at java.lang.Thread.run(Thread.java:745) >> >> Maurice. >> > > From info at cuhka.com Mon Feb 29 20:04:52 2016 From: info at cuhka.com (Maurice) Date: Mon, 29 Feb 2016 21:04:52 +0100 Subject: GLS language errors (Was: Internal error: Error loading stock shader FillRoundRect_LinearGradient,_PAD on Vivante ARM) In-Reply-To: References: <56D1E6A4.80301@cuhka.com> <56D32F81.7060708@cuhka.com> Message-ID: <56D4A464.9030509@cuhka.com> It looks like the same issue indeed and I second the remark "Don't refer to e.g. gl_FragCoord in the header, but put it in main." When running the egl language validator there were additional errors though: ERROR: 0:53: 'texture2D' : no matching overloaded function found WARNING: 0:53: 'return' : type conversion on return values was not explicitly allowed until version 420 Should I still file a bug, or put additional information in an existing one? As an aside, for me to continue, should I try to build a Yocto image with an older driver? Maurice. Op 29-02-16 om 20:45 schreef Johan Vos: > Hi, > > It seems to me you might be running in the same issue we had on > Android with the recent Adreno drivers: > http://mail.openjdk.java.net/pipermail/openjfx-dev/2015-July/017575.html > > See that thread for discussion, and for a fix-proposal here: > https://bitbucket.org/javafxports/8u60-rt/commits/595633bbaae36f98d85d47d276294442ea43488c > > Reading back that thread, I still have a todo on trying to find a > generic solution for this... > > - Johan > > On Sun, Feb 28, 2016 at 6:33 PM, Maurice > wrote: > > When I run the glslangValidator on > FillRoundRect_LinearGradient_PAD.frag it gives the following error: > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > > When I move pixcoord's declaration on line 19 into the main() > function it gives no errors. > > This is the full output of find -name "*.frag" -exec > glslangValidator {} \; > > ERROR: 0:53: 'oTexCoords' : undeclared identifier > ERROR: 0:53: 'texture2D' : no matching overloaded function found > ERROR: 0:53: '=' : cannot convert from 'const float' to 'temp > highp 4-component vector of float' > ERROR: 3 compilation errors. No code generated. > > > ERROR: 0:55: 'oTexCoords' : undeclared identifier > ERROR: 0:55: 'texture2D' : no matching overloaded function found > ERROR: 0:55: 'scalar swizzle' : not supported with this profile: es > ERROR: 0:55: 'rgb' : vector field selection out of range > ERROR: 0:55: '=' : cannot convert from 'const float' to 'temp > highp 3-component vector of float' > ERROR: 5 compilation errors. No code generated. > > > ERROR: 0:53: 'oTexCoords' : undeclared identifier > ERROR: 0:53: 'texture2D' : no matching overloaded function found > WARNING: 0:53: 'return' : type conversion on return values was not > explicitly allowed until version 420 > ERROR: 2 compilation errors. No code generated. > > > ERROR: 0:55: 'oTexCoords' : undeclared identifier > ERROR: 0:55: 'texture2D' : no matching overloaded function found > ERROR: 0:55: 'scalar swizzle' : not supported with this profile: es > ERROR: 0:55: 'rgb' : vector field selection out of range > ERROR: 0:55: '=' : cannot convert from 'const float' to 'temp > highp 3-component vector of float' > ERROR: 5 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:53: 'oTexCoords' : undeclared identifier > ERROR: 0:53: 'texture2D' : no matching overloaded function found > ERROR: 0:53: '=' : cannot convert from 'const float' to 'temp > highp 4-component vector of float' > ERROR: 3 compilation errors. No code generated. > > > ERROR: 0:55: 'oTexCoords' : undeclared identifier > ERROR: 0:55: 'texture2D' : no matching overloaded function found > ERROR: 0:55: 'scalar swizzle' : not supported with this profile: es > ERROR: 0:55: 'rgb' : vector field selection out of range > ERROR: 0:55: '=' : cannot convert from 'const float' to 'temp > highp 3-component vector of float' > ERROR: 5 compilation errors. No code generated. > > > ERROR: 0:53: 'oTexCoords' : undeclared identifier > ERROR: 0:53: 'texture2D' : no matching overloaded function found > WARNING: 0:53: 'return' : type conversion on return values was not > explicitly allowed until version 420 > ERROR: 2 compilation errors. No code generated. > > > ERROR: 0:55: 'oTexCoords' : undeclared identifier > ERROR: 0:55: 'texture2D' : no matching overloaded function found > ERROR: 0:55: 'scalar swizzle' : not supported with this profile: es > ERROR: 0:55: 'rgb' : vector field selection out of range > ERROR: 0:55: '=' : cannot convert from 'const float' to 'temp > highp 3-component vector of float' > ERROR: 5 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:18: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:17: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > ERROR: 0:19: 'non-constant global initializer' : not supported > with this profile: es > ERROR: 1 compilation errors. No code generated. > > > > Op 27-02-16 om 19:10 schreef Maurice: > > I'm running into the following exception when I start a simple > JavaFX test program on my ARM based board: > > Shader compile log: (21:0) : error : In declarations of global > variables with no > storage qualifier or with a const qualifier, any initializer > must be a constant > expression > (103:0) : error : undefined identifier: 'pixcoord' > > java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. > java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > sorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at > com.sun.prism.es2.ES2ResourceFactory.createStockShader(ES2ResourceFac > tory.java:312) > at com.sun.prism.impl.ps > .BaseShaderContext.getPaintShader(BaseShaderCont > ext.java:256) > at com.sun.prism.impl.ps > .BaseShaderContext.validatePaintOp(BaseShaderCon > text.java:477) > at com.sun.prism.impl.ps > .BaseShaderContext.validatePaintOp(BaseShaderCon > text.java:374) > at com.sun.prism.impl.ps > .BaseShaderGraphics.renderGeneralRoundedPgram(Ba > seShaderGraphics.java:842) > at com.sun.prism.impl.ps > .BaseShaderGraphics.renderGeneralRoundedRect(Bas > eShaderGraphics.java:601) > at com.sun.prism.impl.ps > .BaseShaderGraphics.fillRoundRect(BaseShaderGrap > hics.java:1557) > at > com.sun.javafx.sg.prism.NGRegion.renderBackgroundRectanglesDirectly(N > GRegion.java:1119) > at > com.sun.javafx.sg.prism.NGRegion.renderBackgroundRectangle(NGRegion.j > ava:830) > at > com.sun.javafx.sg.prism.NGRegion.renderAsRectangle(NGRegion.java:751) > at > com.sun.javafx.sg.prism.NGRegion.renderContent(NGRegion.java:572) > at > com.sun.javafx.sg.prism.NGNode.doRender(NGNode.java:2053) > at com.sun.javafx.sg.prism.NGNode.render(NGNode.java:1945) > at > com.sun.javafx.sg.prism.NGGroup.renderContent(NGGroup.java:235) > at > com.sun.javafx.sg.prism.NGNode.doRender(NGNode.java:2053) > at com.sun.javafx.sg.prism.NGNode.render(NGNode.java:1945) > at > com.sun.javafx.tk.quantum.ViewPainter.doPaint(ViewPainter.java:477) > at > com.sun.javafx.tk.quantum.ViewPainter.paintImpl(ViewPainter.java:330) > at > com.sun.javafx.tk.quantum.PresentingPainter.run(PresentingPainter.jav > a:91) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:51 > 1) > at > java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) > at com.sun.javafx.tk.RenderJob.run(RenderJob.java:58) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor. > java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor > .java:617) > at > com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.run(Quantu > mRenderer.java:125) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.RuntimeException: Error creating fragment > shader > at > com.sun.prism.es2.ES2Shader.createFromSource(ES2Shader.java:141) > at > com.sun.prism.es2.ES2Shader.createFromSource(ES2Shader.java:173) > at > com.sun.prism.es2.ES2ResourceFactory.createShader(ES2ResourceFactory. > java:224) > at > com.sun.prism.shader.FillRoundRect_LinearGradient_PAD_Loader.loadShad > er(FillRoundRect_LinearGradient_PAD_Loader.java:53) > ... 30 more > java.lang.InternalError: Error loading stock shader > FillRoundRect_LinearGradient > _PAD > at > com.sun.prism.es2.ES2ResourceFactory.createStockShader(ES2ResourceFac > tory.java:315) > at com.sun.prism.impl.ps > .BaseShaderContext.getPaintShader(BaseShaderCont > ext.java:256) > at com.sun.prism.impl.ps > .BaseShaderContext.validatePaintOp(BaseShaderCon > text.java:477) > at com.sun.prism.impl.ps > .BaseShaderContext.validatePaintOp(BaseShaderCon > text.java:374) > at com.sun.prism.impl.ps > .BaseShaderGraphics.renderGeneralRoundedPgram(Ba > seShaderGraphics.java:842) > at com.sun.prism.impl.ps > .BaseShaderGraphics.renderGeneralRoundedRect(Bas > eShaderGraphics.java:601) > at com.sun.prism.impl.ps > .BaseShaderGraphics.fillRoundRect(BaseShaderGrap > hics.java:1557) > at > com.sun.javafx.sg.prism.NGRegion.renderBackgroundRectanglesDirectly(N > GRegion.java:1119) > at > com.sun.javafx.sg.prism.NGRegion.renderBackgroundRectangle(NGRegion.j > ava:830) > at > com.sun.javafx.sg.prism.NGRegion.renderAsRectangle(NGRegion.java:751) > at > com.sun.javafx.sg.prism.NGRegion.renderContent(NGRegion.java:572) > at > com.sun.javafx.sg.prism.NGNode.doRender(NGNode.java:2053) > at com.sun.javafx.sg.prism.NGNode.render(NGNode.java:1945) > at > com.sun.javafx.sg.prism.NGGroup.renderContent(NGGroup.java:235) > at > com.sun.javafx.sg.prism.NGNode.doRender(NGNode.java:2053) > at com.sun.javafx.sg.prism.NGNode.render(NGNode.java:1945) > at > com.sun.javafx.tk.quantum.ViewPainter.doPaint(ViewPainter.java:477) > at > com.sun.javafx.tk.quantum.ViewPainter.paintImpl(ViewPainter.java:330) > at > com.sun.javafx.tk.quantum.PresentingPainter.run(PresentingPainter.jav > a:91) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:51 > 1) > at > java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) > at com.sun.javafx.tk.RenderJob.run(RenderJob.java:58) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor. > java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor > .java:617) > at > com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.run(Quantu > mRenderer.java:125) > at java.lang.Thread.run(Thread.java:745) > > Maurice. > > > From kevin.rushforth at oracle.com Mon Feb 29 21:04:22 2016 From: kevin.rushforth at oracle.com (Kevin Rushforth) Date: Mon, 29 Feb 2016 13:04:22 -0800 Subject: 9-dev unlocked following sanity testing Message-ID: <56D4B256.8000709@oracle.com> From bryanb at webbtide.com Mon Feb 29 22:19:02 2016 From: bryanb at webbtide.com (Bryan Buchanan) Date: Tue, 1 Mar 2016 08:19:02 +1000 Subject: Canvas and Keyboard events Message-ID: I have this layout: BorderPane with a MenuBar (top) and TabPane (center) I have two initial tabs. Selecting some menu option will create a new tab. One of the menu options creates a drawing surface, which is made up of a StackPane with a Canvas. The canvas has FocusTraversable set to true and has keyboard event handlers: canvas.setFocusTraversable(true); canvas.setOnKeyPressed((KeyEvent e) -> handleHotKeys(e)); canvas.setOnKeyTyped((KeyEvent e) -> handleChars(e)); The canvas responds to keyboards events - I can get "a", "b", "c" etc, DEL, INS, END and other keys I'm interested in. However, when I press "left arrow" or "right arrow", the MenuBar gets focus. If I then click in the canvas, the Tab control gets focus. If I keep pressing an arrow key, the tabs cycle though, until I get back to the tab with the canvas, then the arrow events are sent to the canvas, and it works like it should. I don't understand why the arrow key events don't go first to the canvas. Any clues appreciated.