#2605 closed defect (fixed)
RSB does not handle waf --destdir connectly with MSYS2
Reported by: | Chris Johns | Owned by: | Chris Johns |
---|---|---|---|
Priority: | high | Milestone: | 4.11 |
Component: | tool/rsb | Version: | 4.11 |
Severity: | critical | Keywords: | |
Cc: | Blocked By: | ||
Blocking: |
Description
Change History (3)
comment:1 Changed on 02/22/16 at 06:05:58 by Chris Johns
comment:2 Changed on 02/22/16 at 06:46:23 by Chris Johns <chrisj@…>
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:3 Changed on 02/22/16 at 06:46:52 by Chris Johns <chrisj@…>
Note: See
TracTickets for help on using
tickets.
The RTEMS tools do not get installed correctly.
A configure script appends the POSIX version of the --prefix path to DESTDIR when using 'make DESTDIR=/C/destdir install'. This means if a prefix is '/C/prefix' is used with a DESTDIR of '/C/destdir' the resultant path is '/C/destdir/C/prefix. Note the double '/C/'.
With the same paths waf results in '/C/destdir/prefix' which is correct because there is no drive annotation you can use, both paths are on the same drive. The RSB does not handle this path so it copies an empty tree to the final install path
The issue is a weird mix of shell configures scripts at the POSIX level building native Windows programs and waf which is using Windows paths.
There is no clear solution and so the config file for the waf build needs to handle this special case.