Make sure to use 0.6.13.3 which is freshly released, due to many fixes / but always try develop branch before reporting, actual bug reports to Github only, Commercial people go here: https://nuitka.net/pages/commercial.html
Just figured people might of experienced never ending prints of y
What kind of terminal is that, it looks funny with letters on the left side of the frame.
Yeah, you would have to delete the AppData of Nuitka, in
~.cache/ in the WSL.
The
tqdm guys hate a few terminals, maybe it's messed up. Nuitka doesn't echo your response.
# Compilation mode, support OS specific. Note that macOS is going to gain onefile mode "soon".
# nuitka-project-if: {OS} in ("Windows", "Linux"):
# nuitka-project: --onefile
# nuitka-project-if: {OS} not in ("Windows", "Linux"):
# nuitka-project: --standalone
# nuitka-project-if: {OS} == "Windows":
# nuitka-project: --windows-onefile-tempdir
# The PySide2 plugin covers qt-plugins
# nuitka-project: --enable-plugin=pyside2
# The pkg-resources plugin is not yet automatic
# nuitka-project: --enable-plugin=pkg-resources
# Protect the constants from being readable.
# nuitka-project: --enable-plugin=data-hiding
# Include datafiles for Qt into the binary directory.
# nuitka-project: --enable-plugin=datafile-inclusion
# nuitka-project: --qt-datadir={MAIN_DIRECTORY}
# nuitka-project: --qt-datafile-pattern=*.js
# nuitka-project: --qt-datafile-pattern=*.qml
You don't read the output of Nuitka, or you wouldn't have half of the options you are using.
oh lordy lol. well we would love to use nuitka for all of our apps and pay for the pro features once we get it all set up. We have some licensing systems built in to the apps and it would be nice to have the encryption features. any step making it harder to decompile is a plus
I was working on a solve my deployment customer, and didn't quite feel like writing that kind of code. What I wonder @DurkTheBurk_gitlab is why you don't use
--include-datafile for the onefile inclusion. It's not as good as the datafile-inclusion plugin, but at least it's in the onefile binary.
trying to find it in the docs
ok, it's named
--include-data-file :)
Check help output, copying a whole dir is not well supported yet, but I kind of want to do that for next release.
I am thinking of
--include-package-data as more convinient, as it finds the package locations itself.
ive got the build working on ubuntu it didnt have any problems. ill try debugging wsl when i get some more time
yeah, only cosmetic stuff... but I still like these things to be right.
it's better than pyinstaller
And for commercial, I want to add high grade protection of data files, not just including data file in a onefile archive that can be unpacked by anybody and changed :) but rather include them in the binary as constant data, like it will be with 0.6.14 now.
On factory the new project options are available, but not yet documented, refer to my example above if you want to use it.
This is highly experimental and may not even run in current form after I made cleanups.
