summaryrefslogtreecommitdiff
path: root/x11/fltk
AgeCommit message (Collapse)AuthorFilesLines
2005-03-19Originally fltk used different file names for the man pages depending onben8-433/+475
the platform. I followed the documentation that is now in pkgsrc.txt and put the default names in PLIST, and the NetBSD names in PLIST.NetBSD. The PLIST handling does not actually work this way, and it will be cleaner to use the same file names for man pages regardless of platform.
2005-02-24update to 1.1.6drochner2-6/+6
changes: - Documentation updates (STR #552, STR #608) - Added the 2.0 Fl_Widget::copy_label() method to allow FLTK 1.x applications to have their label strings managed by FLTK (STR #630) - Added Fl::delete_widget() method to safely delete widgets in callback methods (STR #629) +bugfixes
2005-02-23Add RMD160 checksums to the SHA1 ones.wiz1-1/+2
2004-10-21Patches no longer neededadam2-54/+0
2004-10-21Changes 1.1.5rc1:adam9-115/+111
- Documentation updates (STR #186, STR #245, STR #250, STR #277, STR #281, STR #328, STR #338) - fl_scroll() did not handle scrolling from off-screen on WIN32 (STR #315) - Fl_File_Chooser did not allow manual entry of a drive letter (STR #339) - Fl_Menu now uses the boxtype to redraw the menu background (STR #204) - Fl_Scroll now shows the background image when a framed box type is used and the Fl_Scroll is a direct decendent of a window (STR #205) - Added a new_directory_tooltip string pointer to allow localization of the file chooser's new directory button (STR #340) - Added Fl_Menu_::find_item() method (STR #316) - The Fl_Widget copy operator definitions were not conditionally compiled properly (STR #329) - FLUID's Layout functionality did not move child widgets when laying out group widgets (STR #319) - FLUID's Layout->Center In Group functionality did not properly handle widgets that were children of a Fl_Window widget (STR #318) - The Fl_Text_Display destructor did not remove the predelete callback associated with the current buffer (STR #332) - Fixed several bugs in the MacOS X Fl::add_fd() handling (STR #333, STR #337)
2004-10-03Libtool fix for PR pkg/26633, and other issues. Update libtool to 1.5.10tv2-3/+4
in the process. (More information on tech-pkg.) Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and installing .la files. Bump PKGREVISION (only) of all packages depending directly on the above via a buildlink3 include.
2004-09-22Mechanical changes to package PLISTs to make use of LIBTOOLIZE_PLIST.jlam1-17/+1
All library names listed by *.la files no longer need to be listed in the PLIST, e.g., instead of: lib/libfoo.a lib/libfoo.la lib/libfoo.so lib/libfoo.so.0 lib/libfoo.so.0.1 one simply needs: lib/libfoo.la and bsd.pkg.mk will automatically ensure that the additional library names are listed in the installed package +CONTENTS file. Also make LIBTOOLIZE_PLIST default to "yes".
2004-06-27fix @dirrm in PLIST:grant2-4/+4
share/doc/html/fltk -> dirrm share/doc/fltk bump PKGREVISION.
2004-05-23Change PLIST.common location of HTML documentation. Somehow this gotben1-162/+162
missed while I was addressing PR#25652.
2004-05-21Address FLTK issues mentioned in PR#25652. Changes:ben3-12/+9
* link libjpeg and libpng to fluid * install documentation to doc instead of doc/html * bump PKGREVISION
2004-05-05No longer used.snj1-23/+0
2004-05-05Add include/Fl/* to BUILDLINK_FILES. Needed to get palmosemulator building.snj1-1/+2
2004-04-17Correct PLIST for non-NetBSD platforms.ben4-432/+438
2004-04-13Update x11/fltk to 1.1.5rc1 and s/USE_X11BASE/USE_X11/.xtraeme4-11/+11
Changes: CHANGES IN FLTK 1.1.5rc1 - Documentation updates (STR #186, STR #245, STR #250, STR #277, STR #281, STR #328, STR #338) - fl_scroll() did not handle scrolling from off-screen on WIN32 (STR #315) - Fl_File_Chooser did not allow manual entry of a drive letter (STR #339) - Fl_Menu now uses the boxtype to redraw the menu background (STR #204) - Fl_Scroll now shows the background image when a framed box type is used and the Fl_Scroll is a direct decendent of a window (STR #205) - Added a new_directory_tooltip string pointer to allow localization of the file chooser's new directory button (STR #340) - Added Fl_Menu_::find_item() method (STR #316) - The Fl_Widget copy operator definitions were not conditionally compiled properly (STR #329) - FLUID's Layout functionality did not move child widgets when laying out group widgets (STR #319) - FLUID's Layout->Center In Group functionality did not properly handle widgets that were children of a Fl_Window widget (STR #318) - The Fl_Text_Display destructor did not remove the predelete callback associated with the current buffer (STR #332) - Fixed several bugs in the MacOS X Fl::add_fd() handling (STR #333, STR #337) - The Fl_Text_Display widget did not display selections set by the application (STR #322) - FLUID crashed if you did layout with a window widget (STR #317) - Fl_Scroll::clear() didn't remove the child widget from the Fl_Scroll widget (STR #327) - Fl_Value_Slider::draw_bg() didn't always apply the clipping rectangle (STR #235) - fl_filename_relative() returned the wrong string if the absolute pathname was equal to the current working directory (STR #224) - Fl_Help_Dialog didn't correctly restore the scroll position when going forward/back in the link history if the file changed (STR #218) And more...
2004-03-18Fix serious bug where BUILDLINK_PACKAGES wasn't being ordered properlyjlam1-3/+2
by moving the inclusion of buildlink3.mk files outside of the protected region. This bug would be seen by users that have set PREFER_PKGSRC or PREFER_NATIVE to non-default values. BUILDLINK_PACKAGES should be ordered so that for any package in the list, that package doesn't depend on any packages to the left of it in the list. This ordering property is used to check for builtin packages in the correct order. The problem was that including a buildlink3.mk file for <pkg> correctly ensured that <pkg> was removed from BUILDLINK_PACKAGES and appended to the end. However, since the inclusion of any other buildlink3.mk files within that buildlink3.mk was in a region that was protected against multiple inclusion, those dependencies weren't also moved to the end of BUILDLINK_PACKAGES.
2004-03-05Reorder location and setting of BUILDLINK_PACKAGES to match templatejlam1-5/+8
buildlink3.mk file in revision 1.101 of bsd.buildlink3.mk.
2004-02-18bl3ifyjlam2-7/+26
2004-02-18Update from FLTK 1.0.11 to FLTK 1.1.4.ben13-358/+424
2004-02-08PKGLIBTOOL and PKGSHLIBTOOL are no more.jlam1-2/+2
2004-02-02These packages need a C++ compiler.jlam1-2/+2
2004-01-20Move WRKSRC definition away from the first paragraph in a Makefile.agc1-2/+2
2003-12-01Force the use of a C++ compiler to compile C++ source files in a more cleanben4-26/+38
manner, from feedback in PR 23252.
2003-11-30As pointed out by jlam:jschauma1-2/+2
bump PKGREVISION on packages depending on graphics/glu due to latest shlib changes there.
2003-10-30s/USE_GMAKE/USE_GNU_TOOLS+=make/grant1-2/+2
2003-10-30define USE_GCC_SHLIB.grant1-3/+4
sort USE_* lines.
2003-10-30Force the use of a C++ compiler to compile C++ source files. From anagc2-4/+4
analysis of the problem by Ben Collver in PR 23252.
2003-07-17s/netbsd.org/NetBSD.org/grant1-2/+2
2003-03-12More updates from Mesa:jschauma1-2/+3
As with the Makefiles, only include Mesa's buildlink when necessary, otherwise include MesaLib's and/or glu's buildlink.
2003-03-09Bump PKGREVISION due to upgrade of Mesa and friends.jschauma1-3/+4
Only include Mesa/buildlink2.mk if the package requires all three of MesaLib, glu and glut - else only include the necessary buildlink2s.
2003-02-28Subdirectory at Sourceforge is fltk, not FLTK.jmmv1-2/+2
2003-02-17convert to use test target from bsd.pkg.mkdillo1-5/+2
addresses PR pkg/19416
2002-11-25Bump PKGREVISION to on x11/fltk to 1: link the dependent librariesjlam3-13/+14
directly into libfltk.{la,so} so that we don't need to guess at which additional libraries will be needed to link into a program when linking against libfltk. Suggested in private email by Dave Sainty <dave at dtsp dot co dot nz>.
2002-11-25FLTK headers should also be found under <include/Fl/*>.jlam1-1/+2
2002-10-09Unused.wiz1-36/+0
2002-08-25Merge changes in packages from the buildlink2 branch that havejlam2-5/+25
buildlink2.mk files back into the main trunk. This provides sufficient buildlink2 infrastructure to start merging other packages from the buildlink2 branch that have already been converted to use the buildlink2 framework.
2002-02-15mkdir -> ${MKDIR}skrll1-2/+2
rmdir -> ${RMDIR} rm -> ${RM} (${RM} added to PLIST_SUBST) chmod -> ${CHMOD} chown -> ${CHOWN}
2001-10-31Move pkg/ files into package's toplevel directoryzuntum2-1/+1
2001-10-24I am a triple idiot. The only relevant variable that x11.buildlink.mkjlam1-2/+2
redefines about which buildlink.mk files would care is BUILDLINK_X11_DIR, which points to the location of the X11R6 hierarchy used during building. If x11.buildlink.mk isn't included, then BUILDLINK_X11_DIR defaults to ${X11BASE} (set in bsd.pkg.mk), so its value is always safe to use. Remove the ifdefs surrounding the use of BUILDLINK_X11_DIR in tk/buildlink.mk and revert changes to move x11.buildlink.mk before the other buildlink.mk files.
2001-10-23x11.buildlink.mk needs to be included before any buildlink.mk files thatjlam1-2/+2
use X11_BUILDLINK_MK as a test value. Generally just reordering the inclusions so that x11.buildlink.mk comes before the other buildlink.mk files will make everthing work.
2001-08-29Use x11.buildlink.mk instead of USE_X11. Also convert hard-coded referencesjlam1-1/+2
to ${X11BASE} in the header and library search paths into references to ${LOCALBASE}/share/x11-links. These packages should now be strongly- buildlinked regardless of whether xpkgwedge is installed. Changes well-tested on NetBSD-1.5X/i386 with and without xpkgwedge and lightly-tested on NetBSD-1.5.1/alpha without xpkgwedge.
2001-07-27Add dir_DEFAULT setting used by EVAL_PREFIX logic to set the defaultjlam1-1/+2
installation directory in case the package isn't installed.
2001-07-20Mechanical changes to buildlink.mk files to use EVAL_PREFIX to setjlam1-2/+2
BUILDLINK_PREFIX.<pkgname>. This allows buildlink to find X11BASE packages regardless of whether they were installed before or after xpkgwedge was installed. Idea by Alistair Crooks <agc@pkgsrc.org>.
2001-07-01Move inclusion of bsd.buildlink.mk to start of file.jlam1-3/+3
2001-06-23Generalize how the dependency pattern may be specified. Instead of justjlam1-4/+5
FOO_REQD=1.0 being converted to foo>=1.0, one can now directly specify the dependency pattern as FOO_DEPENDS=foo>=1.0. This allows things like JPEG_DEPENDS=jpeg-6b, or fancier expressions like for postgresql-lib. Change existing FOO_REQD definitions in Makefiles to FOO_DEPENDS.
2001-06-20Mark as USE_BUILDLINK_ONLY.jlam1-8/+8
2001-06-17USE_MESA is defined automatically by the buildlink.mk file.jlam1-2/+1
2001-06-11CPPFLAGS is now passed to MAKE_ENV and CONFIGURE_ENV by bsd.pkg.mk, sojlam1-2/+1
adapt by moving CPPFLAGS settings to top-level, and removing explicit inclusion of CPPFLAGS into MAKE_ENV and CONFIGURE_ENV.
2001-06-11The buildlink include and lib directories are added to CFLAGS, CPPFLAGS,jlam1-4/+1
CXXFLAGS, and LDFLAGS by the buildlink.mk files so remove the extra definitions to add them from the package Makefiles. As advised by the bsd.buildlink.mk file, also ensure that the buildlink.mk files are included prior to defining any package-specific CFLAGS/LDFLAGS to ensure that the buildlink directories are at the head of the compiler search paths.
2001-06-11Use bsd.buildlink.mk instead of duplicating code all over the place.jlam1-48/+11
2001-06-10Use cookies (.*_done) to determine whether headers and libs have beenjlam1-5/+14
linked from a particular package, and add a pre-configure target to the buildlink.mk file to more painlessly use buildlink.mk files. A ${BUILDLINK_TARGETS} variable still exists in case a package _must_ define NO_CONFIGURE.
generated by cgit v1.2.3 (git 2.39.1) at 2024-06-06 15:11:05 +0000