Re: [edk2] Projects outside the edk directory structure

2013-02-23 Thread Rod Smith
robbing functionality for those who want to use TianoCore in a more traditional (by TianoCore standards) way. > -Original Message- From: Rod Smith > [mailto:rodsm...@rodsbooks.com] Sent: Friday, February 22, 2013 7:22 > PM To: edk2-devel@lists.sourceforge.net Subject: Re: [edk2

Re: [edk2] Projects outside the edk directory structure

2013-02-23 Thread Mcdaniel, Daryl
first steps to solving the problem. I would like to help you provide a strong argument for change or enhancement of the current tools. Daryl McDaniel -Original Message- From: Rod Smith [mailto:rodsm...@rodsbooks.com] Sent: Friday, February 22, 2013 7:22 PM To: edk2-devel@lists.sourceforg

Re: [edk2] Projects outside the edk directory structure

2013-02-22 Thread Rod Smith
On 02/22/2013 01:22 PM, Mcdaniel, Daryl wrote: > IMHO, the easiest way to build a package or module that is not in the > WORKSPACE tree is to use symbolic links and the standard EDK II build > system. Create a symbolic link to your package in the root of > $WORKSPACE or a link to your module within

Re: [edk2] Projects outside the edk directory structure

2013-02-22 Thread Dan
Joe Vernaci gmail.com> writes: > > > The biggest limitation is the edk build tools.  It makes the assumption that all of the code is inside the 'workspace' directory.  There is no reason why you can't just copy files and create your own make files, but the edk buildtools have some auto gene

Re: [edk2] Projects outside the edk directory structure

2013-02-22 Thread Mcdaniel, Daryl
h [mailto:rodsm...@rodsbooks.com] Sent: Friday, February 22, 2013 8:33 AM To: edk2-devel@lists.sourceforge.net Subject: Re: [edk2] Projects outside the edk directory structure On 02/21/2013 09:48 AM, Dan wrote: > I know its possible to create an application and build it outside of the edk2 > di

Re: [edk2] Projects outside the edk directory structure

2013-02-22 Thread Rod Smith
On 02/21/2013 09:48 AM, Dan wrote: > I know its possible to create an application and build it outside of the edk2 > directory structure, because I have an existing one that works in that way. > However I had to make a number of changes that were supremely hacky and not > at all how I would want to

Re: [edk2] Projects outside the edk directory structure

2013-02-22 Thread Joe Vernaci
The biggest limitation is the edk build tools. It makes the assumption that all of the code is inside the 'workspace' directory. There is no reason why you can't just copy files and create your own make files, but the edk buildtools have some auto generated files and automagically invoke other to

Re: [edk2] Projects outside the edk directory structure

2013-02-22 Thread Dan
Andrew Fish apple.com> writes: > > Dan, > > I don't think there is a clean way to do this. > > I've seen folks run into this. Especially if they have a library/application/driver that can cross > compile for multiple environments. To make it cross compile for EFI you have make it live in an

Re: [edk2] Projects outside the edk directory structure

2013-02-21 Thread Andrew Fish
Dan, I don't think there is a clean way to do this. I've seen folks run into this. Especially if they have a library/application/driver that can cross compile for multiple environments. To make it cross compile for EFI you have make it live in an edk2 tree. Andrew Fish On Feb 21, 2013,

[edk2] Projects outside the edk directory structure

2013-02-21 Thread Dan
I know its possible to create an application and build it outside of the edk2 directory structure, because I have an existing one that works in that way. However I had to make a number of changes that were supremely hacky and not at all how I would want to work on the more complicated applicatio