This works for me as in it starts building and doesn't die immediately with CreateProcess(NULL, better than renaming sh.exe and make.exe :)

Alien-wxWidgets-0.69\inc\My\Build\Win32.pm

sub build_wxwidgets {
    my $self = shift;
    my $old_dir = Cwd::cwd();

    my $uni = $self->awx_unicode ? 'UNICODE=1'   : 'UNICODE=0';
    my $mslu = $self->awx_mslu   ? 'MSLU=1'      : 'MSLU=0';
    my $dbg = $self->awx_debug   ? 'BUILD=debug' : 'BUILD=release';
    my $opt = join ' ', $uni, $mslu, $dbg, 'SHARED=1', 'SHELL=cmd.exe'
+;
[download]

This was a flop , dies with CreateProcess(NULL, probably all that reboot talk ... nonsense :)

Alien-wxWidgets-0.69\inc\My\Build\Win32.pm
sub massage_environment {
    my( $self ) = shift;

    if( $self->notes( 'build_wx' ) ) {
        $ENV{WXWIN} = $ENV{WXDIR} = File::Spec->rel2abs
          ( $self->notes( 'build_data' )->{data}{directory} );
        $ENV{SHELL} = 'cmd.exe' if $Config::Config{sh}=~/cmd/i;
        
        my $mingw_gcc = My::Build::Base->awx_path_search( '*-gcc-*.exe
+' ); # i686-w64-mingw32-gcc-4.6.3.exe
        my $basename = File::Basename::basename($mingw_gcc, '.exe' );
        $basename = "libexec/gcc/$1/$2" if $basename =~ m{^(.+?)-gcc-(
+.+)}is;
        my $new_path = File::Spec->rel2abs(
            File::Spec->catfile(
                File::Basename::dirname($mingw_gcc) ,
                File::Spec->updir, 
                $basename
            )
        );
#~         die "SHELL=$ENV{SHELL}\n$mingw_gcc\n$basename\n$new_path";
        $ENV{PATH}.=';'.$new_path;
## didnt work

    }
}
[download]

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.