Difference between revisions of "Autobuild/Package Layout"

From Second Life Wiki
Jump to navigation Jump to search
(Created page with "=== tarball layout === *bin *cmake *include **include/<packagename> *lib **lib/debug **lib/relwithdebinfo **lib/release **lib/python25 *LICENSES === gotchas === # some existin…")
 
Line 16: Line 16:
# some existing packages have their libraries located directly under lib, some have them under lib/{debug,relwithdebinfo,release}
# some existing packages have their libraries located directly under lib, some have them under lib/{debug,relwithdebinfo,release}
# python pacakges are not fully supported, as we have not determined how to cleanly organize python module directories for compatibility with multiple python versions
# python pacakges are not fully supported, as we have not determined how to cleanly organize python module directories for compatibility with multiple python versions
# this is not compatible with the legacy package layout used in the indra codebase, they need to be converted to the legacy layout to be used with install.py for now. UPDATE: {{User|Brad}} has gotten [[Autobuild/Teamcity|TeamCity]] to do this for us by using a BuildParam value to configure this (build_legacy_package can be set to true).
# this is not compatible with the legacy package layout used in the indra codebase, they need to be converted to the legacy layout to be used with install.py for now. UPDATE: {{User|Brad_Linden}} has gotten [[Autobuild/Teamcity|TeamCity]] to do this for us by using a BuildParam value to configure this (build_legacy_package can be set to true).


[[Category:Open Source Portal]]
[[Category:Open Source Portal]]

Revision as of 13:28, 10 January 2011

tarball layout

  • bin
  • cmake
  • include
    • include/<packagename>
  • lib
    • lib/debug
    • lib/relwithdebinfo
    • lib/release
    • lib/python25
  • LICENSES

gotchas

  1. some existing packages have their libraries located directly under lib, some have them under lib/{debug,relwithdebinfo,release}
  2. python pacakges are not fully supported, as we have not determined how to cleanly organize python module directories for compatibility with multiple python versions
  3. this is not compatible with the legacy package layout used in the indra codebase, they need to be converted to the legacy layout to be used with install.py for now. UPDATE: Brad_Linden has gotten TeamCity to do this for us by using a BuildParam value to configure this (build_legacy_package can be set to true).