-
Notifications
You must be signed in to change notification settings - Fork 9
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
Cannot run starter extension on macOS #6
Comments
What's your OS? |
I think I configured the paths correctly and I’m running high Sierra.
…On Thu, Jun 21, 2018 at 7:18 AM Samuel Mehrbrodt ***@***.***> wrote:
What's your OS?
Did you configure the LibreOffice & SDK paths correctly as described in
the readme?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#6 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AfikqNUJoH_NfcQHd-dpG7GNoRDh6fA4ks5t-4EVgaJpZM4UuYeF>
.
|
Ah yeah there are some restrictions on macOS making the LOEclipse extension unusable on macOS, see also LibreOffice/loeclipse#54 for reference. |
smehrbrodt
changed the title
Cannot run starter extension
Cannot run starter extension on macOS
Jun 21, 2018
Ok thanks
…On Thu, Jun 21, 2018 at 8:47 AM Samuel Mehrbrodt ***@***.***> wrote:
Ah yeah there are some restrictions on macOS making the LOEclipse
extension unusable on macOS, see also LibreOffice/loeclipse#54
<LibreOffice/loeclipse#54> for reference.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#6 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AfikqCwQdjRlJCrtOIwaL-gvk1l01CRZks5t-5XOgaJpZM4UuYeF>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thank you for providing this example. I followed the steps given, but whenever I run I get the following error:
sh: soffice.bin: command not found
However, I can run soffice directly from terminal.
How can I fix this error?
The text was updated successfully, but these errors were encountered: