DOCSLIB.ORG

Minecraft Bedrock Launcher Documentation

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Minecraft Bedrock Launcher Documentation MrARM & contributors Jul 27, 2021 Contents: 1 Getting started 1 1.1 AppImage................................................1 1.2 Flatpak..................................................1 1.3 macOS..................................................2 1.4 Source build...............................................2 1.5 Getting help...............................................2 2 Frequently Asked Questions 3 2.1 Do I need to own Minecraft: Pocket Edition to play?..........................3 2.2 Does it work on Windows 7 / 8?.....................................3 2.3 How does it work?............................................4 2.4 Where are my worlds?..........................................4 2.5 Can I use resource packs?........................................4 2.6 Why would I want to use this projects server, instead of the official one?................4 3 Troubleshooting 5 3.1 Extracting APKs.............................................6 3.2 AppImage................................................6 3.3 Controller.................................................6 3.4 Game launcher..............................................7 3.5 Qt launcher UI..............................................9 4 Building from sources 11 4.1 Introduction (read first).......................................... 11 4.2 Compiling MSA (for Xbox Live).................................... 12 4.3 Compiling the game launcher...................................... 13 4.4 Compiling the Qt UI........................................... 14 4.5 Compiling the server launcher (Outdated as of 2021-07-27)...................... 15 5 Extract utility 17 5.1 Usage................................................... 17 5.2 Build instructions............................................. 17 6 Dedicated server 19 6.1 Server Properties............................................. 19 7 About 21 i ii CHAPTER 1 Getting started This launcher has been rewritten in 2020 to use mainly a fake Java Native Interface to communicate with Minecraft: Bedrock Edition. Additionally shortly after the release of the first 64bit versions on the Google Play Store, this previously 32bit only Launcher has been ported to arm64 and x86_64. 1.1 AppImage Prebuilt AppImage binary’s for linux x86_64, x86, armv7 hardfloat and armv8 are currently available here. Af- ter downloading simply open terminal, chmod +x Minecraft_Bedrock_Launcher-x86_64.0.0.661. AppImage and run it. With some Filemanagers you should be able to run it with double click, similar to running a *.exe file on Windows. Otherwise run it from a Terminal ./Minecraft_Bedrock_Launcher-x86_64.0. 0.661.AppImage If it’s your first time you have installed an AppImage and you want an Icon in your startmenu • install AppImageLauncher • run the AppImage like before • AppImageLauncher will ask you to integrate it, press yes • You can now start and update the Launcher directly from your startmenu 1.2 Flatpak You can also install mcpelauncher on Linux via Flathub. To install it, first setup Flatpak then run sudo flatpak install flathub io.mrarm.mcpelauncher If it’s your first time you have installed a Flatpak please logout from your Computer and sign back in to be able to find the Launcher inside your startmenu. To run it, run 1 Minecraft Bedrock Launcher Documentation flatpak run io.mrarm.mcpelauncher 1.3 macOS Prebuilt macOS binary’s are currently available here. Always copy the App to a writeable location otherwise the updater won’t work. If you want to compile from sources on macOS go here (Outdated as of 2021-07-27). 1.4 Source build If there are no packages available for your distribution, check out the Source build guide. You can also use the Linux build script (Outdated as of 2021-07-27). 1.5 Getting help We have a Discord chatroom, which you can join using the following link: https://discord.gg/TaUNBXr 2 Chapter 1. Getting started CHAPTER 2 Frequently Asked Questions 2.1 Do I need to own Minecraft: Pocket Edition to play? Yes. To download and update a compatible versions of the Game, the Google Play account you sign in with needs to own the game on the Play Store. Then you are able to download and play some previous versions of the game as well, althought not offically supported by Google Play. 2.1.1 The launcher cannot download the game from: • The Amazon App store, althought may or may not work on arm devices. You have to extract the apk from an amazon device. 2.1.2 The launcher cannot download and cannot launch the game from: This would require a completly different Launcher, if that would even possible • The Apple iOS App store • The Microsoft Store, previously by redeeming a gift code for Minecraft: Windows 10 Edition 2.2 Does it work on Windows 7 / 8? No, due to the amount of work required to get this running on Windows. Play the Windows 10 Edition instead if you can. Note that you can not play Minecraft in the current version of Windows Subsystem for Linux (WSL), as the mouse input is broken due to an issue with its graphic stack. 3 Minecraft Bedrock Launcher Documentation 2.3 How does it work? The project runs the native libraries from the Android version directly on your computer. This is accomplished by fixing the incompatibilities between the libc used on Android and the one used on desktop Linux or OS X (Android - Bionic; Linux - glibc). This is a simple compatibility layer which doesn’t impact performance in any significant way; it’s similar to Wine, but much more lightweight and simple. Aditionally, all Android-specific code has been rewritten to run on Linux (AppPlatform, Store, Xbox Live, etc.). 2.4 Where are my worlds? Linux: ~/.local/share/mcpelauncher/games/com.mojang/minecraftWorlds Linux (Flatpak): ~/.var/app/io.mrarm.mcpelauncher/data/mcpelauncher/games/com. mojang/minecraftWorlds Mac OS X: ~/Library/Application Support/mcpelauncher/games/com.mojang/ minecraftWorlds Each world has its own directory. If you have multiple worlds, you can identify them by their name in levelname. txt found in each world. The mcpelauncher-server creates and expects its world files in world. 2.5 Can I use resource packs? Yes, put them in ~/.local/share/mcpelauncher/games/com.mojang/resource_packs. (For Flatpak) ~/.var/app/io.mrarm.mcpelauncher/data/mcpelauncher/games/com.mojang/ resource_packs For Mac OS X, put them in ~/Library/Application Support/mcpelauncher/games/com.mojang/ resource_packs. Shaders are also resource packs. (Shaders must be GLSL based and must be compatible with your graphics drivers) Note: You will probably need to extract .zip and .mcpack files into their own subdirectory for them to work properly. 2.6 Why would I want to use this projects server, instead of the offi- cial one? If. • the official one doesn’t work for you • you need scripting on the server • some rarely needed particular modding capabilities 4 Chapter 2. Frequently Asked Questions CHAPTER 3 Troubleshooting • Extracting APKs – I downloaded a Minecraft APK from the internet and it doesnt work! – I copied the Minecraft APK from my phone over to my computer, but it doesnt extract – Can somebody give me the APK / extracted files? • AppImage – AppImage crashes when I try to sign in to Google • Controller – The player’s view drifts by itself when a controller is plugged in – The controller doesn’t work at all • Game launcher – Graphics performance issues (software rendering) - EGLUT: failed to initialize EGL display... – MSA daemon could not be found – No audio / music – Updating the launcher – MacOS X Catalina – Google prevents login This browser or app may not be secure. Try using a different browser – File picking doesn’t work or crashes – I compiled and/or installed everything, but Minecraft doesn’t start 5 Minecraft Bedrock Launcher Documentation – I used the Qt UI (metalauncher) to download the game, but mcpelauncher-client still doesn’t work – I run into lagspikes during gameplay • Qt launcher UI – Running the troubleshooter – Could not find the game launcher – The launcher crashes when I press Download and Play – Clearing the launcher UI data – Obtaining the game log 3.1 Extracting APKs 3.1.1 I downloaded a Minecraft APK from the internet and it doesnt work! APKs acquired from anything other than the Google Play store is unsupported by us. It might be possible, but we will not help you. 3.1.2 I copied the Minecraft APK from my phone over to my computer, but it doesnt extract Your APK is made for the ARM architecture. You need an x86 (32-bit) or x86_64 (64-bit) APK to play on your computer. If you have an ARM laptop (most chromebooks, pinebook) it should work. 3.1.3 Can somebody give me the APK / extracted files? NO. That is Piracy and we DO NOT support it on this project. Anyone caught asking this in the support server will face consequences. 3.2 AppImage 3.2.1 AppImage crashes when I try to sign in to Google The current workaround is to use LD_PRELOAD for nss3, eg. LD_PRELOAD=/usr/lib/libnss3.so ./ Minecraft_Bedrock_Launcher.AppImage Make sure you the libnss3 package installed. 3.3 Controller 3.3.1 The player’s view drifts by itself when a controller is plugged in This happens when the controller’s Deadzones are not set properly for the game. You must manually set the deadzones for your controller. 6 Chapter 3. Troubleshooting Minecraft Bedrock Launcher Documentation • Linux: https://wiki.archlinux.org/index.php/Gamepad#evdev_API_deadzones or if you have an Xbox360 Con- troller, open a terminal and run sudo xboxdrv --detach-kernel-driver --deadzone 6000 --silent --type xbox360 --mimic-xpad while you are ingame. • Mac OS X: TBA 3.3.2 The controller doesn’t work at all Under Linux, you may have to plug the controller after launching the game. 3.4 Game launcher 3.4.1 Graphics performance issues (software rendering) - EGLUT: failed to initialize EGL display... If the game is running poorly, it might be using software rendering (identified by the llvmpipe string in the renderer). If you have been redirected here by a link in the launcher this is the case. You should make sure to install the proper 32-bit graphic drivers for your hardware. • For integrated graphics and most AMD GPUs (and maybe Nvidia on nouveau) - sudo apt-get install libegl1-mesa:i386 libegl1-mesa-drivers:i386 • For some Nvidia cards (eg.
Recommended publications
  • Cryptomator Documentation Release 1.5.0

    Cryptomator Documentation Release 1.5.0

    Cryptomator Documentation Release 1.5.0 Cryptobot Sep 15, 2021 Desktop 1 Setup 3 1.1 Windows...............................................3 1.2 macOS................................................3 1.3 Linux.................................................3 2 Getting Started 5 3 Adding Vaults 7 3.1 Create a New Vault..........................................8 3.2 Open an Existing Vault........................................ 13 4 Accessing Vaults 15 4.1 Unlocking a Vault.......................................... 16 4.2 Working with the Unlocked Vault.................................. 17 4.3 Locking a vault............................................ 18 5 Password And Recovery Key 21 5.1 Change Password........................................... 21 5.2 Show Recovery Key......................................... 22 5.3 Reset Password............................................ 23 6 Vault Mounting 27 6.1 General Adapter Selection...................................... 27 6.2 Options applicable to all Systems and Adapters........................... 27 6.3 WebDAV-specific options...................................... 28 6.4 Dokany-specific options....................................... 28 6.5 FUSE-specific options........................................ 28 7 Vault Management 29 7.1 Remove Vaults............................................ 29 7.2 Reorder Vaults............................................ 29 7.3 Vault Options............................................. 29 8 Setup 33 8.1 Google PlayStore..........................................
  • PDF-Dokumenten Zusammenzusetzen Im Test Raspi 3A+

    PDF-Dokumenten Zusammenzusetzen Im Test Raspi 3A+

    Haiku: BeOS-Klon bekommt RasPi 3 Modell A+: Neuer easyLINUX COMMUNITY-EDITIONJetzt mit zusätzlichen Seiten ! rund umneues den Paketmanagement Linux-Einstieg S. 82 Mini-PC im Überblick S. 86 Frei kopieren und beliebig weiter verteilen ! 02.2019 02.2019 Digitale Notizen, Gliederungseditoren, Zusammenarbeit im LAN und unterwegs WISSEN TEILEN WISSEN TEILEN WISSEN Mini-Server: Vorträge um ein Diskussionsforum ergänzen S. 28 Joplin: Evernote-Ersatz ohne Zwang zur Cloud S. 32 Pydio Cells: Dateien teilen und gemeinsam bearbeiten S. 24 Cherrytree und Piggydb: Daten ordnen und miteinander vernetzen S. 16 Steam Play: Der neue Valve-Client im Test Dank Vulkan-API und Proton verspricht das Unternehmen mehr Spiele für Linux – unser Report deckt das Potenzial und die Probleme des neuen Ansatzes auf S. 74 Hilfe aus der Ferne Netzwerk-Konfiguration Einsteigertaugliche Remote-Software Mit nur einem Tool Geräte einrichten, öffnet SSH-Zugang zum eigenen PC S.38 Routen setzen und Traffic steuern S. 80 Top-Distris auf zwei Heft-DVDs MANJARO 18 • APT-CLONE • PLASMA 5.14 • GIMP 2.10 • RASPI 3A+ • • 3A+ RASPI • 2.10 GIMP • 5.14 PLASMA • APT-CLONE • 18 MANJARO EUR 8,50 EUR 9,35 sfr 17,00 EUR 10,85 EUR 11,05 EUR 11,05 02 www.linux-user.de Deutschland Österreich Schweiz Benelux Spanien Italien 4 196067 008502 02 Editorial Lindows? Sehr geehrte Leserinnen und Leser, wer sich gelegentlich auch in englisch- sprachigen Medien über Linux und quell- offene Software informiert, der kennt unvermeidlich das Kürzel sjvn: Steven J. Vaughan-Nichols liefert seit Jahrzehnten technische Hintergrund informationen und spitzzüngige Meinungsstücke über Jörg Luther das Open-Source- Umfeld.
  • Linux Sound Subsystem Documentation Release 4.13.0-Rc4+

    Linux Sound Subsystem Documentation Release 4.13.0-Rc4+

    Linux Sound Subsystem Documentation Release 4.13.0-rc4+ The kernel development community Sep 05, 2017 CONTENTS 1 ALSA Kernel API Documentation 1 1.1 The ALSA Driver API ............................................ 1 1.2 Writing an ALSA Driver ........................................... 89 2 Designs and Implementations 145 2.1 Standard ALSA Control Names ...................................... 145 2.2 ALSA PCM channel-mapping API ..................................... 147 2.3 ALSA Compress-Offload API ........................................ 149 2.4 ALSA PCM Timestamping ......................................... 152 2.5 ALSA Jack Controls ............................................. 155 2.6 Tracepoints in ALSA ............................................ 156 2.7 Proc Files of ALSA Drivers ......................................... 158 2.8 Notes on Power-Saving Mode ....................................... 161 2.9 Notes on Kernel OSS-Emulation ..................................... 161 2.10 OSS Sequencer Emulation on ALSA ................................... 165 3 ALSA SoC Layer 171 3.1 ALSA SoC Layer Overview ......................................... 171 3.2 ASoC Codec Class Driver ......................................... 172 3.3 ASoC Digital Audio Interface (DAI) .................................... 174 3.4 Dynamic Audio Power Management for Portable Devices ...................... 175 3.5 ASoC Platform Driver ............................................ 180 3.6 ASoC Machine Driver ............................................ 181 3.7 Audio Pops
  • Linux Apps That Run Anywhere

    Linux Apps That Run Anywhere

    7/22/2018 AppImage | Linux apps that run anywhere Linux apps that run anywhere (h "As a user, I want to download an application from the original author, and run it on my Linux desktop system just like I would do with a Windows or Mac application." (m "As an application author, I want to provide packages for Linux desktop systems, without the (h need to get it 'into' a distribution and without having to build for gazillions of different distributions." (h (h (h LEADING LINUX DISTRIBUTIONS Download an application, make it executable, and run! No need to install. No system libraries or system preferences are altered. Can also run in a sandbox like Firejail (https://github.com/netblue30/firejail) https://appimage.org/ 1/10 7/22/2018 AppImage | Linux apps that run anywhere (h (m (h (h Distribute your desktop Linux application in the AppImage format and win users running all common Linux distributions. Package once and run everywhere. Reach users on all major desktop distributions. (h (h WHAT PEOPLE THINK https://appimage.org/ 2/10 7/22/2018 AppImage | Linux apps that run anywhere (h Dirk Hohndel (m "The AppImage approach is really really useful." Picture: Copyright Faces of Open Source / Peter Adams. Licensed under CC-BY-NC-SA 4.0. Original picture (h (http://facesofopensource.com/dirk-hohndel/) (h (h (h https://appimage.org/ 3/10 7/22/2018 AppImage | Linux apps that run anywhere (h (m (h Drawing: [email protected] Larry Ewing and The GIMP. (h SEE IT IN ACTION (h Here is an application packaged as an AppImage for you to try.
  • The GNOME Census: Who Writes GNOME?

    The GNOME Census: Who Writes GNOME?

    The GNOME Census: Who writes GNOME? Dave Neary & Vanessa David, Neary Consulting © Neary Consulting 2010: Some rights reserved Table of Contents Introduction.........................................................................................3 What is GNOME?.............................................................................3 Project governance...........................................................................3 Why survey GNOME?.......................................................................4 Scope and methodology...................................................................5 Tools and Observations on Data Quality..........................................7 Results and analysis...........................................................................10 GNOME Project size.......................................................................10 The Long Tail..................................................................................11 Effects of commercialisation..........................................................14 Who does the work?.......................................................................15 Who maintains GNOME?................................................................17 Conclusions........................................................................................22 References.........................................................................................24 Appendix 1: Modules included in survey...........................................25 2 Introduction What
  • Features Ask Klaus!

    Features Ask Klaus!

    FEATURES Ask Klaus! Klaus Knopper answers your Linux questions Thanks for reading this, Klaus; it really means a lot to me that you take time to help out the Linux community. Mark Mina If I’m not completely mistaken (having no such model for test- ing), the main challenge with this note- AskBy Klaus Knopper Klaus! book really seems to be the graphics Knoppix Install adapter, which is a hybrid Intel + ATI/ Hello, Klaus. I have been using your AMD RadeonHD 6550M. You will most OS version 6.4 as supplied on the likely need a new kernel (at least 2.6.38 DVD with the January 2011 Linux Maga- or 2.6.39) with the Radeon DRM module zine. I like it so much that I would like to and Xorg 1.10 with the xorg-video- install it on the hard drive on one of my radeon driver, which is currently in De- machines. I have looked through the bian/ unstable. This is quite distro-inde- files but cannot find a way to install it. pendent; the most recently released ones Can you please advise? I am not on the will be the best candidates. Internet but hope to be on in the next You may also succeed by switching off couple of months. Best Regards, John one of the graphics chipsets in the BIOS Stirling and explicitly configuring the other in Xorg. The Intel version may be a good A Knoppix harddisk install option candidate. For Knoppix, try to boot with: exists in the Preferences menu with the “0wn” (“zero work needed”) knoppix xmodule=intel utility.
  • Pipewire: a Low-Level Multimedia Subsystem

    Pipewire: a Low-Level Multimedia Subsystem

    Proceedings of the 18th Linux Audio Conference (LAC-20), SCRIME, Université de Bordeaux, France, November 25–27, 2020 PIPEWIRE: A LOW-LEVEL MULTIMEDIA SUBSYSTEM Wim Taymans ∗ Principal Software Engineer Red Hat, Spain [email protected] ABSTRACT 2. LINUX AUDIO LANDSCAPE PipeWire is a low-level multimedia library and daemon that facili- Audio support on Linux first appeared with the Open Sound System tates negotiation and low-latency transport of multimedia content be- (OSS) [6] and was until the 2.4 kernel the only audio API available tween applications, filters and devices. It is built using modern Linux on Linux. It was based around the standard Unix open/close/read- infrastructure and has both performance and security as its core de- /write/ioctl system calls. sign guidelines. The goal is to provide services such as JACK and OSS was replaced by the Advanced Linux Sound Architecture PulseAudio on top of this common infrastructure. PipeWire is media (ALSA) [7]from Linux 2.5. ALSA improved on the OSS API and agnostic and supports arbitrary compressed and uncompressed for- included a user space library that abstracted many of the hardware mats. A common audio infrastructure with backwards compatibility details. The ALSA user-space library also includes a plugin infras- that can support Pro Audio and Desktop Audio use cases can poten- tructure that can be used to create new custom devices and plugins. tially unify the currently fractured audio landscape on Linux desk- Unfortunately, the plugin system is quite static and requires editing tops and workstations and give users and developers a much better of configuration files.
  • Audio on Linux: End of a Golden Age?

    Audio on Linux: End of a Golden Age?

    Audio on Linux: End of a Golden Age? Lars-Peter Clausen – Analog Devices Agenda ● History – Major transitions in software and hardware architecture ● Present – A look at the current situation – Are we in a golden age? ● Future – What major transitions lie ahead of us – How are we going to react to them? Interdependent vs. Modular Interdependent ● No clear boundaries defined between sub- modules ● Different sub-modules are aware of each others internals – Creates dependencies ● Parts can't be upgraded or modified independently of each other Modular ● Partitioning in sub-modules ● Clearly defined functions and interfaces ● Parts can be changed independently of each other – Drop-in replacements ● Constraint by the interface History Humble Beginnings PC Speaker (Beeper) ● Found in all IBM compatible PCs – Present in the first IBM PC 5150 (1981) ● Has only two states – Toggling a specific frequency generates a tone (PWM) ● Magnetic or Piezoelectric plate ● In Linux supported by the input framework Extending Features Soundblaster ● First widespread consumer sound card – Soundblaster 1.0 release in 1989 ● Primarily synthesizer based ● Mono PCM channel ● Became defacto standard for consumer sound cards – Many applications expected a sound blaster interface – Other manufacturers included a Soundblaster compatibility mode in their hardware Audio on Linux Open Sound System (OSS) Open Sound System (OSS) ● Used to be default audio subsystem in v2.4 ● /dev/dsp interface – To playback audio use write() – To capture audio use read() – Some IOCTLs for
  • UC-35 Development of an Automated Software Packaging Solution for Linux

    UC-35 Development of an Automated Software Packaging Solution for Linux

    Automated Software Packaging for Linux using AppImage IT Capstone Program Project Sponsor: Tsai-Tien Tseng Created by: Blair Hill, Robert Ryan, Dylan Parker, Bishwo Marhatta, and Sammi Figueroa Project Description Future Potential • Automate packaging Linux software • Our final script solution automates programs into AppImages with scripts AppImage creation of fully installed written in bash script software • AppImages are a self-contained • Automating the installation of software executable that is portable across would be difficult but theoretically different Linux distributions possible • Specifically focused on • Further automation could be achieved packaging bioinformatics software used with retrieval using curl and git clones Research Areas Figure 2. Script creating an AppImage Intellectual Merit • AppDir structure as the basis for • Automation accelerates the initial creating an AppImage Methodology creation of many AppImages at once • How the foundational software • Automation simplifies AppImage "Appimagetool" is used to turn AppDirs • Study documentation of AppImage, maintenance when a new version of into AppImages related projects, and Linux the software is released • Higher-order software that uses • Implement and test bash scripts "Appimagetool" under the hood to • Local(ex. USB) or remote(ex. server) collect and package software • Study open-source project code for repositories of AppImages streamline solutions setting up new research machines • Linux directory structure and common • Iterate on our scripts • Process could be expanded to other libraries subsets or a wider domain of software • How to find dependencies for a piece of applications software to include in the AppImage Preliminary Results • Our initial automation script utilized outside tools like “Appimage-builder” Abstract Often many scientists and researchers use different versions of Linux to • Created a dependency on Debian-based run software which can cause dependency errors, and makes in Linux distribution's APT software difficult to create a functioning workstation.
  • Snap Vs Flatpak Vs Appimage: Know the Differences | Which Is Better

    Snap Vs Flatpak Vs Appimage: Know the Differences | Which Is Better

    Published on Tux Machines (http://www.tuxmachines.org) Home > content > Snap vs Flatpak vs AppImage: Know The Differences | Which is Better Snap vs Flatpak vs AppImage: Know The Differences | Which is Better By Rianne Schestowitz Created 08/12/2020 - 8:29pm Submitted by Rianne Schestowitz on Tuesday 8th of December 2020 08:29:48 PM Filed under Software [1] Every Linux distribution has its own package manager tool or command-line based repository system to update, install, remove, and manage packages on the system. Despite having a native package manager, sometimes you may need to use a third-party package manager on your Linux system to get the latest version of a package to avoid repository errors and server errors. In the entire post, we have seen the comparison between Snap, AppImage, and Flatpak. Snap, Flatpak, and AppImage; all have their pros and cons. In my opinion, I will always prefer the Flatpak package manager in the first place. If I can?t find any packages on Flatpak, then I?ll go for the AppImage. And finally, Snap is an excellent store of applications, but it still requires some development. I would go to the Snap store for proprietary or semi-proprietary applications than main applications. Please share it with your friends and the Linux community if you find this post useful and informative. Let us know which package manager do you prefer to use on your Linux system. You can write also write down your opinions regarding this post in the comment section. [2] Software Source URL: http://www.tuxmachines.org/node/145224 Links: [1] http://www.tuxmachines.org/taxonomy/term/38 [2] https://www.ubuntupit.com/snap-vs-flatpak-vs-appimage-know-the-difference/.
  • Idiomatic and Reproducible Software Builds Using Containers for Reliable Computing

    Idiomatic and Reproducible Software Builds Using Containers for Reliable Computing

    Master’s Thesis Idiomatic and Reproducible Software Builds using Containers for Reliable Computing Jonas Weber April 18, 2016 arXiv:1702.02999v1 [cs.SE] 9 Feb 2017 Albert-Ludwigs-Universität Freiburg Faculty of Engineering Department of Computer Science Bioinformatics Eingereichte Masterarbeit gemäß den Bestimmungen der Prüfungsordnung der Albert-Ludwidgs-Universität Freiburg für den Studiengang Master of Science (M.Sc.) Informatik vom 19. August 2005. Bearbeitungszeitraum 12. Januar 2016 - 12. Juli 2016 Gutachter Prof. Dr. Rolf Backofen Head of the Group Chair for Bioinformatics Zweitgutachter Prof. Dr. Christoph Scholl Director Chair of Operating Systems Betreuer Dr. Björn Grüning Abstract Containers as the unit of application delivery are the ‘next big thing’ in the software development world. They enable developers to create an executable image containing an application bundled with all its dependencies which a user can run inside a controlled environment with virtualized resources. Complex workflows for business-critical applications and research environments require a high degree of reproducibility which can be accomplished using uniquely identified images as units of computation. It will be shown in this thesis that the most widely used approaches to create an image from pre-existing software or from source code lack the ability to provide idiomaticity in their use of the technology as well as proper reproducibility safe-guards. In the first part, existing approaches are formalized and discussed and a new approach is introduced. The approaches are then evaluated using a suite of three different examples. This thesis provides a framework for formalizing operations involving a layered file system, containers and images, and a novel approach to the creation of images using utility containers and layer donning fulfilling the idiomaticity and reproducibility criteria.
  • Dust3d Documentation Release 1.0.0-Rc.1

    Dust3d Documentation Release 1.0.0-Rc.1

    dust3d Documentation Release 1.0.0-rc.1 Jeremyi HU Aug 10, 2021 Contents: 1 Getting Started 1 1.1 Download and Install Dust3D......................................1 1.2 Dust3D Interface Overview.......................................2 1.3 Menu Bar.................................................3 1.4 Parts Tree Panel.............................................7 1.5 Script Panel................................................ 10 1.6 Dust3D Shortcuts & Hotkey Guide................................... 11 1.7 Dust3D Script Reference......................................... 12 2 Dust3D Modeling Examples 23 2.1 Modeling Ant using Dust3D....................................... 23 2.2 Make a 3D model from scratch using Dust3D.............................. 26 2.3 Modeling Camel using Dust3D..................................... 26 2.4 Modeling Horse using Dust3D...................................... 27 3 For Developers 29 3.1 Building Dust3D............................................. 29 3.2 Write a 3D modeling software from scratch............................... 32 4 Indices and tables 41 i ii CHAPTER 1 Getting Started 1.1 Download and Install Dust3D • For Windows (64 Bit): https://github.com/huxingyi/dust3d/releases/download/1.0.0-rc.6/dust3d-1.0.0-rc.6.zip No need to install, unzip and run the exe. • For Windows (32 Bit): https://github.com/huxingyi/dust3d/releases/download/1.0.0-rc.6/dust3d-1.0.0-rc.6-x86.zip No need to install, unzip and run the exe. • For Mac OS X: https://github.com/huxingyi/dust3d/releases/download/1.0.0-rc.6/dust3d-1.0.0-rc.6.dmg If “The following disk images couldn’t be opened” popped up, that means the downloaded file was broken, please retry. If “can’t be opened because its integrity cannot be verified” popped up, please follow ni_kush’s answer in this reddit post.