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] |
Christopher Faylor wrote:
You have left out some crucial steps. What about the headers for cygwin? the libraries? the binutils? Getting all that stuff together is, as I mentioned, a PITA. Building a combined source-tree for binutils/gcc is equally as annoying. 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.On Mon, Jul 08, 2002 at 07:51:58AM -0400, Nicholas Wourms wrote:Christopher Faylor wrote:On Mon, Jul 08, 2002 at 03:05:54AM +0200, Jan Nieuwenhuizen wrote:* set of functions for each stage (configure, make, install) etc, and between stages. * each package can override any of these functions with its own. * configure, build, package src and binary package. * rather simple, specific and lightweight. Looking at mknetrel, there are two things that I really miss from my self-centered pov: * setting up the cross building environment.There should be little, if any cross build environment to set up. You either have the cross compilers or you don't.I hate to chime in, but I love Jan's scripts for building a cross-compiler. Let's be frank, building a cross environment is easy, but it is a tedious task somewhat prone to mistakes.mkdir build cd build /src/configure --target=i686-pc-cygwin --host=i686-pc-cygwin --build=i686-pc-linux --prefix=/wherever make make install
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |