-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plugin was not found. #18
Comments
The readme has not been updated in a while (It's something I need to do). However, the example in the examples folder is up to date and should work. |
I tried the example in example folder but the same error occurs. |
Are you using the newest copy of the example folder? The newest example folder is using version 1.0.0. Anything using an 0.x.x version is out of date and should be updated. I just did a fresh clone on a new system of the example folder and it built. |
I want to create a JPackage for windows , linux and mac. Will this plugin create native libs for all the os ? |
As long as you run the build on each platform it would. Cross OS builds are not supported by gradle's native setup, which handles most of the native building. This plugin is just a thin extension onto gradle's native toolset to configure it right for JNI. |
I have three devices with windows , linux and mac operating systems. If I build JPackage wtih this plugin on each os . Will this plugin create native libs for each os ? |
Yes, it would. |
Please , Give a sample project for this plugin. |
The example is the only sample I currently have that isn't dependent on our other internal plugins to handle more complicated building scenarios. |
If youre getting that error you must be using an old copy of the example. The current example uses 1.0.0 as the plugin version. So if its trying to load 0.1.6, youre trying to load an old version that won't work. |
I also tried the new version 0.1.6 . But , it not worked. |
The new version is not 0.1.6. The current version is 1.0.0. |
I tried both 0.1.6 and 1.0.0 . But , not worked. |
So whats the error you get with 1.0.0? |
It definitely won't be the same error. That error log is showing its trying to run 0.1.6, which will not work, and wouldn't be the error if 1.0.0 is used. If you clone this repo, go into the examples folder, and run |
Oh. I thought I had published 1.0.0, but apparently I hadn't. We're still a WIP upgrading to 1.0.0. As a workaround for now, go to the root directory and run |
How can I solve this ?
The text was updated successfully, but these errors were encountered: