How to run .AppImage on ubuntu 17.10?
I did cura-build from the following exec (AppRun and Appimagetool) files from https://github.com/AppImage/AppImageKit/releases
~cura-build/build$ make
Copying AppRun executable...
...
...
...
...
...
Embedding ELF...
Marking the AppImage as executable...
Success
Please consider submitting your AppImage to AppImageHub, the crowd-sourced
central directory of available AppImages, by opening a pull request
at https://github.com/AppImage/appimage.github.io
[ 98%] Built target packaging
Scanning dependencies of target signing
[100%] Signing Package...
Generating signature...
Generating SHA-1 sum...
[100%] Built target signing
After generated package I got an .Appimage file, then I try to run this file,
~: chmod a+x Cura-0.0.0-master.AppImage
~: ./Cura-0.0.0-master.AppImage
execv error: No such file or directory
I checked with these file properties as 'Allow executing file as program'
How to resolve this?
Please download a readymade AppImage from https://ultimaker.com/en/products/ultimaker-cura-software and report issues at https://github.com/Ultimaker/Cura/issues, thanks.
for RUN
in linux(ubuntu)
chmod +x Name.AppImage
./Name.AppImage
Related
I am trying to build an application that communicates with dds with opendds. I am using the opendds layer on krikstone. The bitbake image is built with the opendds libraries but when I build the sdk it seems the layer nativesdk is not installed. When I run the cmake I get the error "Missing required dependencies OPENDDS_IDL;ACE_GPERF;TAO_IDL".
from the opendds.inc I see there is the nativesdk install. I added a junk line and expected that when i build the opendds or build the populate-sdk I will fail but it seems that the nativesdk is not run.
build is for imx8mm variscite som with command bitbake fsl-image-qt5 -v populate_sdk_ext
layer with the problem is meta-opendds (krikstone branch) building version 3.22
the layer has a bb file that requires an opendds.inc file which has the nativesdk install
Blockquote
do_install:append:class-nativesdk() {
dfdf -- my junk line to trigger failure
ln -sf ${bindir}/opendds_idl ${D}${datadir}/dds/bin/opendds_idl
ln -sf ${bindir}/ace_gperf ${D}${datadir}/ace/bin/ace_gperf
ln -sf ${bindir}/tao_idl ${D}${datadir}/ace/bin/tao_idl
}
Blockquote
** i added a junk line to trigger failure but it doesnt fail with building the sdk or image itself
why is the nativesdk command not run and why is the sdk without the opendds_idl executable
thanks
I was able at last to build the nativesdk files. I had to build them specifically as they are not build by default. i had to "bitbake nativesdk-opendds" manually.
my mistake was to believe that the nativesdk will be defaulted. my assumption is that if i am using the opendds that most probable that i will build subscribers/produces applications and will need the opendds_idl executable.
!!!! after testing the nativesdk-opendds it did not solve the problem !!!
!! in general after adding building the opendds layer i cannot build the Messanger example for lack of the opendds_idl and other two (tao,ace) executable
I am using helm installer task in ado yaml pipeline. It has been working fine for more than a year now. All of a sudden today I am seeing below error.
##[error]Error: Unable to locate executable file: 'helm'. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
My yaml file:
- task: HelmInstaller#0
inputs:
helmVersion: ${{ parameters.helmVersion }}
installKubectl: true
checkLatestHelmVersion: false
Did anyone face this issue ?
Further logs from the task:
Downloading: https://api.github.com/repos/helm/helm/releases
(node:144) Warning: Use Cipheriv for counter mode of aes-256-ctr
Downloading: https://get.helm.sh/helm-v3.10.2-linux-amd64.zip
Extracting archive
/usr/bin/unzip /__w/_temp/helm-v3.10.2-f8239f1e-9c15-41c1-b7db-776e2cbaa057.zip
Archive: /__w/_temp/helm-v3.10.2-f8239f1e-9c15-41c1-b7db-776e2cbaa057.zip
creating: linux-amd64/
inflating: linux-amd64/helm
inflating: linux-amd64/LICENSE
inflating: linux-amd64/README.md
Caching tool: helm 3.10.2 x64
Prepending PATH environment variable with directory: /__t/helm/3.10.2/x64/linux-amd64
Verifying helm installation...
##[error]Error: Unable to locate executable file: 'helm'. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
Finishing: HelmInstaller
I've had the same problem. We are running our pipeline on our own agent, so was able to confirm that the helm files are downloaded correctly. The issue seems to be that the file is not set as executable.
I have raised an issue on MS developer community (https://developercommunity.visualstudio.com/t/Helm-tool-installer-recently-started-fai/10221504?space=21&sort=newest) and will update any feedback I receive.
As a workaround, I have found that using the HelmInstaller#1 (along with KubectlInstaller#0 where necessary) has allowed me to get my pipeline working again.
We've had the same issue today morning and we fixed using HelmInstaller#1 Preview and also we needed to add a new task for Kubectl Tool Installer.
With that our pipelines were fixed.
I am trying to build onnxruntime from source on Linux. According to this instruction I have successfully built python wheels and shared libs. But I have not seen headers for C API.
There is a build option --build_csharp which seems to enable C#/C packages. I tried to add this option but got following errors.
CMake Warning at CMakeLists.txt:137 (message):
Language Csharp is not found in the system
I installed dotnet-sdk-3.1 but still got this error. Can I ask how to properly generate onnxruntime C API on Linux? Thanks!
Please try the following steps:
- Steps to build ONNX from source code:
1. git clone --recursive https://github.com/Microsoft/onnxruntime
2. Get the commit ID of the version you want to build (In case you want older version)
3. git checkout "your commitID"
4. Install the required version of Cmake on your system
6. Run: <path>\build.sh --config Release --build_shared_lib --parallel
7. A build folder will be created in the onnxruntime.
5. Get the onnxruntime.dll from the dir: \onnxruntime\build\Windows\Release\Release
6. Get the required headers (onnxruntime_c_api.h, onnxruntime_cxx_api.h, onnxruntime_cxx_inline.h)
from the dir: \onnxruntime\include\onnxruntime\core\session and put it in the unit location.
I have been trying to write some instrumental test case of android code using UiAutomator tool. This test cases can be run via android studio without any problem. But now i want to install this test cases into device as a jar file and need to run via command line. I had tried the following link for building and deploying uiautomator tests:
https://stuff.mit.edu/afs/sipb/project/android/docs/tools/testing/testing_ui.html#creating
build.xml is generated but when command "ant build" is executed it shows error:
Android/Sdk/tools/ant/uibuild.xml:198: null returned: 1
After that i have tried to create jar files using gradle build instead of ant build tool using this link
http://wiliamsouza.github.io/#/2013/10/30/android-uiautomator-gradle-build-system
I have run the "gradle build" command from the project directory and output got;
Building dex...
:compileJava UP-TO-DATE
:processResources UP-TO-DATE
:classes UP-TO-DATE
:jar
:assemble
:compileTestJava UP-TO-DATE
:processTestResources UP-TO-DATE
:testClasses UP-TO-DATE
:test
:check
:build
BUILD SUCCESSFUL
Total time: 7.709 secs
but there was no jar file found in "dist" folder. In have installed jar file found in build/libs folder,
adb push sample-0.1.jar /data/local/tmp/
then tried to run the test cases using the command
adb shell uiautomator runtest sample-0.1.jar -c com.test.uiautomator.sample.Sample
But it shows error as:
INSTRUMENTATION_RESULT: shortMsg=java.lang.RuntimeException
INSTRUMENTATION_RESULT: longMsg=Didn't find
class"com.test.uiautomator.sample.Sample"
on path: DexPathList[[zip
file"/system/framework/android.test.runner.jar",
zip file"/system/framework/uiautomator.jar",
zip file"/data/local/tmp/sample-0.1.jar"],
nativeLibraryDirectories=[/vendor/lib, /system/lib]]
INSTRUMENTATION_CODE: 0
Is anyone have any idea on this.. how can i create jar files of my uiautomator test cases and how can i run them via command line..?
Got a Solution !!!
Actually my requirement was to run instrumental test cases (UiAutomator in my case)through command line, for this purpose it is not necessary to generate a jar file of the test classes and install them to devices, instead we can create separate apk file of test case package and install them in the same way as application apk file is installed. And then run adb commands for executing the test cases. Please check the below link which has the detailed explanation.
https://developer.android.com/studio/test/command-line.html#RunTestsCommand
When I try to compile TOSSIM in tiny OS v-2.0.2 , this is the error that it is giving me:
# make micaz sim
Makefile:2: /opt/tinyos-2.1.0/support/make/Makerules: No such file or directory
make: *** No rule to make target `/opt/tinyos-2.1.0/support/make/Makerules'. Stop.
How to remove this error?
Did you run a ./configure ? This is usually the config script used by make files, but sometimes people use strange build systems so I'd look around in the project's root directory for something else relating to configuring or installing. There should also be a text file called 'INSTALL' which helps.
The usual build commands are:
./configure
make
make install clean