This is the mail archive of the cygwin-apps@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: mknetrel for president


On Mon, Jul 08, 2002 at 12:59:38PM -0400, Nicholas Wourms wrote:
>>   mkdir build
>>   cd build
>>   /src/configure --target=i686-pc-cygwin --host=i686-pc-cygwin 
>>   --build=i686-pc-linux --prefix=/wherever
>>   make
>>   make install
>>
>You have left out some crucial steps.  What about the headers for 
>cygwin?

Extract them from a net release.  Put them in

/whereever/i686-pc-cygwin/include

>the libraries?

Extract them from a net release.  Put them in

/whereever/i686-pc-cygwin/lib

(both of the above are what I do since that means you're using the
same libraries and headers as cygwin users)

>the binutils?

Build a compiler with the above steps.  Then build binutils with
the same steps.

>Getting all that stuff together is, as I mentioned, a PITA.

So, build everything natively on cygwin.

>Building a combined source-tree for binutils/gcc is equally as
>annoying.

cd /src
cvs -d pserver:anoncvs@sources.redhat.com:/cvs/uberbaum co .

However, for cygwin work, I don't actually put everything in one
directory.  There is no real reason to do so.  Just create a binutils
directory and a gcc directory.  Then you can build both independently of
the other from the net release sources.  That's what I do.  I use the
above sequence of commands to build the cross-binutils and cross-gcc.

It's not like the compiler has to be constantly rebuilt either.  Once
you have something that works, you should be pretty much done unless you
notice a new severe bug report with the old binutils or gcc or
something.

>A script which allows one to build the package and the packaging
>environment would be most optimal.  I like your other suggestion to
>make this functionality a separate script which mknetrel can hook if
>the option to build a cross environment is passed.

No, mknetrel will never have a "hook" for building cross tools.  It
is not part of its goal.

If someone wants to contribute YA cross building script then that's
fine.  I don't have one and I don't really see that it is a strong goal
for building cygwin packages.

I built a linux cross build environment.  I use it for my packages.  I
am not in any suggesting that everyone has to do so.  mknetrel should
work fine on cygwin.  If it doesn't, send patches.

cgf


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]