-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change how platform packages without a mapping in rosdep/*.yaml are handled for OpenEmbedded #223
Comments
Do this by having superflore use superflore will no longer use the OpenEmbedded Layer Index to guess mappings. |
This change has been incorporated into revision 40 of the Superflore OE Recipe Generation Scheme wiki page. |
…s-infrastructure#223) - Add -native to ROS_SUPERFLORE_GENERATED_PLATFORM_PACKAGE_DEPENDENCIES. - yoctoRecipe.rosdep_cache is now only used to generate rosdep-resolved.yaml . - Also rename generate_rosdistro_conf() -> generate_ros_distro_inc()
…s-infrastructure#223) - Add -native to ROS_SUPERFLORE_GENERATED_PLATFORM_PACKAGE_DEPENDENCIES. - yoctoRecipe.rosdep_cache is now only used to generate rosdep-resolved.yaml . - Also rename generate_rosdistro_conf() -> generate_ros_distro_inc()
…nfrastructure#223) - Use ${ROS_UNRESOLVED_PLATFORM_PKG_<PLATFORM_PKG>} as the mapped value when <PLATFORM_PKG> isn't resolved by entries in rosdep/*.yaml and add assignments of the form ROS_UNRESOLVED_PLATFORM_PKG_<PLATFORM_PKG> = "UNRESOLVED-<PLATFORM_PKG>" to conf/ros-distro/include/<ROS_DISTRO>/generated-ros-distro.inc . These assignments are then manually overridden in conf/ros-distro/include/<ROS_DISTRO>/ros-distro.inc as the mappings are determined. This make possible rapid iteration because superflore need not be rerun until rosdep/*.yaml are updated with all of the new mappings. - Drop using the OpenEmbedded Layer Index to guess the mapping of an unresolved platform package. It would often guess wrong, requiring a rerun of superflore. This change means that yoctoRecipe.rosdep_cache is now only used to generate rosdep-resolved.yaml . - Also rename generate_rosdistro_conf() -> generate_ros_distro_inc()
…nfrastructure#223) - Use ${ROS_UNRESOLVED_PLATFORM_PKG_<PLATFORM_PKG>} as the mapped value when <PLATFORM_PKG> isn't resolved by entries in rosdep/*.yaml and add assignments of the form ROS_UNRESOLVED_PLATFORM_PKG_<PLATFORM_PKG> = "UNRESOLVED-<PLATFORM_PKG>" to conf/ros-distro/include/<ROS_DISTRO>/generated-ros-distro.inc . These assignments are then manually overridden in conf/ros-distro/include/<ROS_DISTRO>/ros-distro.inc as the mappings are determined. This make possible rapid iteration because superflore need not be rerun until rosdep/*.yaml are updated with all of the new mappings. - Drop using the OpenEmbedded Layer Index to guess the mapping of an unresolved platform package. It would often guess wrong, requiring a rerun of superflore. This change means that there is no longer a dependency on "bs4" and that yoctoRecipe.rosdep_cache is now only used to generate rosdep-resolved.yaml . - Also, rename generate_rosdistro_conf() to generate_ros_distro_inc() so that it corresponds to the name of the file it generates.
…nfrastructure#223) - Use ${ROS_UNRESOLVED_PLATFORM_PKG_<PLATFORM_PKG>} as the mapped value when <PLATFORM_PKG> isn't resolved by entries in rosdep/*.yaml and add assignments of the form ROS_UNRESOLVED_PLATFORM_PKG_<PLATFORM_PKG> = "UNRESOLVED-<PLATFORM_PKG>" to conf/ros-distro/include/<ROS_DISTRO>/generated-ros-distro.inc . These assignments are then manually overridden in conf/ros-distro/include/<ROS_DISTRO>/ros-distro.inc as the mappings are determined. This make possible rapid iteration because superflore need not be rerun until rosdep/*.yaml are updated with all of the new mappings. - Drop using the OpenEmbedded Layer Index to guess the mapping of an unresolved platform package. It would often guess wrong, requiring a rerun of superflore. This change means that there is no longer a dependency on "bs4" and that yoctoRecipe.rosdep_cache is now only used to generate rosdep-resolved.yaml . - Also, rename generate_rosdistro_conf() to generate_ros_distro_inc() so that it corresponds to the name of the file it generates.
…nfrastructure#223) - Use ${ROS_UNRESOLVED_PLATFORM_PKG_<PLATFORM_PKG>} as the mapped value when <PLATFORM_PKG> isn't resolved by entries in rosdep/*.yaml and add assignments of the form ROS_UNRESOLVED_PLATFORM_PKG_<PLATFORM_PKG> = "UNRESOLVED-<PLATFORM_PKG>" to conf/ros-distro/include/<ROS_DISTRO>/generated-ros-distro.inc . These assignments are then manually overridden in conf/ros-distro/include/<ROS_DISTRO>/ros-distro.inc as the mappings are determined. This make possible rapid iteration because superflore need not be rerun until rosdep/*.yaml are updated with all of the new mappings. - Drop using the OpenEmbedded Layer Index to guess the mapping of an unresolved platform package. It would often guess wrong, requiring a rerun of superflore. This change means that there is no longer a dependency on "bs4" and that yoctoRecipe.rosdep_cache is now only used to generate rosdep-resolved.yaml . - Also, rename generate_rosdistro_conf() to generate_ros_distro_inc() so that it corresponds to the name of the file it generates.
…nfrastructure#223) - Use ${ROS_UNRESOLVED_PLATFORM_PKG_<PLATFORM_PKG>} as the mapped value when <PLATFORM_PKG> isn't resolved by entries in rosdep/*.yaml and add assignments of the form ROS_UNRESOLVED_PLATFORM_PKG_<PLATFORM_PKG> = "UNRESOLVED-<PLATFORM_PKG>" to conf/ros-distro/include/<ROS_DISTRO>/generated-ros-distro.inc . These assignments are then manually overridden in conf/ros-distro/include/<ROS_DISTRO>/ros-distro.inc as the mappings are determined. This make possible rapid iteration because superflore need not be rerun until rosdep/*.yaml are updated with all of the new mappings. - Drop using the OpenEmbedded Layer Index to guess the mapping of an unresolved platform package. It would often guess wrong, requiring a rerun of superflore. This change means that there is no longer a dependency on "bs4" and that yoctoRecipe.rosdep_cache is now only used to generate rosdep-resolved.yaml . - Also, rename generate_rosdistro_conf() to generate_ros_distro_inc() so that it corresponds to the name of the file it generates.
…nfrastructure#223) - Use ${ROS_UNRESOLVED_PLATFORM_PKG_<PLATFORM_PKG>} as the mapped value when <PLATFORM_PKG> isn't resolved by entries in rosdep/*.yaml and add assignments of the form ROS_UNRESOLVED_PLATFORM_PKG_<PLATFORM_PKG> = "UNRESOLVED-<PLATFORM_PKG>" to conf/ros-distro/include/<ROS_DISTRO>/generated-ros-distro.inc . These assignments are then manually overridden in conf/ros-distro/include/<ROS_DISTRO>/ros-distro.inc as the mappings are determined. This make possible rapid iteration because superflore need not be rerun until rosdep/*.yaml are updated with all of the new mappings. - Drop using the OpenEmbedded Layer Index to guess the mapping of an unresolved platform package. It would often guess wrong, requiring a rerun of superflore. This change means that there is no longer a dependency on "bs4" and that yoctoRecipe.rosdep_cache is now only used to generate rosdep-resolved.yaml . - Also, rename generate_rosdistro_conf() to generate_ros_distro_inc() so that it corresponds to the name of the file it generates.
…nfrastructure#223) - Use ${ROS_UNRESOLVED_PLATFORM_PKG_<PLATFORM_PKG>} as the mapped value when <PLATFORM_PKG> isn't resolved by entries in rosdep/*.yaml and add assignments of the form ROS_UNRESOLVED_PLATFORM_PKG_<PLATFORM_PKG> = "UNRESOLVED-<PLATFORM_PKG>" to conf/ros-distro/include/<ROS_DISTRO>/generated-ros-distro.inc . These assignments are then manually overridden in conf/ros-distro/include/<ROS_DISTRO>/ros-distro.inc as the mappings are determined. This make possible rapid iteration because superflore need not be rerun until rosdep/*.yaml are updated with all of the new mappings. - Drop using the OpenEmbedded Layer Index to guess the mapping of an unresolved platform package. It would often guess wrong, requiring a rerun of superflore. This change means that there is no longer a dependency on "bs4" and that yoctoRecipe.rosdep_cache is now only used to generate rosdep-resolved.yaml . - Also, rename generate_rosdistro_conf() to generate_ros_distro_inc() so that it corresponds to the name of the file it generates.
…nfrastructure#223) - Use ${ROS_UNRESOLVED_PLATFORM_PKG_<PLATFORM_PKG>} as the mapped value when <PLATFORM_PKG> isn't resolved by entries in rosdep/*.yaml and add assignments of the form ROS_UNRESOLVED_PLATFORM_PKG_<PLATFORM_PKG> = "UNRESOLVED-<PLATFORM_PKG>" to conf/ros-distro/include/<ROS_DISTRO>/generated-ros-distro.inc . These assignments are then manually overridden in conf/ros-distro/include/<ROS_DISTRO>/ros-distro.inc as the mappings are determined. This make possible rapid iteration because superflore need not be rerun until rosdep/*.yaml are updated with all of the new mappings. - Drop using the OpenEmbedded Layer Index to guess the mapping of an unresolved platform package. It would often guess wrong, requiring a rerun of superflore. This change means that there is no longer a dependency on "bs4" and that yoctoRecipe.rosdep_cache is now only used to generate rosdep-resolved.yaml . - Also, rename generate_rosdistro_conf() to generate_ros_distro_inc() so that it corresponds to the name of the file it generates.
…nfrastructure#223) - Use ${ROS_UNRESOLVED_PLATFORM_PKG_<PLATFORM_PKG>} as the mapped value when <PLATFORM_PKG> isn't resolved by entries in rosdep/*.yaml and add assignments of the form ROS_UNRESOLVED_PLATFORM_PKG_<PLATFORM_PKG> = "UNRESOLVED-<PLATFORM_PKG>" to conf/ros-distro/include/<ROS_DISTRO>/generated-ros-distro.inc . These assignments are then manually overridden in conf/ros-distro/include/<ROS_DISTRO>/ros-distro.inc as the mappings are determined. This make possible rapid iteration because superflore need not be rerun until rosdep/*.yaml are updated with all of the new mappings. - Drop using the OpenEmbedded Layer Index to guess the mapping of an unresolved platform package. It would often guess wrong, requiring a rerun of superflore. This change means that there is no longer a dependency on "bs4" and that yoctoRecipe.rosdep_cache is now only used to generate rosdep-resolved.yaml . - Also, rename generate_rosdistro_conf() to generate_ros_distro_inc() so that it corresponds to the name of the file it generates.
…nfrastructure#223) - Use ${ROS_UNRESOLVED_PLATFORM_PKG_<PLATFORM_PKG>} as the mapped value when <PLATFORM_PKG> isn't resolved by entries in rosdep/*.yaml and add assignments of the form ROS_UNRESOLVED_PLATFORM_PKG_<PLATFORM_PKG> = "UNRESOLVED-<PLATFORM_PKG>" to conf/ros-distro/include/<ROS_DISTRO>/generated-ros-distro.inc . These assignments are then manually overridden in conf/ros-distro/include/<ROS_DISTRO>/ros-distro.inc as the mappings are determined. This make possible rapid iteration because superflore need not be rerun until rosdep/*.yaml are updated with all of the new mappings. - Drop using the OpenEmbedded Layer Index to guess the mapping of an unresolved platform package. It would often guess wrong, requiring a rerun of superflore. This change means that there is no longer a dependency on "bs4" and that yoctoRecipe.rosdep_cache is now only used to generate rosdep-resolved.yaml . - Also, rename generate_rosdistro_conf() to generate_ros_distro_inc() so that it corresponds to the name of the file it generates.
- Use ${ROS_UNRESOLVED_PLATFORM_PKG_<PLATFORM_PKG>} as the mapped value when <PLATFORM_PKG> isn't resolved by entries in rosdep/*.yaml and add assignments of the form ROS_UNRESOLVED_PLATFORM_PKG_<PLATFORM_PKG> = "UNRESOLVED-<PLATFORM_PKG>" to conf/ros-distro/include/<ROS_DISTRO>/generated-ros-distro.inc . These assignments are then manually overridden in conf/ros-distro/include/<ROS_DISTRO>/ros-distro.inc as the mappings are determined. This make possible rapid iteration because superflore need not be rerun until rosdep/*.yaml are updated with all of the new mappings. - Drop using the OpenEmbedded Layer Index to guess the mapping of an unresolved platform package. It would often guess wrong, requiring a rerun of superflore. This change means that there is no longer a dependency on "bs4" and that yoctoRecipe.rosdep_cache is now only used to generate rosdep-resolved.yaml . - Also, rename generate_rosdistro_conf() to generate_ros_distro_inc() so that it corresponds to the name of the file it generates. - This commit resolves issue ros-infrastructure#223.
- Use ${ROS_UNRESOLVED_PLATFORM_PKG_<PLATFORM_PKG>} as the mapped value when <PLATFORM_PKG> isn't resolved by entries in rosdep/*.yaml and add assignments of the form ROS_UNRESOLVED_PLATFORM_PKG_<PLATFORM_PKG> = "UNRESOLVED-<PLATFORM_PKG>" to conf/ros-distro/include/<ROS_DISTRO>/generated-ros-distro.inc . These assignments are then manually overridden in conf/ros-distro/include/<ROS_DISTRO>/ros-distro.inc as the mappings are determined. This make possible rapid iteration because superflore need not be rerun until rosdep/*.yaml are updated with all of the new mappings. - Drop using the OpenEmbedded Layer Index to guess the mapping of an unresolved platform package. It would often guess wrong, requiring a rerun of superflore. This change means that there is no longer a dependency on "bs4" and that yoctoRecipe.rosdep_cache is now only used to generate rosdep-resolved.yaml . - Also, rename generate_rosdistro_conf() to generate_ros_distro_inc() so that it corresponds to the name of the file it generates. - This commit resolves issue ros-infrastructure#223.
- Use ${ROS_UNRESOLVED_PLATFORM_PKG_<PLATFORM_PKG>} as the mapped value when <PLATFORM_PKG> isn't resolved by entries in rosdep/*.yaml and add assignments of the form ROS_UNRESOLVED_PLATFORM_PKG_<PLATFORM_PKG> = "UNRESOLVED-<PLATFORM_PKG>" to conf/ros-distro/include/<ROS_DISTRO>/generated-ros-distro.inc . These assignments are then manually overridden in conf/ros-distro/include/<ROS_DISTRO>/ros-distro.inc as the mappings are determined. This make possible rapid iteration because superflore need not be rerun until rosdep/*.yaml are updated with all of the new mappings. - Drop using the OpenEmbedded Layer Index to guess the mapping of an unresolved platform package. It would often guess wrong, requiring a rerun of superflore. This change means that there is no longer a dependency on "bs4" and that yoctoRecipe.rosdep_cache is now only used to generate rosdep-resolved.yaml . - Also, rename generate_rosdistro_conf() to generate_ros_distro_inc() so that it corresponds to the name of the file it generates. - This commit resolves issue ros-infrastructure#223. Signed-off-by: Martin Jansa <[email protected]>
- Use ${ROS_UNRESOLVED_PLATFORM_PKG_<PLATFORM_PKG>} as the mapped value when <PLATFORM_PKG> isn't resolved by entries in rosdep/*.yaml and add assignments of the form ROS_UNRESOLVED_PLATFORM_PKG_<PLATFORM_PKG> = "UNRESOLVED-<PLATFORM_PKG>" to conf/ros-distro/include/<ROS_DISTRO>/generated-ros-distro.inc . These assignments are then manually overridden in conf/ros-distro/include/<ROS_DISTRO>/ros-distro.inc as the mappings are determined. This make possible rapid iteration because superflore need not be rerun until rosdep/*.yaml are updated with all of the new mappings. - Drop using the OpenEmbedded Layer Index to guess the mapping of an unresolved platform package. It would often guess wrong, requiring a rerun of superflore. This change means that there is no longer a dependency on "bs4" and that yoctoRecipe.rosdep_cache is now only used to generate rosdep-resolved.yaml . - Also, rename generate_rosdistro_conf() to generate_ros_distro_inc() so that it corresponds to the name of the file it generates. - This commit resolves issue ros-infrastructure#223. Signed-off-by: Martin Jansa <[email protected]>
- Use ${ROS_UNRESOLVED_PLATFORM_PKG_<PLATFORM_PKG>} as the mapped value when <PLATFORM_PKG> isn't resolved by entries in rosdep/*.yaml and add assignments of the form ROS_UNRESOLVED_PLATFORM_PKG_<PLATFORM_PKG> = "UNRESOLVED-<PLATFORM_PKG>" to conf/ros-distro/include/<ROS_DISTRO>/generated-ros-distro.inc . These assignments are then manually overridden in conf/ros-distro/include/<ROS_DISTRO>/ros-distro.inc as the mappings are determined. This make possible rapid iteration because superflore need not be rerun until rosdep/*.yaml are updated with all of the new mappings. - Drop using the OpenEmbedded Layer Index to guess the mapping of an unresolved platform package. It would often guess wrong, requiring a rerun of superflore. This change means that there is no longer a dependency on "bs4" and that yoctoRecipe.rosdep_cache is now only used to generate rosdep-resolved.yaml . - Also, rename generate_rosdistro_conf() to generate_ros_distro_inc() so that it corresponds to the name of the file it generates. - This commit resolves issue #223. Signed-off-by: Martin Jansa <[email protected]>
Fixed by #232 |
…nfrastructure#232) - Use ${ROS_UNRESOLVED_PLATFORM_PKG_<PLATFORM_PKG>} as the mapped value when <PLATFORM_PKG> isn't resolved by entries in rosdep/*.yaml and add assignments of the form ROS_UNRESOLVED_PLATFORM_PKG_<PLATFORM_PKG> = "UNRESOLVED-<PLATFORM_PKG>" to conf/ros-distro/include/<ROS_DISTRO>/generated-ros-distro.inc . These assignments are then manually overridden in conf/ros-distro/include/<ROS_DISTRO>/ros-distro.inc as the mappings are determined. This make possible rapid iteration because superflore need not be rerun until rosdep/*.yaml are updated with all of the new mappings. - Drop using the OpenEmbedded Layer Index to guess the mapping of an unresolved platform package. It would often guess wrong, requiring a rerun of superflore. This change means that there is no longer a dependency on "bs4" and that yoctoRecipe.rosdep_cache is now only used to generate rosdep-resolved.yaml . - Also, rename generate_rosdistro_conf() to generate_ros_distro_inc() so that it corresponds to the name of the file it generates. - This commit resolves issue ros-infrastructure#223. Signed-off-by: Martin Jansa <[email protected]>
Change how platform packages without a mapping in
rosdep/*.yaml
are handled for OpenEmbedded so that it's possible to specify all of the mappings that bitbake requires in order to parse the metadata for a particular recipe without having to rerun superflore multiple times.The text was updated successfully, but these errors were encountered: