| Age | Commit message (Collapse) | Author |
|---|
|
Modify toolchain-scripts-mingw32.bbclass to add a check in
environment-setup script which removes trailing slash in
path of SDKROOT.
This is needed to avoid multiple adjacent slashes in paths
which are produced by appending to SDKROOT.
In reference to https://learn.microsoft.com/en-us/windows/win32/fileio/naming-a-file?redirectedfrom=MSDN
naming convention used for paths and disk drives in windows
should use a single backslash. Even though in some cases windows
ignores double slashes in paths and it might work but it isn't
documented as a right naming convention and does fail in some
cases eg. dir command cannot interpret double slashes and fails.
For example if my SDK is located in D: drive, the environment
setup scripts sets "SDKROOT=D:\" and hence SDKTARGETSYSROOT
gets set as "SDKTARGETSYSROOT=D:\\sysroots\armv8a-oe-linux"
The introduced check removes additional slash in SDKROOT to
set it as "SDKROOT=D:" so all other variables using SDKROOT
get set without additional slash.
Signed-off-by: Muhammad Hamza <muhammad_hamza@mentor.com>
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
|
|
This converts the layer to the new override syntax. This was done using
<oe-core>/scripts/contrib/convert-overrides.py <this-layer>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
The command to properly set the exit code at the end of the toolchain
environment was using the correct flag delimiter '/', but the code to
coerce all the unix-style paths to windows paths was incorrectly
changing this to a '\'. This worked find in wines cmd, but on an actual
Windows host, this caused cmd to wait indefinitely. Fix this by
appending the command after the path separators are coerced.
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
|
|
The "set" command in Windows has some unfortunate behaviors that can
frequently make it look like the toolchain script had an error. This
makes automated testing of the SDK more difficult, so add a line to the
environment setup script that ensures the script exits with success.
[YOCTO #13020]
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
|
|
Updates the variables configured by the toolchain script to match the
oe-core class. This combines the changes from:
0b5f1b0430 ("toolchain-scripts: put TARGET_ARCH and TARGET_OS into environment")
47160a8c51 ("cmake: fix linking in multilib SDKs")
668f56bb24 ("toolchain-scripts: drop PYTHONHOME")
81f126f4a8 ("toolchain-scripts.bbclass: Use PYTHONPATH instead of PYTHONHOME")
[YOCTO #13020]
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
|
|
The environment script generatation is updated to match YP 2.0 version.
In addition, there was an error in the way the EXTRAPATH component was being
generated.
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
|
|
When using standard paths, the user may end up exceeding the path length to
some toolchain helper libraries (DLLs) and binaries.
By switching to using the "short path", we can avoid this in many more cases.
If the user does exceed the path length, their only option will be to move
the SDK lower in their directory tree.
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
|
|
Since the environment .sh files can't be used on a normal windows machine,
change to providing .bat files instead. The same mechanisms normally used
can be used on the Windows command line. i.e.
Unix way:
$ source environment-setup-armv5te-wrs-linux-gnueabi.sh
$ $CC hello.c
Win32 way:
C:\Users\mhatle\win-sdk>environment-setup-armv5te-wrs-linux-gnueabi.bat
C:\Users\mhatle\win-sdk>%CC% hello.c
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
|
Muhammad Hamza
Richard Purdie
Joshua Watt
Mark Hatle