Chris Yate
Chris Yate
@franzeal I don't follow completely: where do you put this code? ``` var input = $(el.find('input')).datetimepicker(scope.to.dateTimePickerOptions); scope.datetimepicker = input.data("DateTimePicker"); ``` Is that in a script block within your page html?
Same problem here. Is this package being maintained?
(The 2024-01-09 build also fails)
The top of the log: That plugin is found (and it's executable). ```DEBUG: Probing plugin /home/username/.vs/project/build-linux-ninja-clang-release-installer/Release/InstallerOutput/linuxdeploy-plugin-gstreamer.sh DEBUG: subprocess /home/username/.vs/project/build-linux-ninja-clang-release-installer/Release/InstallerOutput/linuxdeploy-plugin-gstreamer.sh --plugin-type failed with exit code 1 DEBUG: stdout: Invalid argument: --plugin-type...
Update: I've stripped this right back to a very minimal test with a completely empty target folder. This doesn't work, but indicates there may be something about my deployment staging...
Here's a zipped example - a Hello World app, a 256x256 white icon, and script to create the appdir (which I've also included). Run the test.sh: this expects the linuxdeploy...
Hi @TheAssassin , Sorry to nag, but please could you confirm whether this looks like a bug, or user error on my end?
Ooops. It's user error in my example. sorry! But I have sent a PR https://github.com/linuxdeploy/linuxdeploy/pull/316 since that's an issue here.
@memsharded I'm hijacking this thread, I hope it's relevant. I would like to set, or override the `extension_properties` value `compatibility_cppstd` to false for specific external recipes that we use. In...