GNUstep is a set of general-purpose Objective-C libraries based on the
OpenStep standard developed by NeXT (now Apple) Inc. The libraries
consist of everything from foundation classes, such as dictionaries and
arrays, to GUI interface classes such as windows, sliders, buttons, etc.
Please contact the GNUstep maintainers at <discussion@gnustep.org> in
case of questions and help offers.
devel/gnustep-make: Fix "makeinfo --html" output directory
- Bump PORTREVISION for package change
Since texinfo 7, "makeinfo --html foo.texi" outputs to foo_html/ rather than
foo/ which causes build/plist error for some ports.
For example, during
Take x11-toolkits/gnustep-gui for example, it runs "makeinfo --html AppKit.texi"
then checks AppKit/ directory
makeinfo --html AppKit.texi; \
if [ -f AppKit/AppKit_toc.html ]; \
then \
mv AppKit/AppKit.html .; \
mv AppKit/AppKit_*.html .; \
rmdir AppKit/AppKit; \
fi
Obtained
from: https://github.com/gnustep/tools-make/commit/3ff4ee8a053b85d63cd34f645258902bb0dc6f04
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
devel: remove 'Created by' lines
A big Thank You to the original contributors of these ports:
* "Waitman Gobble" <uzimac@da3m0n8t3r.com>
* <jkoshy@FreeBSD.org>
* Aaron Dalton <aaron@FreeBSD.org>
* Aaron Dalton <aaron@daltons.ca>
* Aaron H. K. Diep <ahkdiep@gmail.com>
* Aaron Hurt <ahurt@anbcs.com>
* Abel Chow <abel_chow@yahoo.com>
* Adam McLaurin
* Adam Saponara <as@php.net>
* Adam Weinberger <adamw@FreeBSD.org>
* Ade Lovett <ade@FreeBSD.org>
(Only the first 15 lines of the commit message are shown above )
Update a few GNUstep ports:
* devel/gnustep-make: Update to 2.8.0
* lang/gnustep-base: Update to 1.27.0
* x11-toolkits/gnustep-back: update to 0.28.0
* x11-toolkits/gnustep-gui: update to 0.28.0
Also bump PORTREVISION on dependent ports.
Move Objective-C ports to the v2 GNUstep ABI.
* Bump the LLVM revision used for GNUstep to 7, the minimum to support
the new ABI.
* GNUstep-back does not work with lld, so mark it to use Gold (BFD LD
doesn't seem able to link Objective-C things).
* Turn off some annoying debug logs in GNUstep back, which generate
several messages per second when you move the mouse. These should
never have been enabled in a release build anyway.
* Downgrade Cenon to 4.0.2. This was the last version to actually work
with GNUstep (the later ones use XCode >= 5 .xib files, which GNUstep
can't parse).
* Update gorm to git head. The current release doesn't work with the
new Objective-C ABI, but -head has the patches to fix it.
* Update PikoPixel and add it to the gnustep-app meta-package.
* Update the three core GNUstep packages to the latest release.
* Update gnumail and pantomime to the latest release and fix a linking
error with the new ABI.
* Update GNUstep FTP to the latest version.
Reviewed by: bapt (previous version)
Fix configure options for gnustep-make
We were not setting the flag to select the GNUstep ABI, so were defaulting to
using the GCC-compatible version, which was likely to trigger a lot of subtle
bugs. This was noticed when C++ exceptions thrown through Objective-C stack
frames caused segfaults.
Update GNUstep core libraries.
Update the default Objective-C compiler.
Fix various build failures in GNUstep ports from newer versions of the GNUstep
core libraries and from changes to GNUstep Make.
Update various ports that use GNUstep and bump the portrevision of the ones
that haven't had a new release.
Update GNUstep ports to their latest versions.
Also fix a few bits of generic infrastructure along the way.
Approved by: bapt (mentor)
Differential Revision: https://reviews.freebsd.org/D2961
Convert bsd.gnustep.mk to USES=gnustep
Simplify gnustep ports
Hook into the regular ports framework:
- LIB_DEPENDS for library dependencies
- Use regular USE_LDCONFIG
Reuse USES=objc (automatic)
USE_GNUSTEP is now a macro to set the dependencies and build feature needed.
Accepted arguments: back base build gui
Merge deskutils/preferencepanes into deskutils/systempreferences
Enforce clang 3.4 in USES=c*11*,objc,gnustep as clang 3.3 has some bugs
Requested by: bapt
PR: ports/195122
Differential Revision: https://reviews.freebsd.org/D1181
Exp-run by: self
With hat: portmgr
devel/gnustep-make: Fix and modernize pkg-plist
Running "make check-plist" on gnustep-make results in plist errors:
===> Checking for items in STAGEDIR missing from pkg-plist
Orphaned: GNUstep/System/Library/Makefiles/Master/deb.make
Orphaned: GNUstep/System/Library/Makefiles/deb-equivs-control.template
Orphaned: GNUstep/System/Makefiles
The latest was caused by a keyword typo (I think) and the first two were
just missing. While here, modernize the whole thing. No @exec keywords
are needed -- the post-install takes care of the symlink already.
Update to latest GNUstep core libraries.
Update dependent packages with more recent releases.
Remove old and bit-rotted ones.
Switch to using clang 3.3 and libobjc2 1.7 by default, so modern Objective-C
features work out of the box and remove a lot of configurable options for
sub-optimal (and, often, unsupported / deprecated upstream) configurations.
Take maintainership of GNUstep-related ports.
Several of the ports left in have scary warnings which mean that they are likely
broken in lots of cases. Future commits will fix them.
Approved by: bapt
- Please welcome back Chris Petrik as maintainer of
these ports [1]
- Trim headers
- Remove indefinite article from COMMENT
- Convert tab to space in WWW lines
PR: ports/175415 [1]
Submitted by: Chris Petrik <c.petrik.sosa@gmail.com> [1]
Discussed with: bapt
- Add LDFLAGS to CONFIGURE_ENV and MAKE_ENV (as it was done with LDFLAGS)
- Fix all ports that add {CPP,LD}FLAGS to *_ENV to modify flags instead
PR: 157936
Submitted by: myself
Exp-runs by: pav
Approved by: pav
Update CONFIGURE_ARGS for how we pass CONFIGURE_TARGET to configure script.
Specifically, newer autoconf (> 2.13) has different semantic of the
configure target. In short, one should use --build=CONFIGURE_TARGET
instead of CONFIGURE_TARGET directly. Otherwise, you will get a warning
and the old semantic may be removed in later autoconf releases.
To workaround this issue, many ports hack the CONFIGURE_TARGET variable
so that it contains the ``--build='' prefix.
To solve this issue, under the fact that some ports still have
configure script generated by the old autoconf, we use runtime detection
in the do-configure target so that the proper argument can be used.
Changes to Mk/*:
- Add runtime detection magic in bsd.port.mk
(Only the first 15 lines of the commit message are shown above )
