hi,
i would like to build to crosswalk 7 but i get this log builf fail
Build Log:
- Warning: The Crosswalk team has updated Crosswalk 7 with the CVE security fixes for Open SSL to bring Crosswalk 7 into compliance. This was accomplished by updating the base Chromium version used in Crosswalk which fixes the known Open SSL vulnerabilities. The Chromium team did not update the Open SSL version and Crosswalk will still report version 1.0.1e. For more information, visit <a style="color: #9bcc44" href="https://software.intel.com/en-us/html5/articles/crosswalk-7-open-ssl-update" target="_blank">Crosswalk 7 Open SSL Update</a>
anyone can help me please ?
thanks in advance
連結已複製
The warning is just a warning, it does not prevent you from building a Crosswalk 7 app. Note that at some point you will not be able to submit a Crosswalk 7 to the Google store, because of that warning. See the post.
See the "You can view the log of the Android build here" line directly above the summary build log? That "here" link contains a detailed build log. Attach that detailed build log to this forum thread.
Please! DO NOT PASTE the detailed build log into your forum post, it is extremely difficult to scan and review when you do that. Please copy it into a text file and ATTACH that text file to this thread using the "Attach Media" button below.
Paul Fischer (Intel) wrote:
See the "You can view the log of the Android build here" line directly above the summary build log? That "here" link contains a detailed build log. Attach that detailed build log to this forum thread.
Please! DO NOT PASTE the detailed build log into your forum post, it is extremely difficult to scan and review when you do that. Please copy it into a text file and ATTACH that text file to this thread using the "Attach Media" button below.
hi,
thanks for reply
the build fail log is n text file attached
however ... you told that i can't upload apk with cw7 to google play ? why ?
also when i trty with new cocoon is work great but with cw10,11,12 and also the shared 14 the game is lag ...
Read this page for info regarding why you cannot push Crosswalk 7 apps to Google Play: https://software.intel.com/en-us/xdk/docs/using-the-build-tab#recbuildversions
The Crosswalk team is working on fixing the lag issues, this is outside of our direct control. We are aware of the issue and work is being done to address it. Did you try the Crosswalk Shared option? That uses 14, which is supposed to have a fix for some of the performance problems. Even if you choose to not use the shared option, you can use it to determine if the performance is fixed. There will be an embedded build option. Please see this doc page for more info: https://software.intel.com/en-us/xdk/docs/choosing-crosswalk-build-options-shared-or-embedded
The AdMob plugin is the source of the problem. I cannot tell you why it is causing the problem, but it is. You might need to get some help from the AdMob author to understand what is going on there. Was the plugin added by Construct2 or are you doing this yourself? Here's a link to that plugin author's stuff: http://cranberrygame.github.io/
Paul Fischer (Intel) wrote:
Read this page for info regarding why you cannot push Crosswalk 7 apps to Google Play: https://software.intel.com/en-us/xdk/docs/using-the-build-tab#recbuildve...
The Crosswalk team is working on fixing the lag issues, this is outside of our direct control. We are aware of the issue and work is being done to address it. Did you try the Crosswalk Shared option? That uses 14, which is supposed to have a fix for some of the performance problems. Even if you choose to not use the shared option, you can use it to determine if the performance is fixed. There will be an embedded build option. Please see this doc page for more info: https://software.intel.com/en-us/xdk/docs/choosing-crosswalk-build-optio...
The AdMob plugin is the source of the problem. I cannot tell you why it is causing the problem, but it is. You might need to get some help from the AdMob author to understand what is going on there. Was the plugin added by Construct2 or are you doing this yourself? Here's a link to that plugin author's stuff: http://cranberrygame.github.io/
hi,
i'm not using admob ...
also i did try shared cw14 but still same ...
as i told you the game is run at 54-58fsp but always lag
when i use cocoon it os stable and never lag
i'm using s4 mini
:( sad news
1) You will get hardwareAccelerated if the width=device-width is set in your "meta viewport" tag inside your index.html file. This should be the case, but you might want to double-check. In general, Crosswalk builds include hardware acceleration.
2) That pluggable Crosswalk webview is not available through our build system (yet). It will be automatically used when we have a CLI 5 build system in place AND everything is in place to build a Crosswalk pluggable webview app. Our embedded Crosswalk builds are essentially the same as that, they use the same Crosswalk library to implement the Crosswalk runtime, which is provided by the Crosswalk project team. They provide the library binaries for all of the Crosswalk builds.
3) I am not familiar with the ludei plugin, but I believe it also requires a CLI 5 build system, which we do not yet have in place.
Can you provide a sample game that illustrates the issue you are experiencing, as a complete project source package, in a ZIP file that you attach to this thread (via private message is fine) so I can forward it to the Crosswalk team? In addition, provide a build APK using the Crosswalk build and the Cocoon build so I can show the Crosswalk project.
p.s. Here's what is being included in your app, from a plugin perspective, based on the beginning of the detailed build log you provided:
Installing "org.apache.cordova.device" for android Installing "org.apache.cordova.splashscreen" for android Installing "org.apache.cordova.vibration" for android Installing "nl.x-services.plugins.socialsharing" for android Installing "cordova-plugin-ad-appodeal" for android Fetching plugin "https://github.com/cranberrygame/cordova-plugin-ad-chartboost" via git clone Installing "cordova-plugin-ad-chartboost" for android Fetching plugin "https://github.com/cranberrygame/cordova-plugin-ad-unityads" via git clone Installing "cordova-plugin-ad-unityads" for android Fetching plugin "https://github.com/cranberrygame/cordova-plugin-ad-admob" via git clone Installing "cordova-plugin-ad-admob" for android Fetching plugin "https://github.com/cranberrygame/cordova-plugin-ad-admobsdk" via git clone Installing "cordova-plugin-ad-admobsdk" for android Fetching plugin "com.google.playservices@21.0.0" via plugin registry npm http GET http://registry.cordova.io/com.google.playservices/21.0.0 npm http 304 http://registry.cordova.io/com.google.playservices/21.0.0 Installing "com.google.playservices" for android Updated local.properties No project name specified, using project folder name 'google-play-services_lib'. If you wish to change it, edit the first line of build.xml. Added file .../JumpyBall/com.google.playservices/google-play-services_lib/build.xml Added file .../JumpyBall/com.google.playservices/google-play-services_lib/proguard-project.txt Fetching plugin "https://github.com/cranberrygame/cordova-plugin-ad-mopub" via git clone Installing "cordova-plugin-ad-mopub" for android Fetching plugin "com.google.playservices@21.0.0" via plugin registry Updated local.properties Updated file .../JumpyBall/com.google.playservices/google-play-services_lib/proguard-project.txt Updated local.properties Renamed build.properties to ant.properties No project name specified, using project folder name 'mopub-sdk'. If you wish to change it, edit the first line of build.xml. Added file .../JumpyBall/cordova-plugin-ad-mopub/mopub-sdk/build.xml Added file .../JumpyBall/cordova-plugin-ad-mopub/mopub-sdk/proguard-project.txt Plugin "cordova-plugin-ad-chartboost" already installed on android. Installing "cordova-plugin-game" for android Fetching plugin "com.google.playservices@21.0.0" via plugin registry Fetching plugin "android.support.v4@1.0.0" via plugin registry npm http GET http://registry.cordova.io/android.support.v4/1.0.0 npm http 304 http://registry.cordova.io/android.support.v4/1.0.0 Installing "android.support.v4" for android Installing "cordova-plugin-payment-iap" for android Installing "org.apache.cordova.dialogs" for android Installing "org.apache.cordova.inappbrowser" for android Installing "cordova-plugin-promotion-reviewapp" for android
Note the references to "cordova-plugin-ad-*" in the first lines -- these are plugins that are being added to your build due to plugins that either you or Construct2 has added. The XDK is not adding these automatically, we only build what your project tells us to build.
Likewise, see the end of the build log to see the specific errors, which point back to one of those plugins.
Yes, two APKs (one Crosswalk built and one Cocoon built) and the Crosswalk project in a ZIP file. You can send a private message by pushing this Send author a message link and then attach the items to that private message. I won't be able to do anything with them until sometime next week.
@Matrix -- I installed and ran the two APK files you sent me. A few observations:
- I did not notice any significant difference in performance on my Samsung S3 (of course, I don't fully understand how to play the game, but I did not see any difference in speed or smoothness in the ball or the ramp motion or the explosions with my fiddling around).
- Your project is not organized properly to get the minimum size, you have the project directory and the source directory pointing at the same root, this results in including the plugins directory inside of your built application, which is wasted space, that directory is not part of your source and is not required by the build system.
How did you build this game? Did you use a tool like Construct2 or something similar? If so, how did you go about turning it into an XDK project. I'd like to fix the way we "import" projects, it does not work well, but I need a better understanding of the process you are using.
Do the following to your project directory:
- from within the XDK, go to the Projects tab for this project and rectangle with the little x on it in the upper right corner of the screen (below the twitter feed icon and the login icon) -- this will "delete" the project from the XDK (it only removes it from the Projects tab, nothing more than that)
- exit the XDK
- move the *.xml files that are currently inside the www directory up one level, even with the www directory (to your "deathjumpandroid" directory) -- you
- move the plugins directory up one directory (also to your "deathjumpandroid" directory)
- move the *.xdk and *.xdke files up one directory (also to your "deathjumpandroid" directory)
Once all of the above has been done, restart the XDK and use the "Open An Intel XDK Project" at the bottom left of the Projects tab and then use the file explorer dialog that appears to locate the "DeathJump3.xdk" file that you relocated up one directory.
After you have the project in your list of projects, you may have to reconfigure the "source" directory. From the Projects tab, in the "Project Info" panel, locate the line named "Source Directory." At the far right of that line is a folder icon, push the folder icon and then select the "www" directory that is located inside your project directory.
After all of the above is done your project should be "normal" and will not be unnecessarily adding dead files into the build. You might have to redo the icons and splash screens, but I think those should come out okay (not sure).
