> Hi Everyone,
>
> I got bored waiting for GNUstep to be ported to FreeBSD,
> so I installed it from source on FreeBSD 7-CURRENT. Anyone
> else wanting to play with Étoilé on FreeBSD should do the
> following:

Me too!  I'd love to have Etoile 0.2 to play around with.

> - Do make depends for the GNUstep ports (gui, back, base).
> This is a nice easy way of getting the dependencies all
> installed without thinking.

Done.  Although, I find it strange that you want to do a
make depends instead of a full make.  -back depends on
both -gui and -base, so the best you can get away with is
not compiling -back.

> - Install the gnustep-make port. This is version 2.0.1,
> which is the latest. Having this installed from ports
> makes subsequent things much, much easier.
>
> - Install GNUstep's version of libobjc (the one in the
> base system won't work).

Really?  Even though gnustep-* requires gcc42, which uses a
different libobjc than the gcc3 in the base system?

I grabbed the libobjc-1.4.0 from GNUstep's website and built
it with gmake/gmake install (while having the environment data
from /usr/local/GNUstep/System/Library/Makefiles/GNUstep.csh
sourced) and it chugged along just fine.  It ended up making
/usr/local/GNUstep/Local/Library/Libraries/libobjc.so and
friends.

> - Install -base, -gui and -back as per the instructions
> on the GNUstep site.

I grabbed -base from GNUstep's SVN and I can't get the first
gmake (or ./configure) to finish because it fails on the FFI
library usage check.  Is there anything special to do when
installing libobjc from GNUstep's site?  The tarball for
GNUstep's libobjc had a README.GNUstep file which said that
GNUstep should automatically recognize the new libobjc and
use it, so my assumption is that I've done everything I need
to do.

I've looked through the config.log output, and the code for
testing FFI fails because it's including the wrong header
path.  It's using -I$(GNUSTEP_SYSTEM_HEADERS) (which does
not contain the objc headers installed by GNUstep's libobjc)
instead of -I$(GNUSTEP_LOCAL_HEADERS).  The result is that
objc-decls.h can't be found, which causes objc-api.h to error
like crazy, which is followed by __objc_msg_forward not
being defined.  Manually compiling the test file
(config/config.forward.m) using -I$(GNUSTEP_LOCAL_HEADERS)
instead of the system headers compiles without a hitch.

So I could hack the configuration process to use the local
headers, but I'm sure that'll just blow up on me in the
future.  What's the correct way to go about fixing this?

Thanks,
Joe


_______________________________________________
Etoile-discuss mailing list
[email protected]
https://mail.gna.org/listinfo/etoile-discuss

Répondre à