[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: gnustep-base on msys/mingw: make always regenerates
From: |
Marcel Weiher |
Subject: |
Re: gnustep-base on msys/mingw: make always regenerates |
Date: |
Tue, 22 Oct 2002 00:55:21 +0200 |
On Sunday, October 20, 2002, at 05:50 Uhr, Adam Fedor wrote:
Marcel Weiher wrote:
Hi folks!
I have now found the instructions for building gnustep with
MSYS+MinGW, and things are working much better than before with
cygwin and so forht (Duh!). However, there still are some minor
wrinkles to get out, but nothing really problematic. What *is*
problematic is that make always restarts the build from scratch. Not
too pleasant on Virtual PC...
Any ideas what could be causing the build to re-start from scratch
each time, even if the previus make failed in the final link phase?
One thing I noticed is that it removes and re-copies the headers each
time. Are there dependencies on the build-locations of the headers?
re-copying the headers is a dumb hack. Perhaps this should be
improved. It shouldn't re-compile everything though. Perhaps just 10
or 20 files.
In any case, you could avoid this by compiling from a subdirectory:
cd Source
make
Yes, that helped a bit, thanks. However, for those link-errors, I
still had to go back to the top-level, resulting in (almost?) complete
rebuilds.
Anyway, I have now successfull compiled the gnustep-base, as well as
(sort of) successfully compiled my MPWFoundation (will have to revisit
a couple of places, for example the pthread-based stuff in MPWObject).
Yeah! With NSInvocation now present, even HOM should work.
I will report on details later, but right now the problem is that
although I can compile+link a small test-program, (pretty much
hello-world.m with one class reference), this doesn't run. It exits
with an NSInternalInconsistencyException, reason "Runtime incorrectly
configured to pass argframes". The nice thing is that it at least
behaves identically from a plain DOS prompt, so that was good to see ;-)
There were some problems installing the ffcall library, so my working
guess is that it's related to that. For example, gnustep-base's
autoconf wouldn't autodetect ffcall no matter where I put libs +
headers (or at least so it seemed) so I had to specify this on the
configure command line.
I am also seeing problems with paths that appear similar to what
S.J.Chun reported.
Big thanks for all the help so far,
Marcel
--
Marcel Weiher Metaobject Software Technologies
marcel@metaobject.com www.metaobject.com
Metaprogramming for the Graphic Arts. HOM, IDEAs, MetaAd etc.