On 1/6/05 00:42, in article
1117582976.124298.186480@[EMAIL PROTECTED]
"toby"
<toby@[EMAIL PROTECTED]
> wrote:
> I'd be happy to help.
Thank you. If it's alright, I'll keep your email address on file just in
case! :)
>> The only thing that seems to be missing from the toolset is gdb. Have
you
>> had any success in remote debugging OS X host -> Windows target? Is it
>> simple to do?
>
> I have not done that, as I rarely use symbolic debuggers, but it would
> be an interesting thing to try...
I'm just starting to read the gdb manual, to be honest I wouldn't have a
clue where to start. I'll carry on reading for now... :)
> By the way I recently updated the build-cross script for more recent
> MinGW release files:
>
> GCC_VERSION=3.4.2-20040916-1
> BINUTILS=binutils-2.15.91-20040904-1
> MINGW=mingw-runtime-3.7
> W32API=w32api-3.2
How do you know which versions to use? Are they the same as the 'official'
MinGW download for Windows?
> The gcc configure command now looks like:
>
> "$SRCDIR/$GCC/configure" --with-gcc --with-gnu-ld --with-gnu-as \
> --with-sys-root="$PREFIX/$TARGET" \
> --without-newlib --disable-multilib \
> --target=$TARGET --prefix=$PREFIX \
> --enable-threads --disable-nls --enable-languages=c,c++ \
> --disable-win32-registry --disable-shared
>
Thanks. Out of interest, what difference do the new configure options
make?
Using gcc it's interesting to watch it re****t more warnings and errors
where
Codewarrior let it through without any problems.
We're also investigating Visual Studio (2005 beta 2) and that also spots
more potential problems in our code.
I was always under the impression that Codewarrior was leading the way
wrt.
standards compliance?
--
Steve.
|
