Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
Cardboard VR Projects for Android

You're reading from   Cardboard VR Projects for Android Develop mobile virtual reality apps using the native Google Cardboard SDK for Android

Arrow left icon
Product type Paperback
Published in May 2016
Publisher
ISBN-13 9781785887871
Length 386 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Authors (2):
Arrow left icon
 Linowes Linowes
Author Profile Icon Linowes
Linowes
 Schoen Schoen
Author Profile Icon Schoen
Schoen
Arrow right icon
View More author details
Toc

Table of Contents (16) Chapters Close

Cardboard VR Projects for Android
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface
1. Virtual Reality for Everyone FREE CHAPTER 2. The Skeleton Cardboard Project 3. Cardboard Box 4. Launcher Lobby 5. RenderBox Engine 6. Solar System 7. 360-Degree Gallery 8. 3D Model Viewer 9. Music Visualizer Index

Exporting the RenderBox package


Now that we've finished creating this beautiful RenderBox library, how do we reuse it in other projects? This is where modules and .aar files come into play. There are a number of ways to share code between Android projects. The most obvious way is to literally copy pieces of code into the next project as you see fit. While this is perfectly acceptable in certain situations, and in fact should be part of your normal process, it can become quite tedious. What if we have a bunch of files that reference each other and depend on a certain file hierarchy, such as RenderBox? If you're familiar with Java development, you might say, "Well, obviously just export the compiled classes in a .jar file." You would be right, except that this is Android. We have some generated classes as well as the /res folder, which contains, in this case, our shader code. What we actually want is an .aar file. Android programmers might be familiar with .aidl files, which are used for...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime
Visually different images