Closed robertlevy closed 8 years ago
Did you have the Assets/HoloToolkit folder selected when you went to export the package? If so, that'll miss the required compiler options files that are in the Assets folder. If you select Assets and do a package export that should catch them.
If that doesn't work for you, please let me know.
cool that did the trick. please consider if this warrants a clarification in the gettingstarted.md
This wasn't the first time, so I think we'll use this chance to update the docs. Thanks!
I also noticed this behavior when using Unity re-import functionality to resolve my project's state after a Untiy crash.
Getting a bunch of errors with the message in the title when importing this package into a new project.
My steps (which I think matches what the docs suggest):
The import completes but the HoloToolkit menu does not appear. Instead, I see 7 messages in the error list like: "Assets/HoloToolkit/Sharing/Scripts/SDK/AnchorDownloadRequest.cs(58,22): error CS0227: Unsafe code requires the `unsafe' command line option to be specified". All 7 messages have the same error, just different files.