On 2/25/06, Chris Apers <[EMAIL PROTECTED]> wrote:
> Well, I'm using CW 9.3, I have this error with the 68k compiler, works fine
> with teh ARM one
The ARM and 68K compiler/linkers are totally different tools. Outside
of the IDE, you execute completely different code paths for them.
--
For info
Well, I'm using CW 9.3, I have this error with the 68k compiler, works fine
with teh ARM one
- Original Message -
From: "Ben Combee" <[EMAIL PROTECTED]>
To: "Palm Developer Forum"
Sent: Friday, February 24, 2006 11:19 PM
Subject: Re: CW error
On 2/24/06
On 2/24/06, Chris Apers <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have the following error :
>
> Link Error : internal linker error; line: 1289 file: 'Linker.c'
Which version of CodeWarrior for Palm OS? If you're not using V9.3,
you should upgrade. This usually indicates a bug in the linker; I
k
Hi,
I have the following error :
Link Error : internal linker error; line: 1289 file: 'Linker.c'
Any idea ?
Thanks
Chris
--
For information on using the PalmSource Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/support/forums/
Hi,
Does anyone can explain me why this code doesn't compile under CW
http://capers.free.fr/temp/list.h
with the error :
Error : illegal initialization
(point of instantiation: 'Common::ConfigFile::ConfigFile()')
(instantiating: 'Common::List::~List()')
(instantiating: 'Common::List::cl
the data.
Thanks
bye
- Original Message -
From: Lorraine Chin <[EMAIL PROTECTED]>
Date: Tue, 24 Aug 2004 10:41:51 -0400
To: "Palm Developer Forum" <[EMAIL PROTECTED]>
Subject: CW error reading memory on device
>
> Does anyone know why I'm gettin
Does anyone know why I'm getting "error reading memory on device" whenever
I try to set a breakpoint using the CodeWarrior debugger? I'm debugging
over the USB port to a Tungsten T3. I had been working with a T2 that ran
the same application and same CodeWarrior without any problems. I'm usin
On Mon, 7 Jan 2002, Ben Combee wrote:
> > I'm porting a rather large application by PalmOS standards -- it has
> > _thousands_ of methods, and approximately 450 source *.c files.
>
> Are these true C source files or C++ files?
They are true C source files, the C++ compiler is turned off.
> Rig
"Max Campos" <[EMAIL PROTECTED]> wrote in message
news:72774@palm-dev-forum...
>
> I'm porting a rather large application by PalmOS standards -- it has
> _thousands_ of methods, and approximately 450 source *.c files.
Are these true C source files or C++ files?
>
> Well, i've split it into 18 se
I'm porting a rather large application by PalmOS standards -- it has
_thousands_ of methods, and approximately 450 source *.c files.
Well, i've split it into 18 segments, none of which is codewarrior
complaining that is too big, but I get the following error messages:
__RuntimeModule__: Near d
> Yeah, I tried using that. The problem that I come up with is that as soon
> as I switch all of my files to using mypilot.h Invariably one of them
> starts acting like it can't see pilot.h. (It has no idea what a FrmPtr is
> and similar things.) Maybe I don't understand this, but I though that
On Sat, 4 Mar 2000, Matthew D Moss wrote:
>
> The basic answer to this make sure you #include "pilot.h" only once. How?
> Here's one basic method. Create a file named "mypilot.h" which contains the
> following:
>
> #ifndef __PILOT_H__
> #include
> #endif
>
> (I think that's the correct symb
> Oh, I've seen it.
> It seems like this is C++ related because it only showed up for me when I
> had some C++ classes in my project. When I removed 'em and only had C code
> it compiled and linked w/o probs.
> >
> >
> > Error : illegal use of precompiled header
> > Pilot.h line 65#inclu
Oh, I've seen it.
It seems like this is C++ related because it only showed up for me when I
had some C++ classes in my project. When I removed 'em and only had C code
it compiled and linked w/o probs.
Nils Ågren
"Noah J. Ternullo" <[EMAIL PROTECTED]> wrote in message
news:3973@palm-dev-forum...
I'm trying to develop an application for the palm using CW4, C++ and a
little C. I've constructed a couple of classes, each with an
implementation cpp file, and a header h file. I've been desperitly trying
to compile this application for a week now. As near as I can tell my C++
is fine, as is m
15 matches
Mail list logo