Re: problem with latest GNUstep (in CVS) on windows?

[Lloyd Dupont]

Now I am sure that... mh... that I have a different kind of error....

I destroyed all binaries and built directories.
I'm using msys1.0, gcc 3.4.2, GNUstep from today's CVS and the following 
un-updated dependency:
== dependencies ===
ffcall-1.10
libintl-0.11.5-2.bin.zip
libiconv-1.8.1-bin.zip
zlib-1.2.2-bin.zip
jpeg-6b-4-bin.zip
tiff-3.7.2-bin.zip
libpng-1.2.8-bin.zip
===============
I build everything as advised there:
http://wwwmain.gnustep.org/resources/documentation/User/GNUstep/README.MinGW

then I try to build my simple (previously running) program.
And....
mmh.... I have.... a different error....
====
Uncaught exception NSInternalInconsistencyException, reason: 
NSApplication.m:271  Assertion failed in initialize_gnustep_backend.  Unable 
to find backend back
====

hu, hu....
where is this backend?

apparently it should be in some directories pointed to by "GSBackend"
if I perform a search in the Tool directory and I find:
.\Library\Bundles\libgnustep-back-010.bundle.
that could be the one.
How do I put it into GSBackend variable now?


Thanks for paying attention ;-)
And for any future potential help!


Regards,
Lloyd

----- Original Message ----- 
From: "Richard Frith-Macdonald" <richard@brainstorm.co.uk>
To: "Lloyd Dupont" <lloyd@nova-mind.com>
Sent: Wednesday, November 30, 2005 4:14 PM
Subject: Re: problem with latest GNUstep (in CVS) on windows?


> On 30 Nov 2005, at 04:55, Lloyd Dupont wrote:
>
> > it's 2005/11/30 14:47 +0010 (Brisbane Time)
> > I just upgraded my GNUstep code from CVS.
> > Compile it fine...
> >
> > And now I'm trying to run these simple lines of code:
> > main()
> > {
> >    NSAutoreleasePool * pool = [[NSAutoreleasePool alloc] init];
> >    [NSApplication sharedApplication];
> >    // ... would like to be continued ...
> >
> > The 4th one ([NSApplication sharedApplication]) throw an exception:
> > NSInvalidArgumentException, reason: NSRunLoop - unknown event type
>
> Do you still have your application using an old version of the gui/ 
> backend?
> I think the most likely problem is using incompatible versions of the 
> code ...though that's only a guess.