Difference between revisions of "Autobuild/Package Layout"
Jump to navigation
Jump to search
Brad Linden (talk | contribs) |
m (add category) |
||
| Line 18: | Line 18: | ||
# 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). | # 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:Autobuild]] [[Category:Open Source Portal]] | ||
Revision as of 05:37, 7 February 2011
tarball layout
- bin
- cmake
- include
- include/<packagename>
- lib
- lib/debug
- lib/relwithdebinfo
- lib/release
- lib/python25
- LICENSES
gotchas
- 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
- 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).