Package: colorgcc
Version: 1.3.2.0-10
Severity: normal
Maybe consider adding an argument which contains the path
to gcc/g++ to use instead on relying on the PATH arrangement and
symlinks; this would allow using a single installation of colorgcc
with many toolchains without tweaking them to add symlinks:
colorgcc --gcc=/some/toolchain/bin/gcc options
this would allow easier integration in complex build chains.
This could be done via the simple patch:
--- /usr/bin/colorgcc 2009-03-19 03:36:37.000000000 +0100
+++ /usr/bin/colorgcc2 2009-12-15 16:04:14.000000000 +0100
@@ -226,6 +226,12 @@ $compiler = $compilerPaths{$progName} ||
$compiler = $comp_list[0];
@comp_args = ( @comp_list[1 .. $#comp_list], @ARGV );
+# If compiler is specified via --gcc=.., use it
+if( $ARGV[ 0 ] =~ m/--gcc=(.*)/ ) {
+ $compiler = $1;
+ shift( @ARGV );
+}
+
# Check that we don't reference self
die "$compiler is self-referencing"
if ( -l $compiler and (stat $compiler)[1] == (stat $0)[1] );
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.31-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages colorgcc depends on:
ii perl 5.10.1-8 Larry Wall's Practical Extraction
colorgcc recommends no packages.
colorgcc suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
