Packages are installed to %appdata%\McNeel\Rhinoceros\packages. You’ll likely need to edit this file afterwards to give the package a more general name and description. Rename it to rh6_0, otherwise it won’t show up in the Package Manager for Rhino 6.Īlso note that the spec command will use the first GHA that it finds when generating a manifest.yml file. If you’re referencing RhinoCommon/Grasshopper v5 in the Rhino 6 version of your plug-in then you’ll get a package with rh5_* in the file name. It should just work if you’re referencing v6 and v7 RhinoCommon/Grasshopper respectively in the Rhino 6 and Rhino 7 versions of your plug-in. To build a platform-specfic package, run the build command again with the -platform argument, where can be either win or mac. The second part, any, refers to the platform that the plug-in is intended for. OS X 10.11.6 (El Capitan) or better is required for Grasshopper for Mac beta OS X 10.10.5 (Yosemite) OS X 10.9.5. Rhino runs on ordinary Windows and Mac desktop and laptop computers with: Rhino 5 for Windows Hardware. The first part, rh6_18, is inferred from the version of Grasshopper.dll or Rhinocommon.dll that is referenced in the plug-in project. buy download gallery features news community learn support resources my account sign in.
The filename includes a “distribution tag” (in this case rh6_18-any ).
That’s also the version that has all the new stuff to generate correctly named package files based on the version of RhinoCommon/Grasshopper used in your GHAs. Make sure you’re using the version of the yak CLI tool that’s included with Rhino 7. Yep, this was more a limitation of the packaging process and has now been removed.
0 kommentar(er)
