* NightStrike wrote on Wed, Mar 19, 2008 at 07:02:17PM CET:
> On 3/11/08, Bob Friesenhahn <[EMAIL PROTECTED]> wrote:
> > On Tue, 11 Mar 2008, NightStrike wrote:
> > >
> > > I had intended to do everything with non-recursive make, but as you
> > > pointed out once, non-recursive is also considered h
Hi,
On Wed, Mar 19, 2008 at 03:55:55PM -0400, NightStrike wrote:
> > mingw-w64/crt
> > mingw-w64/doc
> > mingw-w64/hdr
...
> So I guess the choices boil down to:
>
> 1) Change the directory structure
> 2) Recursive make to a small degree
>
> Is that about right?
actually, I recommend recursive
On 3/19/08, Stepan Kasal <[EMAIL PROTECTED]> wrote:
> Hello,
>
> On Wed, Mar 19, 2008 at 03:13:06PM -0400, NightStrike wrote:
> > On 3/19/08, Stepan Kasal <[EMAIL PROTECTED]> wrote:
> > > BTW: Why do you insist on the layout described above? I would have
> > > one top-level directory and make "doc
Hello,
On Wed, Mar 19, 2008 at 03:13:06PM -0400, NightStrike wrote:
> On 3/19/08, Stepan Kasal <[EMAIL PROTECTED]> wrote:
> > BTW: Why do you insist on the layout described above? I would have
> > one top-level directory and make "doc" and "headers" (or perhaps
> > "hdr") subdirs.
>
> The mingw-
On 3/19/08, Stepan Kasal <[EMAIL PROTECTED]> wrote:
> BTW: Why do you insist on the layout described above? I would have
> one top-level directory and make "doc" and "headers" (or perhaps
> "hdr") subdirs.
The mingw-w64-headers directory contains headers that are required to
use the resulting gcc
Good afternon Della,
On Wed, Mar 19, 2008 at 02:02:17PM -0400, NightStrike wrote:
> > On Tue, 11 Mar 2008, NightStrike wrote:
> > > I had intended to do everything with non-recursive make, but as [Ralf]
> > > pointed out once, non-recursive is also considered harmful.
[thread:]
> http://lists.gnu.
On 3/11/08, Bob Friesenhahn <[EMAIL PROTECTED]> wrote:
> On Tue, 11 Mar 2008, NightStrike wrote:
> >
> > I think I understand what you mean. Create a recursive build tree
> > that allows starting from any point. I would then perhaps put this
> > also in the trunk/Makefile.am:
> >
> > EXTRA_DIST=m
On 3/11/08, Bob Friesenhahn <[EMAIL PROTECTED]> wrote:
> On Tue, 11 Mar 2008, NightStrike wrote:
> >
> > I think I understand what you mean. Create a recursive build tree
> > that allows starting from any point. I would then perhaps put this
> > also in the trunk/Makefile.am:
> >
> > EXTRA_DIST=m
On Tue, 11 Mar 2008, NightStrike wrote:
I think I understand what you mean. Create a recursive build tree
that allows starting from any point. I would then perhaps put this
also in the trunk/Makefile.am:
EXTRA_DIST=mingw-w64-headers mingw-w64-doc
So that from the trunk directory, I could run
On Tue, Mar 11, 2008 at 5:41 PM, Ralf Wildenhues <[EMAIL PROTECTED]> wrote:
> * NightStrike wrote on Mon, Mar 10, 2008 at 03:42:52PM CET:
>
> > Our project is laid out like this:
> >
> > /trunk/
> > /trunk/mingw-w64-crt/
> > /trunk/mingw-w64-doc/
> > /trunk/mingw-w64-headers/
>
>
> > What is t
* NightStrike wrote on Mon, Mar 10, 2008 at 03:42:52PM CET:
> Our project is laid out like this:
>
> /trunk/
> /trunk/mingw-w64-crt/
> /trunk/mingw-w64-doc/
> /trunk/mingw-w64-headers/
> What is the best way to handle this situation to remove the need to
> manually tar up the trunk?
Move the (to
Project page: http://sourceforge.net/projects/mingw-w64
Our project is laid out like this:
/trunk/
/trunk/mingw-w64-crt/
/trunk/mingw-w64-doc/
/trunk/mingw-w64-headers/
In the *-crt directory is where the build system resides, including
any headers required to *build* the crt. In the *headers d
12 matches
Mail list logo
