Yes it is possible to have code that runs on MacOS ported to Raspberry Pi.
Protecting the source code is more of a challenge.
When you build an executable with Pyinstaller, Python, your .pyc files, and the other code required to run your app are bundled together. The .pyc files are not the source code so they may be effective in keeping honest people honest, but there are a number of tools for “decompliling” pyc files back to .py files.
You could also create some additional friction for someone trying to copy your code by obfuscating your code. This would jumble the variables names making the code more difficult to understand and maintain. See: pyminifier, http://liftoff.github.io/pyminifier/obfuscate.html
What are your objectives for protecting the source code? Who are you protecting the source code from?
There might be other approaches that could work.
--
You received this message because you are subscribed to the Google Groups "Kivy users support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kivy-users+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kivy-users/b6cfd2a5-8dfb-4e0d-a475-649fe5bcd0d8n%40googlegroups.com.
On Jan 5, 2023, at 5:18 PM, Elliot Garbus <elli...@cox.net> wrote:
You received this message because you are subscribed to a topic in the Google Groups "Kivy users support" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/kivy-users/1Hr9WtZ1GYc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to kivy-users+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kivy-users/63b74c9b.170a0220.b4641.40f8SMTPIN_ADDED_MISSING%40gmr-mx.google.com.
This is a python problem. If you fix it for python you have solved it for kivy.
But more specifically – what is the threat? If you don’t want anyone to see your source code, obfuscating it is probably a sufficient barrier.
This will not prevent anyone from taking and running your code – but they will have a difficulty understanding it.
If you need to keep the code confidential, create a web app and run the code remotely. If you have a local app you can only keep honest people honest.
You could consider a software license that restricts the use of the app, this gives you a path to sue the user if they have take an unauthorize action.
You could require the user to sign in to use the app.
Any solution, in any language, can be cracked depending on the level of enthusiasm and skill of the hacker.
Can you be more specific about what you are creating, and the threat?
To view this discussion on the web visit https://groups.google.com/d/msgid/kivy-users/0E079350-59E8-4B2F-A52B-5AB4ABBC4D1D%40gmail.com.