This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


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: crosstool-0.36 coming up soonish


This time with the attachments...

On 7/10/05, Paul Schulz <pschulz01@gmail.com> wrote:
> Greetings,
> 
> (My contribution.. see end)
> 
> On 7/10/05, Robert Schwebel <robert@schwebel.de> wrote:
> > On Sat, Jul 09, 2005 at 03:27:10PM -0700, Dan Kegel wrote:
> > > Because I'm trying to become an official gnu project.
> >
> > Ah, ok.
> >
> > > >It would result in a cleaned up top directory; contrary to what we have
> > > >in PTXdist you probably only need one file per config, so it would just
> > > >move the config files into a sub directory.
> > >
> > > Yes, but I ship crosstool with several hundred configs...
> >
> > Well, if you have the SVN repo ready I'll make a prototype
> > in a branch ;) - that's better than discussing without code.
> 
> I was waiting for 0.26 before making any suggestion
> about changing the directory structure, but..
> 
> The attached script (convert-structure)
> puts files into the following directory structure...
>   - ./config (the '.dat' files)
>   - ./bin (shell scripts without demo scrips)
>   - ./examples (current demo scripts)
> 
> The attached patch - crosstool-0.35-paths.patch
> can then be used to adjust the paths in the various
> scripts.
> 
> Comments? Is this useful?
> Regards,
> Paul
>

Attachment: convert-structure
Description: Binary data

Index: crosstool-0.35-ps1/bin/crosstool.sh
===================================================================
--- crosstool-0.35-ps1.orig/bin/crosstool.sh	2005-06-18 16:56:04.000000000 +0930
+++ crosstool-0.35-ps1/bin/crosstool.sh	2005-06-19 15:58:09.000000000 +0930
@@ -17,6 +17,9 @@
 # list at http://sources.redhat.com/ml/crossgcc, or contact the
 # authors, but do your homework first.  As Bill says, "THINK!"
 #
+# Modified to use subdirectory structure for scripts.
+# Paul Schulz <paul@mawsonlakes.org>
+#
 # Meant to be invoked from another shell script.
 # Usage: nine environment variables must be set, namely:
 test -z "${PREFIX}"           && abort "Please set PREFIX to where you want the toolchain installed."
@@ -566,7 +569,7 @@
 # Relies on $EXEEXT being set to .exe if the compilers run on cygwin
 export EXEEXT
 cd $PREFIX
-sh $TOP_DIR/masq.sh
+sh $TOP_DIR/bin/masq.sh
 
 # Build little program that lets user move resulting toolchain to different prefix
 cd $TOP_DIR
Index: crosstool-0.35-ps1/bin/all.sh
===================================================================
--- crosstool-0.35-ps1.orig/bin/all.sh	2005-06-18 16:56:04.000000000 +0930
+++ crosstool-0.35-ps1/bin/all.sh	2005-06-18 17:05:26.000000000 +0930
@@ -10,6 +10,9 @@
 # list at http://sources.redhat.com/ml/crossgcc, but do your homework first.
 # As Bill Gatliff says, "THINK!"
 #
+# Modified to use subdirectory structure for scripts.
+# Paul Schulz <paul@mawsonlakes.org>
+#
 # Meant to be invoked from another shell script.
 # Usage: six environment variables must be set, namely:
 test -z "${TARGET}"           && abort "Please set TARGET to the Gnu target identifier (e.g. pentium-linux)"
@@ -107,7 +110,7 @@
    fi
    # Download and patch
    rm -rf $BUILD_DIR; mkdir -p $BUILD_DIR
-   sh getandpatch.sh
+   sh `pwd`/bin/getandpatch.sh
 fi
 
 if test "$opt_no_build" = ""; then
@@ -117,28 +120,28 @@
     mkdir -p $BUILD_DIR
     cd $BUILD_DIR
     if test "${CYGWIN_DIR}" = ""; then
-        sh $TOP_DIR/crosstool.sh
+        sh $TOP_DIR/bin/crosstool.sh
     else
-        sh ${TOP_DIR}/crosstool-cygwin.sh
+        sh ${TOP_DIR}/bin/crosstool-cygwin.sh
     fi
     cd $TOP_DIR
 
-    sh testhello.sh
+    sh $TOP_DIR/bin/testhello.sh
 fi
 if test "$opt_testlinux" = "1"; then
     # Build a Linux kernel to see if we can
-    sh testlinux.sh
+    sh $TOP_DIR/bin/testlinux.sh
 fi
 
 if test "$opt_builduserland" = "1"; then
     # Build /bin/sh and any other non-toolchain things configured in ptx.config
     # Only needed if you can't run the target's normal /bin/sh with the new toolchain
     cd $BUILD_DIR
-    sh $TOP_DIR/ptx.sh
+    sh $TOP_DIR/bin/ptx.sh
 fi
 
 if test "$opt_no_test" = ""; then
     # Beefy test that lasts for hours
     cd $BUILD_DIR
-    sh $TOP_DIR/crosstest.sh 
+    sh $TOP_DIR/bin/crosstest.sh 
 fi
------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com

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