从windows移植到Android时如何获取软件的硬件要求？
我想将一个在windows平台上用OpenGL编写的3D程序移植到Android上，但我不知道它在一般的Android平台上是否可以顺利运行，所以我想估计多少硬件资源足以让它顺利运行。它类似于公司向用户推荐的软件或 3D 游戏的硬件要求。我不知道移植到Android 时如何获得程序的硬件要求。
我使用了 gdebugger，它给了我一些信息，但我认为这对我来说还不够。这里有人有一些想法或解决方案吗？非常感谢！
I want to transplant a 3D program written in OpenGL on windows platform to Android, but I wonder if it can run smoothly on general Android platforms, so i want to estimate how much hardware resource is sufficient for it to run smoothly. It is some kind like the hardware requirements for a software or 3d game that a company will recommend the users. I don't know how can i get a hardware requirements of my program when transplant to Android.
i used gdebugger and it gave me some information but i don't think that is enough for me. Anyone here have some idea or solution? Many thanks in advance!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
取决于您使用的功能集。例如，如果您使用FBO，设备将必须支持帧缓冲区扩展。如果使用MSAA，线路流畅，设备就会支持相应的扩展。
列出您的要求后，您可以使用 glGet 检查设备支持
http://www.opengl.org/sdk/docs/man/xhtml /glGet.xml
Depends on feature set that you use. For example, if you use FBO, the device will have to support framebuffer extension. If you use MSAA, smooth line, the device will have support corresponding extensions.
After listing down your requirements, you can use glGet to check for the device suppport
http://www.opengl.org/sdk/docs/man/xhtml/glGet.xml
如果您的程序足够简单，您可以编写一些有关纹理填充率的估计值，这是渲染性能的一个非常基本（且古老）的指标。几乎每个 3D 芯片都带有理论填充率，因此您可以获得桌面系统和某些 Android 手机的理论填充率。
纹理内存占用是您可以估计的另一件事，尤其是使用 gdebugger。再说一遍，这些数字对于大多数芯片来说都是已知的。
这是产生一些数字的快速方法，显然没有任何现实生活中的性能保证。
If your program is simple enough, you could write up some estimates about texture fill rate, which is a pretty basic (and old) metric of rendering performance. Nearly every 3D chip comes with a theoretical fill rate, so you can get the theoretical numbers of both your desktop system and some Android phones.
The texture memory footprint is another thing that you can estimate, especially using gdebugger. Once again, these numbers are known for most chips.
This is a quick way to produce some numbers, obviously without any real life performance guarantees.
最好的方法是在实际设备上进行测试，并了解哪些硬件运行良好。您可以分发测试版应用程序并获得一些反馈。
The best way would be to test it on an actual device, and get an idea of what hardware works well. You could distribute a beta app and get some feedback too.