The conflict between libFoundation and gnustep-base is akin to having
(say) two libc libraries on the same system. They provide the same
functionality and conflict in filename space, so they cannot both be
supported on the same system without jumping through some hoops.
gnustep-make was originally designed through library-combo to support
different foundation libraries, primarily as a concession to the
libFoundation guys, but this capability was never truly utilized by
developers. Today these foundation libraries are not truly
interchangeable, the gnustep-gui and other libraries are coupled
tightly with gnustep-base and do not work with libFoundation or
Apple's. Therefore, applications that use libFoundation are not going
to use any of the GNUstep functionality above the foundation library.
So my suggestion is to handle libFoundation as though it was a
separate library outside of the GNUstep environment, to prevent
conflict with the GNUstep headers, have it be installed in its own
subdirectory.
/usr/include/libFoundation
and applications which require libFoundation just need to insert an
include flag during compilation so that its header are found in front
of GNUstep's. These applications like opengroupware are free to use
gnustep-make unchanged for their build process, they just need to add
an additional line in their makefile.
cheers
Scott
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
