I am using a flatpak version of my favorite game engine, godot. Using it, I need to be able to export to android. To do this, it needs adb.
I tried looking in /usr/bin, where the adb executable is located, but Godot couldn't see it because of the flatpak's sandboxing.
I tried runing the flatpack with the --filesystem option, but it didn't work.
Does anyone know how to get the flatpak to have access to the whole filesystem?
Thanks.
This is a know issue. Snap package has issues too. The best option is to use the official executable from the website. If want auto updates you can use Steam or Itch.io
Related
I recently decided to switch from W10 to GNU/Linux, and yes still a Linux noob.
So which is the most recommended way to install flutter on Linux?, a way which won't get me troubles in the future when I try to update flutter.
Right now I only now this three ways, which one is the best option? (you're free to tell me is there is another and better option)
Install Flutter using snapcraft (snapd)
Install Flutter manually with github repo or tar
Install Flutter using yay (Arch-based distros only)
I really don't know anything about flutter in GNU/Linux so, I'd appreciate any opinion and advice.
Thank you in advance.
The best and most stable for me was manually, but not from gitHub, by using tar.
SnapD caused errors, but using .tar has been fine for 5 months now. Updating easily and seamlessly.
As you may have seen, but follow the documentation here step by step will work fine.
https://flutter.dev/docs/get-started/install/linux
If you have trouble exporting the path, come back for further help.
Welcome to the club.
I'm looking for a way to interact with OneDrive through C++. I need to log in and download/upload the file from a known location.
I tried to install curl in VS 2019/2017 using vcpkg but could not, it does not inclide to the code.
Have a look into Microsoft's "azure-storage-cpp"-sample under:
https://azure.github.io/azure-storage-cpp/
All install and build instructions are described there.
Cheers
When I try to sign an EXE file under Linux with Wine, it requires some dll - mfc42.dll. Also tried install that dll with winetricks, but I cannot get it running.
Maybe you know a better way to sign a .EXE under Linux?
Another possible solution is the "OpenSSL-based signcode utility", see http://sourceforge.net/projects/osslsigncode/
I haven't tried it yet, but it sounds promising (much leaner than installing Mono anyway).
I have only found one profiling tool - http://code.google.com/p/android-ndk-profiler/. Wasn't able to get it working so far, so I wonder if there are other tools available.
I need to profile on a physical device, as my application doesn't even work on emulator.
It is not easy to make the Android-NDK profiler work. You need to follow the steps here thoroughly.
Here are some tips that led me to success:
Make sure your android.mk is correct and that you export the NDK_MODULE_PATH.
Use correctly the following functions
monstartup("your_lib.so");
moncleanup();
If the gmon.out is generated now you need to pull it from the device, but not to anywhere in your PC. For me it only works if I go to the application's folder (where jni, obj, res and other folders are) and I do:
console$ adb pull sdcard/gmon.out
Then run gprof. Try will all the versions in your NDK toolchains. For me only one worked, this one:
console$ ~/Libraries/android-ndk-r9/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86_64/bin/arm-linux-androideabi-gprof obj/local/armeabi-v7a/libxxxx.so > profile.txt
The Shiny profiler is platform independent, it runs anywhere and it does not have any dependencies besides a standard C++ compiler. In its more simple usage, all you need to do is add a macro at the beginning of all functions and methods (or at least those that you want to profile).
Intel VTune Amplifier. This profiler allows you to collect hotspots with stacks on Android devices without root or any OS modification.
Here is simple guide:
http://software.intel.com/en-us/articles/using-intel-vtune-amplifier-on-non-rooted-android-devices
In the NDK r13b there is a new tool called simpleperf
I have about a few problems with a new install of the Qt SDK. I probably only need advice, but specific answers are also welcome. Before I begin a mini-story, I am running RHEL5 on academic license under VirtualBox on OSX 10.6. Using Qt version 4.5.3. This is my situation...
1.) I couldn't compile because g++ wasn't found. I fixed this by creating a link: g++ -> g++34. This allowed me to compile but it generated more errors at link-time. I had installed the framework in my home directory unintentionally so I uninstalled/reinstalled the entire SDK to /usr/local/qt.
2.) At this point I could compile but the linker complained about a missing freetype package. I had that already installed but wasn't sure why it couldn't be found. So I installed a few packages that I thought might be missing like libqt4-devel and libqt4-devel-debug. I also installed a few other general programming packages for later use.
3.) Somehwere in this process I can no longer run qmake. I ran it before and I have it installed at /usr/local/qt/qt/bin/qmake. I could create a link to it (though I shouldn't have to OR I could ensure that the location was in the PATH var). However, at this point Qt Creator says there's no Qt installation found. I re-pointed it to the installation location (using Tools/Options) but it still won't run qmake or anything else for that matter...
I only need this linux install to compile and test my Qt projects which I am developing in OSX. So my question is, should I just wipe this RHEL install and start over? And if so, should I use something else like Ubuntu? I am having plenty of hassles that I don't want to deal with as is. Note, this project will require good OpenGL support.
Is there a particular reason that you don't simply use the Qt package that's part of RHEL?
If for some reason you need to build your own, you can get all of the build dependancies with:
$ yum install yum-utils
$ yum-builddep <whatever the qt package's name is>
#scotchi is right, and you should try to use the Qt package that comes with your system unless you need a very different version. I don't know what version of Qt comes with RHEL but if its not up-to-date enough for you (and it might not be, see below) then you could consider changing OS versions. I would only do this after trying his suggestion though, because you may be able to get things working without the hassle of a full OS install.
Now, as to why you might want to switch: RHEL is, as its name ("Enterprise Linux") indicates aimed at companies who want to run servers, or large deployments of desktops. It emphasizes stability and reliability over being cutting edge. Fairly often the version of the compiler and development libraries lag a little behind the curve. This is what their clients want: a stable platform they can develop against and run programs on for a period of time, not constantly needing to keep up with the latest changes, and thoroughly tested. But for people doing development at home it may not be necessary to stay that conservative. I don't know if this is for work, school or personal programming, but it sounds to me like you should move to one of the more desktop-oriented distros. Ubuntu is great, as is Fedora. If you prefer a RHEL-like environment, then choose Fedora.