Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Povray Termux Package Request #291

Open
SDRausty opened this issue May 18, 2017 · 3 comments
Open

Povray Termux Package Request #291

SDRausty opened this issue May 18, 2017 · 3 comments
Labels
informational no action planned, but left open as a source of information for other users

Comments

@SDRausty
Copy link

Hello! @koppi managed to get Povray 3.1 running on his smartphone about a year ago. https://m.imgur.com/a/p8Ali Povray has a package request termux/termux-packages#202 for Termux from about a year ago. Can anyone here help in packaging Povray for Termux?

There is active development going on now at IRC channel: #termux on freenode https://gitter.im/termux/termux and at https://github.com/termux/termux-packages However it appears that packaging Povray for Termux is stalled for almost a year now...

screenshot_20170517-215805

I will love to have Povray running in my smartphone. Can anyone help, please?

@c-lipka
Copy link
Contributor

c-lipka commented Jun 23, 2017

According to termux/termux-packages#202, the problem is getting the boost libraries to compile on Android. Since POV-Ray 3.7 relies heavily on boost throughout the code, that's a deal breaker.

Thanks to C++11, the boost features most extensively used have become available "out of the box" in modern compilers by now: Smart pointers, threads and thread synchronization. So there's some hope that future versions of POV-Ray might be able to compile without boost (while POV-Ray 3.7.1 still uses C++03, we're considering moving to C++11 for POV-Ray 3.7.2). But there's a caveat with the C++11 threads (they don't provide an interface to set a stack size, while the boost implementation does), and there are also some other boost features in use here and there (date and time stuff comes to mind, as well as singletons); so it might be necessary to disable some features, and suffer some drawbacks such as increased memory footprint in others.

And even if POV-Ray becomes sufficiently boost-independent again, porting it to Termux would presumably need someone outside the dev team to pick up the glove, as frankly we probably don't have the time ourselves.

@c-lipka c-lipka added ToDo: volunteers action by community required: needs assistance ToDo: refactor action required: change internal architecture first compatibility reported or triaged as compatibility issue, i.e. affecting only some build or runtime environments labels Jun 23, 2017
@SDRausty
Copy link
Author

SDRausty commented Jul 1, 2017

screenshot_20170701-194819

$ packages list-installed |grep boost

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

boost/stable,now 1.64.0-1 aarch64 [installed]
boost-dev/stable,now 1.64.0-1 aarch64 [installed]

Boost libs
termux/termux-packages#974 by its-pointless was merged on May 3

@SDRausty
Copy link
Author

Do you find Arch Linux in Termux PRoot and Termux on device insiping? These images were raytraced on a smartphone in Termux in Android, January 2018. They were created with Povray in Arch Linux Termux PRoot. This website is about Povray in Arch Linux in Termux PRoot and is being built around Package Request: Povray and Povray Termux Package Request. More information at https://sdrausty.github.io/TermuxPovray/docs. The files are amazing. Thank you for keeping this project up to date.

scifi_demo512

julia512

field512

1ag9512

1asy512

tulips512

pebbles512

@c-lipka c-lipka added informational no action planned, but left open as a source of information for other users and removed ToDo: refactor action required: change internal architecture first ToDo: volunteers action by community required: needs assistance compatibility reported or triaged as compatibility issue, i.e. affecting only some build or runtime environments labels Jun 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
informational no action planned, but left open as a source of information for other users
Projects
None yet
Development

No branches or pull requests

2 participants