Using RajawaliVR with current Rajawali main branch

[yakobom]

Hi,
I was not able to get this working - seems like the current Rajawali dev env has changed (Android Studio support?) so I cannot compile it, the required imports cannot be found...
Any ideas?

Thanks,
yakobom

[flankechen]

@MasDennis
Agree, Rajawali master branch is developing quite fast these days, while VR and AR depends on out of day codes.
I found that even RajawaliActivity is removed.
hopefully, VR and AR branch would catch up the main branch.

[MasDennis]

AR is up to date but VR isn't yet. We are working on this.

[yakobom]

OK, I will be waiting for that.
Thank you very much.

yakobom

[MasDennis]

Hi @yakobom I managed to do it already. Please check the latest update and tell me if you have any problems 🍻

[yakobom]

Thanks a lot for the notification!
I will check it out and let you know.

yakobom

On Fri, May 29, 2015 at 1:40 AM, Dennis Ippel [email protected]
wrote:

Hi @yakobom https://github.com/yakobom I managed to do it already.
Please check the latest update and tell me if you have any problems [image:
🍻]

—
Reply to this email directly or view it on GitHub
#5 (comment).

[yakobom]

Hi,
Just to let you knw - I have left it for now, spent to much time trying to build it, perhaps something is wrong with my private configuration.

[SebastienANTOINE]

Cannot able to build it. Seems broken

[MasDennis]

@SebastienANTOINE can you be a bit more specific? Do you get any messages?

[thebradbain]

@MasDennis I'm not able to build it either. I'll open up a separate issue.

[RamIndani]

I was facing same issue so I opened ticket #14
I pulled branch instead of master and it worked for me.

[JCFerrerG]

The description of #14 sounds similar to this issue and provides enough details to troubleshoot.

Unfortunately, this thread does not have enough information to troubleshoot the issue. The only tangible details can detect are

I cannot compile it, the required imports cannot be found...

and

[not] able to build it...

Given this limited information, it seems to me that #14 is probably a description of this issue -- or perhaps this is a separate issue with an invalid description. Without some clear details (like error messages and environment info), this ticket might get closed as an invalid issue.