Re: [cmake-developers] CPack BAR package generator
Stephen Kelly steveire@... writes: Do you have any thoughts on the CPACK_PACKAGE_CONTACT problem? Namely that the debian generator and the BAR generator have differing expectations on what such a thing would contain. Should we have separate CPACK_PACKAGE_CONTACT_NAME and CPACK_PACKAGE_CONTACT_EMAIL variables? Eric, do you have any thoughts on this issue? I'll soon try to revive this. See the discussion so far at: http://thread.gmane.org/gmane.comp.programming.tools.cmake.devel/7530 Thanks, Steve. -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] CPack BAR package generator
Stephen Kelly steveire@... writes: Do you have any thoughts on the CPACK_PACKAGE_CONTACT problem? Namely that the debian generator and the BAR generator have differing expectations on what such a thing would contain. Should we have separate CPACK_PACKAGE_CONTACT_NAME and CPACK_PACKAGE_CONTACT_EMAIL variables? Eric, do you have any thoughts on this issue? I'll soon try to revive this. See the discussion so far at: http://thread.gmane.org/gmane.comp.programming.tools.cmake.devel/7530 What about using the typical format that contains both name and email address in CPACK_PACKAGE_CONTACT? Would David Cole dlrd...@aol.com work if used in that context for both of these generators...? Or would that make one of them choke? References: http://stackoverflow.com/questions/2631065/what-is-the-format-of-email-header-name-email http://tools.ietf.org/html/rfc2822#section-3.4 D -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] CPack BAR package generator
2013/10/29 David Cole dlrd...@aol.com: Stephen Kelly steveire@... writes: Do you have any thoughts on the CPACK_PACKAGE_CONTACT problem? Namely that the debian generator and the BAR generator have differing expectations on what such a thing would contain. Should we have separate CPACK_PACKAGE_CONTACT_NAME and CPACK_PACKAGE_CONTACT_EMAIL variables? Eric, do you have any thoughts on this issue? Sorry Steve, But my bandwidth on the CMake/CPack front is currently so low that I can barely follow CMake ML discussion correctly. I'll soon try to revive this. See the discussion so far at: http://thread.gmane.org/gmane.comp.programming.tools.cmake.devel/7530 I remember but I have no time to help further right now and for 3 up to 4 weeks from now. What about using the typical format that contains both name and email address in CPACK_PACKAGE_CONTACT? Would David Cole dlrd...@aol.com work if used in that context for both of these generators...? Or would that make one of them choke? This is OK with Debian. Note that concerning Debian, CPACK_PACKAGE_CONTACT is used as a deafult value for CPACK_DEBIAN_PACKAGE_MAINTAINER which is mandatory. If ever the chosen common format for CPACK_PACKAGE_CONTACT is not suitable as-is for filling CPACK_DEBIAN_PACKAGE_MAINTAINER we may be able to automatically extract the relevant bits from CPACK_PACKAGE_CONTACT in order to put appropriate value in CPACK_DEBIAN_PACKAGE_MAINTAINER. Currently we simply do: # Maintainer: (mandatory) if(NOT CPACK_DEBIAN_PACKAGE_MAINTAINER) if(NOT CPACK_PACKAGE_CONTACT) message(FATAL_ERROR CPackDeb: Debian package requires a maintainer for a package, set CPACK_PACKAGE_CONTACT or CPACK_DEBIAN_PACKAGE_MAINTAINER) endif() set(CPACK_DEBIAN_PACKAGE_MAINTAINER ${CPACK_PACKAGE_CONTACT}) endif() References: http://stackoverflow.com/questions/2631065/what-is-the-format-of-email-header-name-email http://tools.ietf.org/html/rfc2822#section-3.4 David Cole dlrd...@aol.com works fine as-is for .deb. The regex shown on the Stackoverflow article is scary. I guess CPack does not have to validate that. -- Erk L'élection n'est pas la démocratie -- http://www.le-message.org -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] CPack BAR package generator
References: http://stackoverflow.com/questions/2631065/what-is-the-format-of-email-header-name-email http://tools.ietf.org/html/rfc2822#section-3.4 David Cole dlrd...@aol.com works fine as-is for .deb. Thanks -- good to know. The regex shown on the Stackoverflow article is scary. I guess CPack does not have to validate that. Scary? I was thinking completely ridiculous, and nearly incomprehensible... which, I guess, naturally leads to scary. I would hate to be the one to try to use that regex in the CMake language... :-) D -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] CPack BAR package generator
2013/9/20 Stephen Kelly steve...@gmail.com: Stephen Kelly steveire@... writes: https://gitorious.org/~steveire/cmake/steveires-cmake It is the start of a CPack generator for BlackBerry BAR packages, required for deployment to those devices. I haven't worked much with CPack before, so I'd appreciate some feedback even at this early point. Eric, and response to this? I'm looking at it right now. 1) You lack at least a CPackBAR.cmake in which you should put the documentation for each CPACK_BAR_xx specific variable usage. Have a look at CPackWIX.cmake or CPackRPM.cmake etc You can check if it's working with: cpack --help-variable CPACK_BAR_xx 2) You shouldn't do add_custom_target(bbpackage COMMAND ${CMAKE_CPACK_COMMAND} -G BAR ) but set(CPACK_GENERATOR BAR) then make package or cpack with no args in the build tree should biuld a BAR package. see cpack --help-variable CPACK_GENERATOR 3) Depending on how much flexibility you want you may chose to do some of the work inside a CMake script like CPackRPM.cmake does or do all you want to do inside the C++ code (cmCPackBARGenerator::PackageFiles) like NSIS or DEB does. Offering some trap in your CPackBAR.cmake may ease 4) You should obviously have some tests for it. (CMakeSource/Tests/CPack*) 4.1) ensure that CPackTestAllGenerators/ works and may be CPackComponents/ CPackComponentsForAll/ as well. 4.2) develop BAR specific test like for CPackWiXGenerator/ I do not have the time to do a test build yet, but I'll try. Thanks, Steve. -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers -- Erk L'élection n'est pas la démocratie -- http://www.le-message.org -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
[cmake-developers] CPack BAR package generator
Hi there, I've pushed a cpack-bar-package topic to my clone https://gitorious.org/~steveire/cmake/steveires-cmake It is the start of a CPack generator for BlackBerry BAR packages, required for deployment to those devices. I haven't worked much with CPack before, so I'd appreciate some feedback even at this early point. Some issues that have come up already are in the commit message. Thanks, Steve. -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers