Native extensions and captive runtime

I'm trying to use native extensions and captive runtime. When I try to create a release, the IDE shows this message "Native extensions are being used in the project but are not supported by the CAPTIVE_RUNTIME_BUNDLE package type. Runtime issues can occur." and I can't continue.
I've been able to compile it using the command-line, but I'm worried about the "runtime issues" that can occur.

Hi,
Sorry, just verified that export release build, with Native Extensions and Captive Runtime bundled for Desktop projects has been fixed and is available in the final release of Flash Builder 4.7.
Thanks,
Hari

Similar Messages

Native extensions and in-app purchase

Hi,
Would AIR 3 support native extensions and in-app purchases on Android and iOS devices? Let me know what timelines are we looking at
Regards
Pulkit

Detailed roadmap information and timelines can be shared under a Non Disclosure Agreement. Contact your local Adobe rep for more information.
Alternatively, join the AIR 3 private pre-release program (in iOS, Android and Playbook) or check out the release notes for the AIR public beta on http://labs.adobe.com/ (only covers AIR desktop at the time of writing).

Native Extensions and Pending Intent

Hi all,
I'm trying to figure out how to get a message back to my AIR application from a Android Native Extension when using a PendingIntent.
The example is from a Notification, creating the notification is fine but I can't get my head around how to receive the pending intent.
I don't really want to launch a new activity, just display the existing AIR one and get access to the FREContext to fire an event.
Any ideas how I can achieve this?
Cheers,
Michael

For anyone that's interested I figured it out.
The answer is in using a BroadcastReceiver and creating a broadcast pending intent.

So are all Android apk's forced too captive runtime now?

I published my Flex app (with a linked native extension) and it was 1.5Mb. But then I upgraded my AIRSDK to 3.7 and now it's 11.7Mb?
Whoa, that's huge!
Thinking this was a Flex problem I built a simple tester AS3 app in Flash Pro, linked in my ane and tried to publish. It went away for a long time then came back with a dialog:
"The APK was packaged successfully, but a warning occurred.
Note: the AIR SDK no longer supports packaging android applications for use with the shared Runtime.
The application has been packaged with a captive Runtime."
So what gives?
And the apk was 9.3Mb.
Can I ask when this started so I know how far I need to fall back? AIR 3.5? (I know 3.4 was ok.)
Is this a permanent thing? Was it really necessary to force all mobile apps to giant captive runtimes?

It's not compatibility with Amazon in general, it's Kindle in particular. Go to this page:
http://www.amazon.com/Adobe-Systems-AIR/dp/B004SRNH10
and on the right side it will tell you what of your devices are compatible, and it says my Kindle isn't. Also, doing a search for Adobe AIR in the store app on Kindle Fire doesn't show any matches.

ADT packaging with native extensions : permission denied error when running remote build.

Hi Team,
We are facing the following error when running the nightly ant build script on Mac machine for our air mobile application. We are using iOS native extensions and package with ADT. This works fine when we run the build as local user in the Mac machine. Earlier we faced some issues due to headless build and we have added the <headless-server>true</headless-server> in corresponding config files (flex-config.xml, airmobile-config.xml). After that we are facing the following error, even when we run the ant build in headless mode using the following command.
ant -Djava.awt.headless=true -f build.xml buildPackage
When running this build as local user in the Mac build machine, we see a window opening with com.adobe.air.ADT while packaging. This is the issue when running nightly build as there is no graphics window.
Can anybody please help how to get rid of this issue for nightly build using adt,jar?
Here is the error from build log:
buildiOSPackageWithNativeExtensionMac:
     [echo] Export the iOS package with Native extension for ApprovalsMobile in Mac
     [java] Exception in thread "main" java.lang.InternalError: Can't connect to window server - not enough permissions.
     [java] at java.lang.ClassLoader$NativeLibrary.load(Native Method)
     [java] at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1827)
     [java] at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1724)
     [java] at java.lang.Runtime.loadLibrary0(Runtime.java:823)
     [java] at java.lang.System.loadLibrary(System.java:1045)
     [java] at sun.security.action.LoadLibraryAction.run(LoadLibraryAction.java:50)
     [java] at java.security.AccessController.doPrivileged(Native Method)
     [java] at java.awt.Toolkit.loadLibraries(Toolkit.java:1605)
     [java] at java.awt.Toolkit.<clinit>(Toolkit.java:1627)
     [java] at java.awt.Dimension.<clinit>(Dimension.java:70)
     [java] at com.adobe.air.validator.ApplicationDescriptorValidator.validateImageUri(ApplicationDescri ptorValidator.java:183)
     [java] at com.adobe.air.validator.ApplicationDescriptorValidator20.validateElement(ApplicationDescr iptorValidator20.java:121)
     [java] at com.adobe.air.validator.ApplicationDescriptorValidator25.validateElement(ApplicationDescr iptorValidator25.java:65)
     [java] at com.adobe.air.validator.ApplicationDescriptorValidator26.validateElement(ApplicationDescr iptorValidator26.java:62)
     [java] at com.adobe.air.validator.ApplicationDescriptorValidator30.validateElement(ApplicationDescr iptorValidator30.java:52)
     [java] at com.adobe.air.validator.ApplicationDescriptorValidator31.validateElement(ApplicationDescr iptorValidator31.java:46)
     [java] at com.adobe.air.validator.DescriptorValidator.endElement(DescriptorValidator.java:239)
     [java] at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser .java:601)
     [java] at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XML DocumentFragmentScannerImpl.java:1782)
     [java] at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDri ver.next(XMLDocumentFragmentScannerImpl.java:2939)
     [java] at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImp l.java:648)
     [java] at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScanne rImpl.java:140)
     [java] at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDo cumentFragmentScannerImpl.java:511)
     [java] at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.ja va:808)
     [java] at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.ja va:737)
     [java] at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119)
     [java] at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java :1205)
     [java] at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.j ava:522)
     [java] at javax.xml.parsers.SAXParser.parse(SAXParser.java:395)
     [java] at javax.xml.parsers.SAXParser.parse(SAXParser.java:198)
     [java] at com.adobe.air.Descriptor.validateXML(Descriptor.java:182)
     [java] at com.adobe.air.Descriptor.<init>(Descriptor.java:56)
     [java] at com.adobe.air.ApplicationDescriptor.<init>(ApplicationDescriptor.java:84)
     [java] at com.adobe.air.ApplicationPackager.validateApplicationDescriptor(ApplicationPackager.java: 101)
     [java] at com.adobe.air.ApplicationPackager.createPackage(ApplicationPackager.java:64)
     [java] at com.adobe.air.ipa.IPAPackager.createPackage(IPAPackager.java:217)
     [java] at com.adobe.air.ADT.parseArgsAndGo(ADT.java:557)
     [java] at com.adobe.air.ADT.run(ADT.java:414)
     [java] at com.adobe.air.ADT.main(ADT.java:464)
Thanks,
Swathi.

Note: Before the above error that were two other errors .
1) The build complained that the adt-bundle-linux toolchain could not be found and required that it be added to .mozconfig. This was done.
2) The build complained that dx could not be found.
The configure file was edited and the values $DX, $AAPT and $AIDL were all set to the adt-bundle-linux/sdk/build-tools/android-4.4 path.
The instructions given on the Mozilla Wiki did not work right for Android and several modifications were made to move it along. But this permission error is tough to figure out.

Unable To Build iOS App Using Native Extension

I’m trying to create a native extension for iOS and use that extension as part of an IPA app for iOS I create from a SWF file using the ADT tool (i.e. the normal use-case for iOS). Note: I have already successfully created the native extension and APK app for Android and now I am trying to build the iOS side.
I have been primarily using the information found at the following websites:
http://www.adobe.com/devnet/air/articles/building-ane-ios-android-pt3.html
http://www.adobe.com/devnet/air/articles/building-ane-ios-android-pt5.html
http://help.adobe.com/en_US/air/build/WS901d38e593cd1bac35eb7b4e12cddc5fbbb-8000.html
I have also searched the Adobe forums for the answer to my question without success.
The error I receive is:
ld: warning: ignoring file /var/folders/c3/mpg4frwn2j1f8scw4jctbmv9hfkswj/T/bd3fbd4a-cf56-4fd6-a06d-d69ea92dc620/lib com.mycompany.MyExtension.a, file was built for archive which is not the architecture being linked (armv7): /var/folders/c3/mpg4frwn2j1f8scw4jctbmv9hfkswj/T/bd3fbd4a-cf56-4fd6-a06d-d69ea92dc620/lib com.mycompany.MyExtension.a
Undefined symbols for architecture armv7:
"_MyExtensionInitializer", referenced from:
      _g_com_adobe_air_fre_fmap in aotInfo.o
"_MyExtensionFinalizer", referenced from:
      _g_com_adobe_air_fre_fmap in aotInfo.o
ld: symbol(s) not found for architecture armv7
Compilation failed while executing : ld64
I receive the above error when I execute the following command:
adt -package -target ipa-ad-hoc -storetype pkcs12 -keystore certificate.pfx -provisioning-profile provisioning_profile.mobileprovision MyApp.ipa MyApp.xml MyApp.swf -extdir packaged-extensions
where the folder “packaged-extensions” contains the ANE file I created using this command:
adt -package -target ane packaged-extensions/MyExtension.ane MyExtension.xml -swc MyExtension.swc -platform Android-ARM -platformoptions platformAndroidARM.xml -C dependencies . -C platform/Android . -platform iPhone-ARM -platformoptions platformiOSARM.xml -C platform/IOS . -platform default -C platform/default library.swf
where the content of the files are as follows:
MyApp.xml:
<application xmlns="http://ns.adobe.com/air/application/4.0">
    <id>MyApp</id>
    <versionNumber>0.0.1</versionNumber>
    <filename>MyApp</filename>
    <initialWindow>
        <content>MyApp.swf</content>
        <visible>true</visible>
        <width>600</width>
        <height>600</height>
    </initialWindow>
    <supportedProfiles>mobileDevice</supportedProfiles>
        <extensions>
                <extensionID>com.mycompany.MyExtension</extensionID>
        </extensions>
</application>
MyExtension.xml:
<extension xmlns="http://ns.adobe.com/air/extension/4.0">
        <id>com.mycompany.MyExtension</id>
        <versionNumber>0.0.1</versionNumber>
        <platforms>
                <platform name="Android-ARM">
                        <applicationDeployment>
                                <nativeLibrary>MyExtension.jar</nativeLibrary>
                                <initializer>com.mycompany.MyExtension</initializer>
                        </applicationDeployment>
                </platform>
                <platform name="iPhone-ARM">
                        <applicationDeployment>
                                <nativeLibrary>libMyExtensionIOSLibrary.a</nativeLibrary>
                                <initializer>MyExtensionInitializer</initializer>
                                <finalizer>MyExtensionFinalizer</finalizer>
                        </applicationDeployment>
                </platform>
                <platform name="default">
                        <applicationDeployment/>
                </platform>
        </platforms>
</extension>
platformiOSARM.xml:
<platform xmlns="http://ns.adobe.com/air/extension/4.0">
<linkerOptions>
    <option>-ios_version_min 5.1</option>
    <option>-liconv</option>
</linkerOptions>
</platform>
MyExtensionIOSLibrary.m (yes, I know it doesn't do anything - it's simple on purpose to help isolate the error):
#import "FlashRuntimeExtensions.h"
void MyContextInitializer(void* extData, const uint8_t *ctxType, FREContext ctx, uint32_t *numFunctionsToTest, const FRENamedFunction **functionsToSet) {
return;
void MyExtensionInitializer(void **extDataToSet, FREContextInitializer* ctxInitializerToSet, FREContextFinalizer* ctxFinalizerToSet) {
    *extDataToSet = NULL;
    *ctxInitializerToSet = &MyContextInitializer;
void MyExtensionFinalizer(void *extData)
    return;
I am using XCode to build MyExtensionIOSLibrary.m into a library file with a .a filename extension. My relevant build settings are:
iOS Deployment Target: iOS 5.1
Architectures: armv7
Build Active Architectures Only: No
Product Scheme: Release
Compile Sources As: Objective-C
Any ideas? Please help.

Thanks for the reply.
yes.I've created a static library with 3rd party frameworks and pulled the .a from product folder(Debug-iphoneos).
and the framework didn't work(armv7 not supported error occurs ..don't know why) with it's original folder structure .
so I followed below link to change folders inside the 3rd party framework and figured out but now the application crashes on startup without giving an error message. .
スタッフ日記 - 【ANE作成】外部フレームワークを含むANE作成時の注意点(iOS) | 株式会社マリエッタ

Using Image Magick within a Native Extension

Hi,
Does anyone know exactly how to incorporate Image Magick into a native extension, and then exactly how to include it and then invoke it in AS3?
My environment is Windows 7/64 bit with FlashBuilder 4.6.
Any advice will be most appreciated, and thanks in anticipation.

Hi, When I posted this question nearly 12 months ago, I did not properly understand how to build an ane incorporating anything.
But I did make some progress and the results can be seen at Air Native Extension - Adobe AIR: Visual QuickPro Guide - Larry Ullman's Book Forums
I hope that it may be of interest.
Regards.

Captive runtime distribution license.

I am planning to develop a mobile game app using Adobe Air and Captive runtime feature.
Do I need to apply for distribution agreement to Adobe for distributing the runtime?

No. At least, I never have.

Successfully using a Native Extension with Flash CS5.5 Pro, having issues

Hey all,
I'm trying to use a native extension due to an app rejection about the new storage guidelines. I'm hoping someone can help me figure out how to use a native extension from Flash CS5.5 and the adt command line utility (I've never used before).
Apples storage guidelines in 5.0.1 require files saved to Documents (and other places) to be marked with the icloud "do not back up" bit. I'm trying to use Adobe's IOS 5.0.1 data storage native extension to do that as I have file sharing enabled and my app downloads files I want the user to be able to copy to their desktop.
From the bits and fragments I'm reading all over, getting it to compile means using the command line adt tool (I've never used it before) because Flash Pro CS5.5 doesn't support native extensions. Also, this native extension requires a v14 SWF published (11.1) and CS5.5 only goes up to 10.2 (or higher if you install the players).
I edited the AiriPhone.xml file and pointed it to an AIR 3.1 airglobal.swc and I have AIR 3.1 overlayed in flash. I can't test AIR for iOS anymore after that change but I can get it to compile a SWF. The adt command line adt utility stopped complaining that my SWF version was 13 when it needed 14, so I assume this worked?
I am trying to compile a debug version so I can see trace statements to see if the native extension reports success on changing the bit. Here is my command line cobbled together from scraps of info on adobe.com and the -help data:
adt -package -target ipa-debug -connect 192.168.1.80 -provisioning-profile myApp.mobileprovision -storetype pkcs12 -keystore myApp.p12 myApp.ipa myApp-app.xml myApp.swf dat AppIconsForPublish Default-Landscape.png Default-LandscapeRight.png -extdir extensionDir
Before this iCloud change this app published directly from Flash Pro CS5.5 without any issues. I am only running into issues getting this app to work with this native extension and/or published correctly.
I am including the folders "dat" and "AppIconsForPublish" as well as splash screens (this app is landscape-only) as well as that extension in the folder extensionDir.
After putting in my password my app compiles into an IPA which I can drop into iTunes. It has the same general size as the IPA generated from Flash Pro. The icon is correct, etc.
When I sync this file, the progress bar goes across, I see it loading on my iPad and then once it goes to install I get a popup saying "iTunes Sync: 'myApp' failed to install."
Is there anything obvious wrong with my adt line? Has anyone else used this native extension? Ideas on what I can do to fix this?
No, unfortunately I did not build this with Flash Builder. I am an avid user of it now and this would be a moot point as it uses ANEs and changes SWF versions trivially. I have to get this to compile using Flash Pro CS5.5 though.
Any help is greatly appreciated!
edit:
Just FWIW, after I updated the .xml to use the latest AIR and such (so the version is 14) I removed the extension, exported purely from Flash Pro CS5.5 and the app works fine. As soon as I enable the <extension> in the XML I can no longer install the app. This just appears to be a noob adt publish issue.

My app downloads PDFs, movies and other information-esque files and saves them to the apps Documents folder so they can be retrieved via file sharing. These files not being in something purgable like /Library/Caches and not having the "do not back up" bit is why I was rejected.
update: It's definitely my command line building.. I took out the native extension completely and published from flash to an IPA and it works. I then run adt on the same SWF that just worked and it fails to install. So the install failing is my command line. I see this article and my command line is very similar. I'm really uncertain why it's failing.

Native extensions

I am trying to test out the native extensions and am having the biggest problems with every precompiled package i try. Wondering if I am doing anything wrong
I am simply trying to use the Vibration example that is provided by Adobe.
When i try to run in debug mode (with iPad simulator)
com.adobe.nativeExtensions::Vibration is not defined
Although i've added the Vibration AS library as a library path and added the ANE to the Native Extensions.
If i try to package to a device. Then i get Java errors
Exception in thread "main" java.lang.Error: Unable to find named traits: com.adobe.nativeExtensions::Vibration
          at adobe.abc.Domain.resolveTypeName(Domain.java:231)
          at adobe.abc.Domain.resolveTypeName(Domain.java:148)
          at adobe.abc.GlobalOptimizer.sccp_eval(GlobalOptimizer.java:6665)
          at adobe.abc.GlobalOptimizer.sccp_analyze(GlobalOptimizer.java:5909)
          at adobe.abc.GlobalOptimizer.sccp(GlobalOptimizer.java:4628)
          at adobe.abc.GlobalOptimizer.optimize(GlobalOptimizer.java:3514)
          at adobe.abc.GlobalOptimizer.optimize(GlobalOptimizer.java:2215)
          at adobe.abc.LLVMEmitter.optimizeABCs(LLVMEmitter.java:526)
          at adobe.abc.LLVMEmitter.generateBitcode(LLVMEmitter.java:336)
          at com.adobe.air.ipa.AOTCompiler.convertAbcToLlvmBitcodeImpl(AOTCompiler.java:472)
          at com.adobe.air.ipa.BitcodeGenerator.main(BitcodeGenerator.java:82)
Compilation failed while executing : ADT
Was the package provided by Adobe not meant to run on a Mac or iOS?
If i try repackaging with only iOS, same story, it cannot run in debug mode on my desktop. And the IPA simply keeps a blank screen.
I'm trying to set up a workflow that will make it easy for Obj C and AS3 programmers to work together. Has anyone achieved that yet?

Here's the getting started page, maybe one of the basic ones will help get you going?
http://www.adobe.com/devnet/air/native-extensions-for-air.html

Is it possible to build a captive runtime package with native extension?

Hi. Now I try to build a captive runtime package with one native extension file(ANE) for Windows.
I use Flash Builder 4.6 Premium and try to export release build.
But Flash Builder warns that captive runtime can not bundle ane file.
So I can not build package.
Official document seems that captive runtime supports native extensions.
Does anyone know about?

Hi. Now I try to build a captive runtime package with one native extension file(ANE) for Windows.
I use Flash Builder 4.6 Premium and try to export release build.
But Flash Builder warns that captive runtime can not bundle ane file.
So I can not build package.
Official document seems that captive runtime supports native extensions.
Does anyone know about?

AIR runtime and AIR applications built using Captive Runtime still need Admin Privilege to Install

I am working on a small project to install AIR application(native .exe & .dmg) with AIR runtime without needing the Administrator privilege so I used Captive runtime but the installation is still asking for admin privilege
I bundled AIR application with AIR runtime using Captive runtime from flash builder 4.6, then I packaged this into a .MSI using Advanced Installer. Now when I install it for a user without admin privilege it prompts me for Admin credentials.
Can you please tell me if
1. I need AIR distribution license to install AIR runtime without Admin privilege
2. Do I need a different installer
3. Am I missing any step here
Thank you

If you're installing to a location where Windows requires elevated privileges, like Program Files, you'll need to have admin privileges to continue. Are you using an AIR based native installer or have you taken the application with the captive runtime and rolled this up in your own installer?
Here's a section from the Installation and deployment options in Adobe AIR 3 article that might help:
Installation privileges
When designing an installer, one has the option to choose from approaches that may or may not require administrative privilege. For example, a drag-and-drop install on Mac OS X requires no special privilege; users can always copy the application into their own application folders, for which they have the necessary permissions. On the other hand, if registry keys must be written to the machine-specific portion of the registry on Windows, installation of that application will require administrative privilege to do so.
The two installer formats directly supported by AIR, AIR files and native installers, have always required administrative privilege. This was a design decision made in part to simplify the implementation of the AIR installers: If administrative privilege is assumed to be available, implementation is possible if the registry can be written to, and so on. It was also selected because, in many enterprises, this is the desired behavior: administrators can use the privilege requirement to gate software installation.
All the same, there are scenarios where supporting installation without requiring administrative privileges is desirable, or even necessary. This can now be achieved using custom installers; you simply need to author an installer that operates correctly with only standard user privilege. In practice this can be easy to achieve; a simple install-by-copy to a writable location (that is, in the user's own folder) will suffice. Should you author a more complex installer, you should keep in mind that the addition of certain operations during the install process will in turn reintroduce the requirement for administrative privileges.

Captive Runtime and SSL WebService

I am trying to get an Air Desktop application that uses WebServices and ANE to install correctly and am having issues with WebServices. When the application is running in the IDE and also deployed in a 'Native Installer' the webservices called work correctly without issue. Now when I try and package as a Captive Runtime the web services are failing with the following error (I am storing application errors in a SQLite db) "[FaultEvent fault=[RPC Fault faultString="HTTP request error" faultCode="Server.Error.Request" faultDetail="null"] messageId="F1B0689A-C225-C6E3-4F28-67FBE72C59E1" type="fault" bubbles=false cancelable=true eventPhase=2]'.
I have seen other discussion about this but they are dealing with moble application not Windows Desktop so I am asking again with reference to windows.

It is also not a version issue.
I tried installing the exact same version of Adobe AIR that would get bundled as captive runtime. It would work perfectly.
Then I even bundled a newer version of the AIR runtime (3.5.0.88 instead of 3.1.0.488) and still it didn't work.
In conclusion: The error only occurs when using HTTPS (SSL) in combination with captive runtime, regardless of the AIR runtime version.
Really hoping someone can solve this problem, because we would like to include the runtime to prevent our customers from installing the runtime and ensuring the correct runtime is used.

Native application (captive runtime) doesn't support GameInput?

I've built a project originally for Flash Player, then for AIR with the GameInput API. With the addition of GameInput support in FlashPlayer 11.8, I've switched back to FP. The game supports controller input through the GameInput API when built as SWF/AIR.
However, when I package it using the -adt command using -target bundle (resulting in a captive runtime native EXE), controller support is lost. A check on launch for GameInput.isSupported returns true as SWF/AIR, but false as EXE with no changes to the project/build.
Any idea if there's a way to get isSupported to register as true and keep my GameInput functionality in a native EXE?

Apologies fixed by moving it out of fx:application

How to use single ant build script to package the application with and without native extensions

Hi,
I am using iOS native extensions for Adobe air. For this I am listing the extensions in the application descriptor file. Since the package with native extensions are meant to run only on device, I want my build script to work without native extensions too to be able to run on simulator. Is this manadatory that I need two separate application descriptors/basically two build scripts to compile and package them? Please suggest and let me know if more explanation is needed.
Thanks,
Swathi.

Hi
This is a known issue addressed by CR205204
As you said, IBM actually does not have rt.jar in its JDK - they have moved contents of rt.jar into various jars.
IBM is not using org/apache/crimson/tree/ in their JDK at all.So the error shows up in the end of build even if it succeeds
You may need to add crimson.jar to wlwBuild classpath, since it is not part of IBMs JDK.
Note: the build will work even w/o crimson.jar giving a non build related IDE exception in the very end.
Thanks
Vimala

Native extensions and captive runtime

Similar Messages

Maybe you are looking for