You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The first four of those are especially problematic since they replace deprecated keys, and the documentation doesn't note that CRAFT_ARCH_TRIPLET and CRAFT_TARGET_ARCH are deprecated.
It also doesn't include several changes to existing environment variables that we make, including:
Prepending a large number of directories to $PATH (roughly equivalent to exporting PATH=$CRAFT_PART_INSTALL/usr/sbin:$CRAFT_PART_INSTALL/usr/bin:$CRAFT_PART_INSTALL/sbin:$CRAFT_PART_INSTALL/bin:$CRAFT_STAGE/usr/sbin:$CRAFT_STAGE/usr/bin:$CRAFT_STAGE/sbin:$CRAFT_STAGE/bin:$PATH)
Similar changes to CPPFLAGS, CFLAGS, CXXFLAGS
Related changes to LDFLAGS
Similar changes to PKG_CONFIG_PATH
Why it needs to get done
The former group can be frustrating for users who don't know what to do about our deprecation notice, and the latter can cause confusion to users if, for example, an unexpected executable gets run.
The text was updated successfully, but these errors were encountered:
What needs to get done
The Step execution environment documentation is incomplete, missing at least the following:
CRAFT_ARCH_BUILD_ON
CRAFT_ARCH_BUILD_FOR
CRAFT_ARCH_TRIPLET_BUILD_ON
CRAFT_ARCH_TRIPLET_BUILD_FOR
CRAFT_STEP_NAME
The first four of those are especially problematic since they replace deprecated keys, and the documentation doesn't note that
CRAFT_ARCH_TRIPLET
andCRAFT_TARGET_ARCH
are deprecated.It also doesn't include several changes to existing environment variables that we make, including:
$PATH
(roughly equivalent to exportingPATH=$CRAFT_PART_INSTALL/usr/sbin:$CRAFT_PART_INSTALL/usr/bin:$CRAFT_PART_INSTALL/sbin:$CRAFT_PART_INSTALL/bin:$CRAFT_STAGE/usr/sbin:$CRAFT_STAGE/usr/bin:$CRAFT_STAGE/sbin:$CRAFT_STAGE/bin:$PATH
)CPPFLAGS
,CFLAGS
,CXXFLAGS
LDFLAGS
PKG_CONFIG_PATH
Why it needs to get done
The former group can be frustrating for users who don't know what to do about our deprecation notice, and the latter can cause confusion to users if, for example, an unexpected executable gets run.
The text was updated successfully, but these errors were encountered: