cpack 创建 deb 包时出现问题
我在主 CMakeListst.txt 中设置了 CPACK_PACKAGE_CONTACT 和 CPACK_DEBIAN_PACKAGE_MAINTAINER 。 cmake 本身运行创建的 CPackConfig.cmake 和 CPackSourceConfig.cmake 都包含变量集。
CPack 仍以
CPack: Create package using DEB 退出 CPack：安装项目 CPack： - 运行预安装目标： CPack： - 安装项目： CPack：创建包 /usr/share/cmake-2.8/Modules/CPackDeb.cmake:274 处的 CMake 错误（消息）： CPackDeb：Debian 软件包需要软件包的维护者，设置 CPACK_PACKAGE_CONTACT 或 CPACK_DEBIAN_PACKAGE_MAINTAINER
有谁知道出了什么问题或如何找出这里发生了什么？
I set CPACK_PACKAGE_CONTACT and CPACK_DEBIAN_PACKAGE_MAINTAINER in my main CMakeListst.txt. cmake itself runs an the created CPackConfig.cmake and CPackSourceConfig.cmake both contain the variables set.
CPack still exits with
CPack: Create package using DEB
CPack: Install projects
CPack: - Run preinstall target for:
CPack: - Install project:
CPack: Create package
CMake Error at /usr/share/cmake-2.8/Modules/CPackDeb.cmake:274 (MESSAGE):
CPackDeb: Debian package requires a maintainer for a package, set
CPACK_PACKAGE_CONTACT or CPACK_DEBIAN_PACKAGE_MAINTAINER
Does anybody have an idea what is wrong or how to find out what is going on here?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
谢谢！ --debug 和 -V 帮助了我。确实应该记录下来！
我发现了问题 - 我在 SET 命令
SET(CPACK_DEBIAN_PACKAGE_MAINTAINER, "Andreas Loew")
中使用了“,”，这不会给出错误，而只是将变量留空...
CMake 似乎将其内容复制到 CPack配置没有任何改变，里面留下了假的“，”。
Thanks! The --debug and -V helped me. Should really be documented!
I found the problem - I used a "," in the SET command
SET(CPACK_DEBIAN_PACKAGE_MAINTAINER, "Andreas Loew")
this does not give an error but simply leaves the variable empty...
CMake seems to copy the content of this to the CPack configuration without any change, leaving the false "," inside.
嗯嗯。 “cpack --help”似乎没有完整记录其命令行选项...
如果您使用“cpack -V”，您将获得更详细的输出。如果您使用“cpack --debug”，您将获得大量输出，您可以费力地浏览这些输出以尝试找到有关问题所在的提示。
尝试一下，看看输出是否对您有帮助。如果没有，也许它至少会产生更多信息，您可以在问题编辑中发布以尝试找出问题所在。
你使用什么版本的cpack？
Hmmmm. "cpack --help" does not appear to document its command line options fully...
If you use "cpack -V", you'll get more verbose output. If you use "cpack --debug", you'll get a ton of output that you can wade through to try to find hints about what went wrong.
Give those a try, and see if any of the output helps you. If not, perhaps it will at least yield some more information you can post in a question edit to try to track down what the problem is.
What version of cpack are you using?