Ok, great!
Here are a few more notes:
- It installs using the GNUstep filesystem layout in /opt/local/GNUstep. Using
the fhs layout with macports will not work, because gnustep-make adds the
gnustep library path to DYLD_LIBRARY_PATH, which is /opt/local/lib with the fhs
layout, and if you add
Am 08.11.2011 um 20:04 schrieb Eric Wasylishen:
> Ok, great!
>
> Here are a few more notes:
>
> - It installs using the GNUstep filesystem layout in /opt/local/GNUstep.
> Using the fhs layout with macports will not work, because gnustep-make adds
> the gnustep library path to DYLD_LIBRARY_PA
Hi Eric,
I'm unable to build GNUstep due to no fault of your own: compiling gcc46
fails in the linking phase of libgcc_s.1.dylib. This is on Snow Leopard.
Apparently gcc46 uses its own linker to link this library.
For now, I am giving up. Can some older GCC be used if I am not interested
in objc2
For over a month I have been suggesting a new release of all GNUstep
code components (perhaps including Gorm as well), but got no reply at
all. Many of us have been pretty busy fixing the bugs Julian reported
and there is still plenty to do in this area. Anyway I would like to
start a discussio
Hi,
I think it is a good idea to release gui&back. Things are piling up and
diverging from base, so they are indeed needed. I am feeling some itches
lately though, but they can surely be solved.
The new cairo surface usage is not prefect, but it is quite good, if
some of the performance and
As I remember it, we agreed on GCC 4.0 and later.
On Tuesday, November 8, 2011, Riccardo Mottola wrote:
> Hi,
>
> I think it is a good idea to release gui&back. Things are piling up and
diverging from base, so they are indeed needed. I am feeling some itches
lately though, but they can surely be
