[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: MinGW issue
From: |
Charles Wilson |
Subject: |
Re: MinGW issue |
Date: |
Sat, 09 Oct 2004 21:35:45 -0400 |
User-agent: |
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040616 MultiZilla/1.6.4.0b |
Bob Friesenhahn wrote:
regardless, this code fragment only needs to work under Cygwin and MinGW
so some other means needs to be found to insert a line before the first
line, but it doesn't need to be very portable.
Guys, why not just use a HERE or an echo? Instead of this statement
$run eval "${SED} -e '1iEXPORTS'"' < "$export_symbols" >
"$output_objdir/$output.def"'
Just change it to these two statements using >> instead of > for the
second one.
$run eval "${ECHO} EXPORTS "'> "$output_objdir/$output.def"'
$run eval "${SED} -n -e 'p'"' < "$export_symbols" >>
"$output_objdir/$output.def"'
That should work, right, if the -n option to sed is universal? (there's
one other place where you have to do the same thing).
BTW, I believe I tried albert chin's suggestion, but it didn't work
because I couldn't encode the newline properly or something, given the
wierd $run eval construction.
--
Chuck
- MinGW issue, Bob Friesenhahn, 2004/10/09
- Re: MinGW issue, Bob Friesenhahn, 2004/10/09
- Re: MinGW issue, Bob Friesenhahn, 2004/10/09
- Re: MinGW issue, Brad, 2004/10/09
- Re: MinGW issue, Bob Friesenhahn, 2004/10/09
- Re: MinGW issue, Albert Chin, 2004/10/09
- Re: MinGW issue,
Charles Wilson <=
- Re: MinGW issue, Albert Chin, 2004/10/09
- Re: MinGW issue, Charles Wilson, 2004/10/09
- Re: MinGW issue, Albert Chin, 2004/10/09
- Re: MinGW issue, Charles Wilson, 2004/10/09
- Re: MinGW issue, Albert Chin, 2004/10/09
- Re: MinGW issue, Charles Wilson, 2004/10/10
- Re: MinGW issue, Bob Friesenhahn, 2004/10/11
- Re: MinGW issue, Bob Friesenhahn, 2004/10/09