On Wed, Jun 25, 2014 at 1:37 AM, Paolo Bonzini <[email protected]> wrote: > This series supersedes "[PATCH] Look for BuildEnv under EDK_TOOLS_PATH" > and "[PATCH] Check that WORKSPACE points to the top of the edk2 checkout". > > The patches make it possible to separately package tools in /usr > and use them compile EDK2.
How are you envisioning the packaging to work? I think that installing all the edk2 BaseTools executables in /usr/bin would be silly. I have two ideas: 1. /usr/bin/edk2-build would be a script that would add /usr/lib/edk2-buildtools/bin to the PATH and run /usr/lib/edk2-buildtools/bin/build 2. Same as 1, except use 'edk2' for the command name, and 'build' as the first parameter. (Ie, use sub-commands like svn/git) I also think it might be convenient if the templates in /usr/lib/edk2-buildtools/Conf were used for Conf files if $WORKSPACE/Conf is empty. -Jordan > The second patch ensures that common > mistakes are detected and explained to the user. > > Paolo > > Paolo Bonzini (2): > edksetup.sh: Look for BuildEnv under EDK_TOOLS_PATH > edksetup.sh: Ensure that WORKSPACE points to the top of an edk2 checkout > > edksetup.sh | 51 ++++++++++++++++++++++++++++++++++++++++++++++++--- > 1 file changed, 48 insertions(+), 3 deletions(-) > > -- > 1.9.3 > ------------------------------------------------------------------------------ Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft _______________________________________________ edk2-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/edk2-devel
