Thread: [brlcad-commits] SF.net SVN: brlcad:[61056] brlcad/trunk/HACKING (Page 5)
Open Source Solid Modeling CAD
Brought to you by:
brlcad
From: <br...@us...> - 2014-06-02 03:08:01
|
Revision: 61056 http://sourceforge.net/p/brlcad/code/61056 Author: brlcad Date: 2014-06-02 03:07:57 +0000 (Mon, 02 Jun 2014) Log Message: ----------- keep a note for the next release (not valid syntax) that we need to merge from a specific revision that overlaps date-wise Modified Paths: -------------- brlcad/trunk/HACKING Modified: brlcad/trunk/HACKING =================================================================== --- brlcad/trunk/HACKING 2014-06-02 03:04:58 UTC (rev 61055) +++ brlcad/trunk/HACKING 2014-06-02 03:07:57 UTC (rev 61056) @@ -1320,6 +1320,7 @@ LAST=`grep -E "\--- [0-9]{4}-[0-9]{2}-[0-9]{2}" NEWS | head -n 2 | tail -n 1 | awk '{print $2}'` echo "LAST=$LAST" + LAST=r57446 svn2cl --break-before-msg --include-rev --stdout -r HEAD:{$LAST} > ChangeLog svn commit -m "update log with commits through $LAST" ChangeLog This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <br...@us...> - 2014-06-03 02:16:57
|
Revision: 61074 http://sourceforge.net/p/brlcad/code/61074 Author: brlcad Date: 2014-06-03 02:16:53 +0000 (Tue, 03 Jun 2014) Log Message: ----------- fix dir typo Modified Paths: -------------- brlcad/trunk/HACKING Modified: brlcad/trunk/HACKING =================================================================== --- brlcad/trunk/HACKING 2014-06-02 21:04:44 UTC (rev 61073) +++ brlcad/trunk/HACKING 2014-06-03 02:16:53 UTC (rev 61074) @@ -1310,7 +1310,7 @@ # NON-AUTO: NEWS # NON-AUTO: README # NON-AUTO: include/conf/PATCH - # NON-AUTO: include/conv/MINOR (See VERSION NUMBERS & COMPATIBILITY section.) + # NON-AUTO: include/conf/MINOR (See VERSION NUMBERS & COMPATIBILITY section.) # NON-AUTO: misc/debian/changelog # NON-AUTO: misc/macosx/Resources/ReadMe.rtfd/TXT.rtf # NON-AUTO: misc/macosx/Resources/Welcome.rtfd/TXT.rtf This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <br...@us...> - 2014-06-04 03:05:14
|
Revision: 61093 http://sourceforge.net/p/brlcad/code/61093 Author: brlcad Date: 2014-06-04 03:05:09 +0000 (Wed, 04 Jun 2014) Log Message: ----------- update opensuse link Modified Paths: -------------- brlcad/trunk/HACKING Modified: brlcad/trunk/HACKING =================================================================== --- brlcad/trunk/HACKING 2014-06-03 21:49:55 UTC (rev 61092) +++ brlcad/trunk/HACKING 2014-06-04 03:05:09 UTC (rev 61093) @@ -1441,7 +1441,7 @@ http://t2-project.org/packages/brlcad.html OpenSUSE package maintainer - https://build.opensuse.org/package/users?package=brlcad&project=Education + https://build.opensuse.org/package/users/Education/brlcad FreeBSD ports maintainer http://www.freebsd.org/cgi/cvsweb.cgi/ports/cad/brlcad/ This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <car...@us...> - 2015-07-27 17:02:36
|
Revision: 65685 http://sourceforge.net/p/brlcad/code/65685 Author: carlmoore Date: 2015-07-27 17:02:34 +0000 (Mon, 27 Jul 2015) Log Message: ----------- fix a spelling Modified Paths: -------------- brlcad/trunk/HACKING Modified: brlcad/trunk/HACKING =================================================================== --- brlcad/trunk/HACKING 2015-07-27 17:01:48 UTC (rev 65684) +++ brlcad/trunk/HACKING 2015-07-27 17:02:34 UTC (rev 65685) @@ -995,7 +995,7 @@ 4) Create a SourceForge account, submit at least two patches that demonstrate competency with our coding style, apply flawlessly, and -provide some signficant improvement. +provide some significant improvement. 5) Get to know the other developers. One of them will need to vouch for your commit access. This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <br...@us...> - 2015-08-28 16:36:17
|
Revision: 66099 http://sourceforge.net/p/brlcad/code/66099 Author: brlcad Date: 2015-08-28 16:36:14 +0000 (Fri, 28 Aug 2015) Log Message: ----------- revert back to the more strict wording regarding commit access Modified Paths: -------------- brlcad/trunk/HACKING Modified: brlcad/trunk/HACKING =================================================================== --- brlcad/trunk/HACKING 2015-08-28 13:47:36 UTC (rev 66098) +++ brlcad/trunk/HACKING 2015-08-28 16:36:14 UTC (rev 66099) @@ -981,11 +981,11 @@ developer guidelines and an existing developer with commit access vouches for the new developer. -If you would like to have commit access, there is no need to ask. -Getting involved with the other contributors and making patches will -result in automatic consideration for commit access. That said, the -following steps represent a minimum that needs to occur in order for -commit access to be granted: +If you would like to have commit access, do not ask for it. Getting +involved with the other contributors and making patches will result in +automatic consideration for commit access. That said, the following +steps represent a minimum that needs to occur in order for commit +access to be granted: 1) Read this file completely. This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <sta...@us...> - 2015-11-24 17:20:24
|
Revision: 66675 http://sourceforge.net/p/brlcad/code/66675 Author: starseeker Date: 2015-11-24 17:20:21 +0000 (Tue, 24 Nov 2015) Log Message: ----------- liborle is gone. Modified Paths: -------------- brlcad/trunk/HACKING Modified: brlcad/trunk/HACKING =================================================================== --- brlcad/trunk/HACKING 2015-11-24 16:57:12 UTC (rev 66674) +++ brlcad/trunk/HACKING 2015-11-24 17:20:21 UTC (rev 66675) @@ -288,11 +288,6 @@ wood graining, air, gravel, grass, clouds, fire, and more. Depends on: librt libbn libbu libtcl -liborle: The "old" run-length encoding library that will decode and -encode University of Utah Raster Toolkit format Run-Length Encoded -data. - Depends on nothing - libpkg: The "Package" library is a network communications library that supports multiplexing and demultiplexing synchronous and asynchronous messages across stream connections. The library supports a This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <sta...@us...> - 2015-11-24 22:47:06
|
Revision: 66680 http://sourceforge.net/p/brlcad/code/66680 Author: starseeker Date: 2015-11-24 22:47:03 +0000 (Tue, 24 Nov 2015) Log Message: ----------- Start weeding out the 'depends on tcl' references that are now out of date. More to do here, and should check the docs more generally. Think I held off on this originally because there was some prospect of punting libtcl out of another library or two... Modified Paths: -------------- brlcad/trunk/HACKING Modified: brlcad/trunk/HACKING =================================================================== --- brlcad/trunk/HACKING 2015-11-24 22:45:39 UTC (rev 66679) +++ brlcad/trunk/HACKING 2015-11-24 22:47:03 UTC (rev 66680) @@ -240,18 +240,18 @@ representation library that supports a wide variety of geometric forms. Geometry can be grouped into combinations and regions using CSG boolean operations. - Depends on: libbn libbu libtcl libregex libm (openNURBS) + Depends on: libbn libbu libregex libm (openNURBS) libbu: The BRL-CAD Utility library contains a wide variety of routines for memory allocation, threading, string handling, argument support, linked lists, and more. - Depends on: libtcl (threading) (malloc) + Depends on: (threading) (malloc) libbn: The BRL-CAD Numerics library provides many floating-point math manipulation routines for vector and matrix math, a polynomial equation solver, noise functions, random number generators, complex number support, and more as well. - Depends on: libbu libtcl libm + Depends on: libbu libm libcursor: The cursor library is a lightweight cursor manipulation library similar to curses but with less overhead. This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <br...@us...> - 2016-04-21 04:22:08
|
Revision: 67702 http://sourceforge.net/p/brlcad/code/67702 Author: brlcad Date: 2016-04-21 04:22:04 +0000 (Thu, 21 Apr 2016) Log Message: ----------- beyond experimental developments is no longer true Modified Paths: -------------- brlcad/trunk/HACKING Modified: brlcad/trunk/HACKING =================================================================== --- brlcad/trunk/HACKING 2016-04-21 04:11:35 UTC (rev 67701) +++ brlcad/trunk/HACKING 2016-04-21 04:22:04 UTC (rev 67702) @@ -422,16 +422,17 @@ There is currently no C++ interface to the core BRL-CAD libraries. There are a few tools and enhancements to libraries that are implemented in C++ (the new BREP object type in librt, for example), -but there are presently no C++ bindings available beyond experimental -developments. While C++ as an implementation language of new tools -and new library interfaces is not prohibited, the mixing of C++ -semantics and C++ code (including simple // style comments) in the -existing C files is not allowed. As new interfaces are developed, new -contributors become involved, and C++ code integration becomes more -prevalent, the contributor guidelines will become reinforced with more -details. +and C++ is used underneath quite a number of libraries, but there is +presently no public C++ API in use outside of OpenNURBS. +While C++ as an implementation language of new tools and new library +interfaces is not prohibited, the mixing of C++ semantics and C++ code +(including simple // style comments) in the existing C files is not +allowed. As new interfaces are developed, new contributors become +involved, and C++ code integration becomes more prevalent, the +contributor guidelines will become reinforced with more details. + CODING STYLE & STANDARDS ------------------------ This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <sta...@us...> - 2016-06-15 21:44:09
|
Revision: 68110 http://sourceforge.net/p/brlcad/code/68110 Author: starseeker Date: 2016-06-15 21:44:06 +0000 (Wed, 15 Jun 2016) Log Message: ----------- need the draw command in the first mged test as well. Modified Paths: -------------- brlcad/trunk/HACKING Modified: brlcad/trunk/HACKING =================================================================== --- brlcad/trunk/HACKING 2016-06-15 21:24:58 UTC (rev 68109) +++ brlcad/trunk/HACKING 2016-06-15 21:44:06 UTC (rev 68110) @@ -1283,7 +1283,7 @@ # Manually check rt, mged, and archer. bin/rt # should report usage with correct library versions - bin/mged -c test.g "make sph sph ; rt" # pops up a sphere + bin/mged -c test.g "make sph sph ; draw sph ; rt" # pops up a sphere bin/mged # displays gui, run: opendb test.g ; draw sph ; rt bin/archer # displays gui, run: opendb test.g ; draw sph ; rt This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <sta...@us...> - 2016-06-15 22:01:13
|
Revision: 68112 http://sourceforge.net/p/brlcad/code/68112 Author: starseeker Date: 2016-06-15 22:01:10 +0000 (Wed, 15 Jun 2016) Log Message: ----------- this is a behavior change, need to investigate. Modified Paths: -------------- brlcad/trunk/HACKING Modified: brlcad/trunk/HACKING =================================================================== --- brlcad/trunk/HACKING 2016-06-15 21:46:16 UTC (rev 68111) +++ brlcad/trunk/HACKING 2016-06-15 22:01:10 UTC (rev 68112) @@ -1283,7 +1283,7 @@ # Manually check rt, mged, and archer. bin/rt # should report usage with correct library versions - bin/mged -c test.g "make sph sph ; draw sph ; rt" # pops up a sphere + bin/mged -c test.g "make sph sph ; rt" # pops up a sphere bin/mged # displays gui, run: opendb test.g ; draw sph ; rt bin/archer # displays gui, run: opendb test.g ; draw sph ; rt This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <sta...@us...> - 2016-06-15 22:07:00
|
Revision: 68114 http://sourceforge.net/p/brlcad/code/68114 Author: starseeker Date: 2016-06-15 22:06:57 +0000 (Wed, 15 Jun 2016) Log Message: ----------- Freecode went read-only back on 2014-06-18 Modified Paths: -------------- brlcad/trunk/HACKING Modified: brlcad/trunk/HACKING =================================================================== --- brlcad/trunk/HACKING 2016-06-15 22:02:37 UTC (rev 68113) +++ brlcad/trunk/HACKING 2016-06-15 22:06:57 UTC (rev 68114) @@ -1481,10 +1481,6 @@ BRL-CAD SourceForge NEWS (authorized can submit) https://sourceforge.net/p/brlcad/news/new - Freshmeat (anyone can submit update) - http://freecode.com/projects/BRL-CAD/ - short summary without news details (sentence format) - BRL-CAD on Facebook (authorized can submit) http://www.facebook.com/pages/BRL-CAD/387112738872 short summary without news details (sentence format) This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <br...@us...> - 2016-08-10 00:48:08
|
Revision: 68621 http://sourceforge.net/p/brlcad/code/68621 Author: brlcad Date: 2016-08-10 00:48:05 +0000 (Wed, 10 Aug 2016) Log Message: ----------- frs is no longer broken up into subdirs Modified Paths: -------------- brlcad/trunk/HACKING Modified: brlcad/trunk/HACKING =================================================================== --- brlcad/trunk/HACKING 2016-08-09 21:26:51 UTC (rev 68620) +++ brlcad/trunk/HACKING 2016-08-10 00:48:05 UTC (rev 68621) @@ -1401,32 +1401,32 @@ SFUSERNAME=`ls ~/.subversion/auth/svn.simple/* | xargs -n 1 grep -A4 sourceforge | tail -1` echo "SFUSERNAME=$SFUSERNAME MAJOR=$MAJOR MINOR=$MINOR PATCH=$PATCH" ssh -v $SFUSERNAME,br...@sh... create - ssh -v $SFUSERNAME,br...@sh... mkdir "/home/frs/project/b/br/brlcad/BRL-CAD\ Source/$MAJOR.$MINOR.$PATCH" + ssh -v $SFUSERNAME,br...@sh... mkdir "/home/frs/project/brlcad/BRL-CAD\ Source/$MAJOR.$MINOR.$PATCH" # create binary dirs (as needed) - ssh -v $SFUSERNAME,br...@sh... mkdir "/home/frs/project/b/br/brlcad/BRL-CAD\ Runtime\ Libraries/$MAJOR.$MINOR.$PATCH" - ssh -v $SFUSERNAME,br...@sh... mkdir "/home/frs/project/b/br/brlcad/BRL-CAD\ for\ BSD/$MAJOR.$MINOR.$PATCH" - ssh -v $SFUSERNAME,br...@sh... mkdir "/home/frs/project/b/br/brlcad/BRL-CAD\ for\ Linux/$MAJOR.$MINOR.$PATCH" - ssh -v $SFUSERNAME,br...@sh... mkdir "/home/frs/project/b/br/brlcad/BRL-CAD\ for\ Mac\ OS\ X/$MAJOR.$MINOR.$PATCH" - ssh -v $SFUSERNAME,br...@sh... mkdir "/home/frs/project/b/br/brlcad/BRL-CAD\ for\ Windows/$MAJOR.$MINOR.$PATCH" + ssh -v $SFUSERNAME,br...@sh... mkdir "/home/frs/project/brlcad/BRL-CAD\ Runtime\ Libraries/$MAJOR.$MINOR.$PATCH" + ssh -v $SFUSERNAME,br...@sh... mkdir "/home/frs/project/brlcad/BRL-CAD\ for\ BSD/$MAJOR.$MINOR.$PATCH" + ssh -v $SFUSERNAME,br...@sh... mkdir "/home/frs/project/brlcad/BRL-CAD\ for\ Linux/$MAJOR.$MINOR.$PATCH" + ssh -v $SFUSERNAME,br...@sh... mkdir "/home/frs/project/brlcad/BRL-CAD\ for\ Mac\ OS\ X/$MAJOR.$MINOR.$PATCH" + ssh -v $SFUSERNAME,br...@sh... mkdir "/home/frs/project/brlcad/BRL-CAD\ for\ Windows/$MAJOR.$MINOR.$PATCH" # upload source dist and any binaries - scp brlcad-$MAJOR.$MINOR.$PATCH* "$SFUSERNAME,br...@sh...:/home/frs/project/b/br/brlcad/BRL-CAD\ Source/$MAJOR.$MINOR.$PATCH/." + scp brlcad-$MAJOR.$MINOR.$PATCH* "$SFUSERNAME,br...@sh...:/home/frs/project/brlcad/BRL-CAD\ Source/$MAJOR.$MINOR.$PATCH/." # extract and upload release notes to source dir cat ../NEWS | tr '\n' '@' | perl -pi -e "s/.*?(@---[[:space:]@-]*[0-9]{4}-[0-9]{2}-[0-9]{2}[[:space:]]*Release[[:space:]]*${MAJOR}\.${MINOR}\.${PATCH}[[:space:]@-]*.*?)@---.*/\1/" | tr '@' '\n' > README-${MAJOR}-${MINOR}-${PATCH}.txt echo "Release notes for $MAJOR.$MINOR.$PATCH" && echo "===" cat README-$MAJOR-$MINOR-$PATCH.txt && echo "===" - scp README-$MAJOR-$MINOR-$PATCH.txt "$SFUSERNAME,br...@sh...:/home/frs/project/b/br/brlcad/BRL-CAD\ Source/$MAJOR.$MINOR.$PATCH/." + scp README-$MAJOR-$MINOR-$PATCH.txt "$SFUSERNAME,br...@sh...:/home/frs/project/brlcad/BRL-CAD\ Source/$MAJOR.$MINOR.$PATCH/." # NON-AUTO: Following the NAMING A BINARY RELEASE convention, # upload any release binaries and platform-specific release notes. - scp README-$MAJOR-$MINOR-$PATCH.txt "$SFUSERNAME,br...@sh...:/home/frs/project/b/br/brlcad/BRL-CAD\ Runtime\ Libraries/$MAJOR.$MINOR.$PATCH/." - scp README-$MAJOR-$MINOR-$PATCH.txt "$SFUSERNAME,br...@sh...:/home/frs/project/b/br/brlcad/BRL-CAD\ for\ BSD/$MAJOR.$MINOR.$PATCH/." - scp README-$MAJOR-$MINOR-$PATCH.txt "$SFUSERNAME,br...@sh...:/home/frs/project/b/br/brlcad/BRL-CAD\ for\ Linux/$MAJOR.$MINOR.$PATCH/." - scp README-$MAJOR-$MINOR-$PATCH.txt "$SFUSERNAME,br...@sh...:/home/frs/project/b/br/brlcad/BRL-CAD\ for\ Mac\ OS\ X/$MAJOR.$MINOR.$PATCH/." - scp README-$MAJOR-$MINOR-$PATCH.txt "$SFUSERNAME,br...@sh...:/home/frs/project/b/br/brlcad/BRL-CAD\ for\ Windows/$MAJOR.$MINOR.$PATCH/." + scp README-$MAJOR-$MINOR-$PATCH.txt "$SFUSERNAME,br...@sh...:/home/frs/project/brlcad/BRL-CAD\ Runtime\ Libraries/$MAJOR.$MINOR.$PATCH/." + scp README-$MAJOR-$MINOR-$PATCH.txt "$SFUSERNAME,br...@sh...:/home/frs/project/brlcad/BRL-CAD\ for\ BSD/$MAJOR.$MINOR.$PATCH/." + scp README-$MAJOR-$MINOR-$PATCH.txt "$SFUSERNAME,br...@sh...:/home/frs/project/brlcad/BRL-CAD\ for\ Linux/$MAJOR.$MINOR.$PATCH/." + scp README-$MAJOR-$MINOR-$PATCH.txt "$SFUSERNAME,br...@sh...:/home/frs/project/brlcad/BRL-CAD\ for\ Mac\ OS\ X/$MAJOR.$MINOR.$PATCH/." + scp README-$MAJOR-$MINOR-$PATCH.txt "$SFUSERNAME,br...@sh...:/home/frs/project/brlcad/BRL-CAD\ for\ Windows/$MAJOR.$MINOR.$PATCH/." # NON-AUTO: Be sure to mark binaries as default download, then # close shell session This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <br...@us...> - 2016-08-10 06:51:09
|
Revision: 68622 http://sourceforge.net/p/brlcad/code/68622 Author: brlcad Date: 2016-08-10 06:51:06 +0000 (Wed, 10 Aug 2016) Log Message: ----------- reading from stdin, not -i in-place file Modified Paths: -------------- brlcad/trunk/HACKING Modified: brlcad/trunk/HACKING =================================================================== --- brlcad/trunk/HACKING 2016-08-10 00:48:05 UTC (rev 68621) +++ brlcad/trunk/HACKING 2016-08-10 06:51:06 UTC (rev 68622) @@ -1414,7 +1414,7 @@ scp brlcad-$MAJOR.$MINOR.$PATCH* "$SFUSERNAME,br...@sh...:/home/frs/project/brlcad/BRL-CAD\ Source/$MAJOR.$MINOR.$PATCH/." # extract and upload release notes to source dir - cat ../NEWS | tr '\n' '@' | perl -pi -e "s/.*?(@---[[:space:]@-]*[0-9]{4}-[0-9]{2}-[0-9]{2}[[:space:]]*Release[[:space:]]*${MAJOR}\.${MINOR}\.${PATCH}[[:space:]@-]*.*?)@---.*/\1/" | tr '@' '\n' > README-${MAJOR}-${MINOR}-${PATCH}.txt + cat ../NEWS | tr '\n' '@' | perl -p -e "s/.*?(@---[[:space:]@-]*[0-9]{4}-[0-9]{2}-[0-9]{2}[[:space:]]*Release[[:space:]]*${MAJOR}\.${MINOR}\.${PATCH}[[:space:]@-]*.*?)@---.*/\1/" | tr '@' '\n' > README-${MAJOR}-${MINOR}-${PATCH}.txt echo "Release notes for $MAJOR.$MINOR.$PATCH" && echo "===" cat README-$MAJOR-$MINOR-$PATCH.txt && echo "===" scp README-$MAJOR-$MINOR-$PATCH.txt "$SFUSERNAME,br...@sh...:/home/frs/project/brlcad/BRL-CAD\ Source/$MAJOR.$MINOR.$PATCH/." This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <br...@us...> - 2016-08-13 19:40:13
|
Revision: 68670 http://sourceforge.net/p/brlcad/code/68670 Author: brlcad Date: 2016-08-13 19:40:07 +0000 (Sat, 13 Aug 2016) Log Message: ----------- add Caterpillar2 as a maintainer for fedora Modified Paths: -------------- brlcad/trunk/HACKING Modified: brlcad/trunk/HACKING =================================================================== --- brlcad/trunk/HACKING 2016-08-13 19:35:39 UTC (rev 68669) +++ brlcad/trunk/HACKING 2016-08-13 19:40:07 UTC (rev 68670) @@ -1456,6 +1456,9 @@ Slackware maintainer http://slackbuilds.org/result/?search=brlcad + Fedora maintainer + https://fedoraproject.org/wiki/User:Germano#Contact + ##################################################################### # 18: Announce the new release. This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <br...@us...> - 2017-03-05 03:29:25
|
Revision: 69517 http://sourceforge.net/p/brlcad/code/69517 Author: brlcad Date: 2017-03-05 03:29:22 +0000 (Sun, 05 Mar 2017) Log Message: ----------- the macros live in vmath.h Modified Paths: -------------- brlcad/trunk/HACKING Modified: brlcad/trunk/HACKING =================================================================== --- brlcad/trunk/HACKING 2017-03-02 23:20:50 UTC (rev 69516) +++ brlcad/trunk/HACKING 2017-03-05 03:29:22 UTC (rev 69517) @@ -548,7 +548,7 @@ comparisons are necessary, use the NEAR_EQUAL and NEAR_ZERO macros with a specified tolerance or the EQUAL and ZERO macros where a tolerance is indeterminate (all the macros are available by including -bn.h, part of libbn). Examples: +vmath.h). Examples: For known tolerances: This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <sta...@us...> - 2017-06-11 03:10:26
|
Revision: 69915 http://sourceforge.net/p/brlcad/code/69915 Author: starseeker Date: 2017-06-11 03:10:23 +0000 (Sun, 11 Jun 2017) Log Message: ----------- Add an explicit reminder to set the release date in NEWS *before* moving out from RELEASE branch... Modified Paths: -------------- brlcad/trunk/HACKING Modified: brlcad/trunk/HACKING =================================================================== --- brlcad/trunk/HACKING 2017-06-11 02:57:30 UTC (rev 69914) +++ brlcad/trunk/HACKING 2017-06-11 03:10:23 UTC (rev 69915) @@ -1330,6 +1330,8 @@ ##################################################################### # 09: Sync RELEASE to STABLE branch: + # Update the NEWS release date for the current release to today's date + # NON-AUTO: Review the log and obtain the last merge revision # number from comments. svn log --stop-on-copy https://svn.code.sf.net/p/brlcad/code/brlcad/branches/STABLE | less This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <sta...@us...> - 2018-03-23 02:29:24
|
Revision: 70842 http://sourceforge.net/p/brlcad/code/70842 Author: starseeker Date: 2018-03-23 02:29:22 +0000 (Fri, 23 Mar 2018) Log Message: ----------- build system is not Bourne Shell Script anymore... Modified Paths: -------------- brlcad/trunk/HACKING Modified: brlcad/trunk/HACKING =================================================================== --- brlcad/trunk/HACKING 2018-03-22 18:33:30 UTC (rev 70841) +++ brlcad/trunk/HACKING 2018-03-23 02:29:22 UTC (rev 70842) @@ -402,9 +402,10 @@ The vast majority of BRL-CAD is written in ANSI C with the intent to be strictly conformant to the C standard. A majority of the MGED geometry editor is written in a combination of C, Tcl/Tk, and Incr -Tcl/Tk. The BRL-CAD Benchmark, build system, and utility scripts are -written in what should be POSIX-compliant Bourne Shell Script. An -initial implementation of a BRL-CAD Geometry Server is written in PHP. +Tcl/Tk. The BRL-CAD Benchmark and utility scripts are written in what +should be POSIX-compliant Bourne Shell Script. The build system uses +the CMake build tool. An initial implementation of a BRL-CAD Geometry +Server is written in PHP. With release 7.0, BRL-CAD has moved forward and worked toward making all of BRL-CAD C code conform strictly with the ANSI/ISO standard for This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <br...@us...> - 2018-08-08 16:44:21
|
Revision: 71447 http://sourceforge.net/p/brlcad/code/71447 Author: brlcad Date: 2018-08-08 16:44:16 +0000 (Wed, 08 Aug 2018) Log Message: ----------- list is getting long, break into related sections for readability Modified Paths: -------------- brlcad/trunk/HACKING Modified: brlcad/trunk/HACKING =================================================================== --- brlcad/trunk/HACKING 2018-08-08 16:44:01 UTC (rev 71446) +++ brlcad/trunk/HACKING 2018-08-08 16:44:16 UTC (rev 71447) @@ -563,17 +563,26 @@ bu_malloc() instead of malloc() bu_calloc() instead of calloc() bu_realloc() instead of realloc() - bu_fgets() instead of fgets() bu_free() instead of free() - bu_log() instead of printf() + bu_bomb() instead of abort() bu_exit() instead of printf()+exit() - bu_dirname() instead of dirname() + bu_getopt() instead of getopt() bu_opterr instead of opterr bu_optind instead of optind bu_optopt instead of optopt bu_optarg instead of optarg + + bu_file_delete() instead of unlink(), rmdir(), and remove() + bu_path_basename() instead of basename() + bu_path_dirname() instead of dirname() + bu_path_match() instead of fnmatch() + + bu_log() instead of printf() + bu_fgets() instead of fgets() + bu_sort() instead of qsort() + bu_strdup() instead of strdup() bu_strlcat() instead of strcat(), strncat(), and strlcat() bu_strlcpy() instead of strcpy(), strncpy(), and strlcpy() @@ -581,8 +590,6 @@ bu_strcasecmp() and BU_STR_EQUIV() instead of stricmp()/strcasecmp() bu_strncmp() instead of strncmp() bu_strcasecmp() instead of strnicmp()/strncasecmp() - bu_file_delete() instead of unlink(), rmdir(), and remove() - bu_sort() instead of qsort() Similarly, ANSI C functions are preferred over the BSD and POSIX interfaces. The following functions should be used: This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <br...@us...> - 2018-09-19 03:39:51
|
Revision: 71745 http://sourceforge.net/p/brlcad/code/71745 Author: brlcad Date: 2018-09-19 03:39:46 +0000 (Wed, 19 Sep 2018) Log Message: ----------- new portability wrapper replaces common sleep calls Modified Paths: -------------- brlcad/trunk/HACKING Modified: brlcad/trunk/HACKING =================================================================== --- brlcad/trunk/HACKING 2018-09-19 03:37:08 UTC (rev 71744) +++ brlcad/trunk/HACKING 2018-09-19 03:39:46 UTC (rev 71745) @@ -567,6 +567,7 @@ bu_bomb() instead of abort() bu_exit() instead of printf()+exit() + bu_snooze() instead of sleep(), usleep(), nanosleep() bu_getopt() instead of getopt() bu_opterr instead of opterr This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <sta...@us...> - 2018-10-01 01:23:46
|
Revision: 71912 http://sourceforge.net/p/brlcad/code/71912 Author: starseeker Date: 2018-10-01 01:23:42 +0000 (Mon, 01 Oct 2018) Log Message: ----------- svn protocol isn't suitable for committing back changes Modified Paths: -------------- brlcad/trunk/HACKING Modified: brlcad/trunk/HACKING =================================================================== --- brlcad/trunk/HACKING 2018-09-28 23:30:31 UTC (rev 71911) +++ brlcad/trunk/HACKING 2018-10-01 01:23:42 UTC (rev 71912) @@ -1265,7 +1265,7 @@ PREV=[[last_trunk_rev]] echo "PREV=$PREV" - svn co svn://svn.code.sf.net/p/brlcad/code/brlcad/branches/RELEASE brlcad.RELEASE + svn co https://svn.code.sf.net/p/brlcad/code/brlcad/branches/RELEASE brlcad.RELEASE cd brlcad.RELEASE svn merge https://svn.code.sf.net/p/brlcad/code/brlcad/trunk@$PREV https://svn.code.sf.net/p/brlcad/code/brlcad/trunk@HEAD . This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <sta...@us...> - 2019-05-13 13:09:35
|
Revision: 73048 http://sourceforge.net/p/brlcad/code/73048 Author: starseeker Date: 2019-05-13 13:09:32 +0000 (Mon, 13 May 2019) Log Message: ----------- Update HACKING description for errata release conventions. Modified Paths: -------------- brlcad/trunk/HACKING Modified: brlcad/trunk/HACKING =================================================================== --- brlcad/trunk/HACKING 2019-05-13 00:09:01 UTC (rev 73047) +++ brlcad/trunk/HACKING 2019-05-13 13:09:32 UTC (rev 73048) @@ -1082,11 +1082,8 @@ {MAJOR_VERSION}.{MINOR_VERSION}.{PATCH_VERSION} All "development" builds use an odd number for the minor version. All -"release" builds use an even number for the minor version. Patched -versions should include a release count: +"release" builds use an even number for the minor version. - {MAJOR_VERSION}.{MINOR_VERSION}.{PATCH_VERSION}[-{RELEASE_COUNT}] - The MAJOR_VERSION should only increment when it is deemed that a significant amount of major changes have accumulated, new features have been added, or enough significant backwards incompatibilities @@ -1107,11 +1104,15 @@ version number. If it becomes necessary to update a posted release, use and increment -the RELEASE_COUNT. The first posted release is implicitly the "-0" -release count (e.g., 7.10.2 is implicitly 7.10.2-0) with subsequent -updated releases incrementing the count (e.g., 7.10.2-1). +the ERRATA_COUNT format outlined below. The first posted release is +implicitly the "-0" release (e.g., 7.10.2 is implicitly 7.10.2-0) with +subsequent updated releases incrementing the count (e.g., 7.10.2-1). +See the "ISSUING AN ERRATA" section below for guidelines on when an +errata update should be used in lieu of a new PATCH_VERSION release. + {MAJOR_VERSION}.{MINOR_VERSION}.{PATCH_VERSION}[-{ERRATA_COUNT}] + NAMING A SOURCE RELEASE ----------------------- @@ -1203,33 +1204,42 @@ zip -PATCHING A RELEASE ------------------- +ISSUING AN ERRATA UPDATE TO A RELEASE +------------------------------------- -Should it become necessary to patch a release that has already been -posted and announced, the mechanism is to post patch files for the -source release and update the uploaded release notes README file. +There are occasionally situations that arise in the release process +where immediately after the tagging and archive uploading a flaw is +identified in the tagged release. If the corrective change can be +succinctly expressed as a small update to the source code, the +update is posted as a patch file for the source release and the +uploaded release notes README file is adjusted to instruct users +building from source code to first apply the patch file or files. +It's expected that all errata patch files are independent and will be +applied sequentially. They should be consistently and incrementally +numbered. Users should be instructed in the release notes README to +download and apply all available patch files. + Example: stop_rt_crashing-0.patch and fix_fbserv-1.patch -It's expected that all patch files are independent and will be applied -sequentially. They should be consistently and incrementally numbered. -Users should be instructed in the release notes README to download and -apply all available patch files. +If it becomes necessary to repost a release, use the ERRATA_COUNT +file name convention described in VERSION NUMBERS & COMPATIBILITY. -For binary releases, it's recommended to just "move on" and let issues +Example: BRL-CAD-7.12.2.dmg is superseded by BRL-CAD-7.12.2-1.dmg + +For binary builds, it's recommended to just "move on" and let issues become resolved in the next release unless there's a critical security -or significant data corruption issue involved. If it becomes -necessary to repost a release, use the RELEASE_COUNT file name -convention described in VERSION NUMBERS & COMPATIBILITY. +or significant data corruption issue involved. If it is necessary to +update the binary, the CMake variable BRLCAD_VERSION_ERRATA may be +defined at configuration time to propagate the errata version number +through the build. BRLCAD_VERSION_ERRATA should be set to match the +highest errata patch file number applied to the source tree. -Example: BRL-CAD-7.12.2.dmg is superseded by BRL-CAD-7.12.2-1.dmg - -Patched binary releases may be moved to the hidden attic folder if +Older binary releases may be moved to the hidden attic folder if critical, though not necessary or recommended. They are preserved for historic record and should never be deleted once announced. Releases -not yet been announced may be updated within two days of being posted -without involving a patch. +which have not yet been announced may be updated within two days of +being posted without involving a errata update. MAKING A RELEASE This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <br...@us...> - 2019-05-13 14:48:13
|
Revision: 73050 http://sourceforge.net/p/brlcad/code/73050 Author: brlcad Date: 2019-05-13 14:48:10 +0000 (Mon, 13 May 2019) Log Message: ----------- generalize from errata to ammendments as we may update a release posting for reasons other than fixing something, it's just a small change of some sort. make the trigger point for ammendments even more explicit as they should be minimized as much as possible. this is because they cause a workflow outside of the usual release process with a number of manual steps not well documented (like uploading release notes with patch update instructions). they're should not be required when the release steps were not fully completed which includes tagging, upload, and announcement among other steps. Modified Paths: -------------- brlcad/trunk/HACKING Modified: brlcad/trunk/HACKING =================================================================== --- brlcad/trunk/HACKING 2019-05-13 14:42:06 UTC (rev 73049) +++ brlcad/trunk/HACKING 2019-05-13 14:48:10 UTC (rev 73050) @@ -1104,13 +1104,13 @@ version number. If it becomes necessary to update a posted release, use and increment -the ERRATA_COUNT format outlined below. The first posted release is +the AMEND_COUNT format outlined below. The first posted release is implicitly the "-0" release (e.g., 7.10.2 is implicitly 7.10.2-0) with subsequent updated releases incrementing the count (e.g., 7.10.2-1). -See the "ISSUING AN ERRATA" section below for guidelines on when an -errata update should be used in lieu of a new PATCH_VERSION release. +See the "AMENDING A RELEASE" section below for guidelines on when a +release should be amended in lieu of a new PATCH_VERSION release. - {MAJOR_VERSION}.{MINOR_VERSION}.{PATCH_VERSION}[-{ERRATA_COUNT}] + {MAJOR_VERSION}.{MINOR_VERSION}.{PATCH_VERSION}[-{AMEND_COUNT}] NAMING A SOURCE RELEASE @@ -1204,44 +1204,37 @@ zip -ISSUING AN ERRATA UPDATE TO A RELEASE -------------------------------------- +AMENDING A RELEASE +------------------ -There are occasionally situations that arise in the release process -where immediately after the tagging and archive uploading a flaw is -identified in the tagged release. If the corrective change can be -succinctly expressed as a small update to the source code, the -update is posted as a patch file for the source release and the -uploaded release notes README file is adjusted to instruct users -building from source code to first apply the patch file or files. +Should it become necessary to modify a release after it has been +tagged, uploaded, and announced, a release amendment may be issued. +Releases that are neither tagged, uploaded, or announced are subject +to at-will change and re-tagging. -It's expected that all errata patch files are independent and will be -applied sequentially. They should be consistently and incrementally -numbered. Users should be instructed in the release notes README to -download and apply all available patch files. +Amendments to source releases are expressed as a sequence of one or +more patch files that are to be applied sequentially. Patch files may +be descriptively named but must be incrementally numbered. The +uploaded release notes and/or README file(s) should instruct users +building from source to download and apply all available patch files +in order. Example: stop_rt_crashing-0.patch and fix_fbserv-1.patch -If it becomes necessary to repost a release, use the ERRATA_COUNT -file name convention described in VERSION NUMBERS & COMPATIBILITY. +For binary builds, it's recommended to just "move on" and let issues +become resolved in the next release unless there's a critical security +or data corruption issue involved. That said, binary releases may be +re-posted with a modified name per the convention described in VERSION +NUMBERS & COMPATIBILITY. Example: BRL-CAD-7.12.2.dmg is superseded by BRL-CAD-7.12.2-1.dmg -For binary builds, it's recommended to just "move on" and let issues -become resolved in the next release unless there's a critical security -or significant data corruption issue involved. If it is necessary to -update the binary, the CMake variable BRLCAD_VERSION_ERRATA may be -defined at configuration time to propagate the errata version number -through the build. BRLCAD_VERSION_ERRATA should be set to match the -highest errata patch file number applied to the source tree. +Older binary releases may be moved to the hidden attic folder, though +not necessary or recommended except where critical vulnerabilities are +involved. Releases are preserved for historic record and should never +be deleted once announced. -Older binary releases may be moved to the hidden attic folder if -critical, though not necessary or recommended. They are preserved for -historic record and should never be deleted once announced. Releases -which have not yet been announced may be updated within two days of -being posted without involving a errata update. - MAKING A RELEASE ---------------- @@ -1283,10 +1276,14 @@ ##################################################################### # 02: Test the merge. + # NON-AUTO: Confirm versioning in include/conf/. + # BRLCAD_VERSION_AMEND may be defined during CMake for an + # amendment build. + mkdir -p .build && cd .build cmake .. -DBRLCAD_BUNDLED_LIBS=ON -DCMAKE_BUILD_TYPE=Release && make - # Manually check rt, mged, and archer. + # NON-AUTO: Manually check rt, mged, and archer. bin/rt # should report usage with correct library versions bin/mged -c test.g "make sph sph ; draw sph ; rt" # pops up a sphere bin/mged # displays gui, run: opendb test.g ; draw sph ; rt This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <sta...@us...> - 2020-02-26 20:03:15
|
Revision: 74964 http://sourceforge.net/p/brlcad/code/74964 Author: starseeker Date: 2020-02-26 20:03:13 +0000 (Wed, 26 Feb 2020) Log Message: ----------- Give rt window a little time to show up before quitting MGED. Modified Paths: -------------- brlcad/trunk/HACKING Modified: brlcad/trunk/HACKING =================================================================== --- brlcad/trunk/HACKING 2020-02-26 14:53:54 UTC (rev 74963) +++ brlcad/trunk/HACKING 2020-02-26 20:03:13 UTC (rev 74964) @@ -1285,7 +1285,7 @@ # NON-AUTO: Manually check rt, mged, and archer. bin/rt # should report usage with correct library versions - bin/mged -c test.g "make sph sph ; draw sph ; rt" # pops up a sphere + bin/mged -c test.g "make sph sph ; draw sph ; rt ; after 1000 ; l sph" # create, view and list info about a sphere bin/mged # displays gui, run: opendb test.g ; draw sph ; rt bin/archer # displays gui, run: opendb test.g ; draw sph ; rt This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <br...@us...> - 2020-05-23 16:59:58
|
Revision: 75894 http://sourceforge.net/p/brlcad/code/75894 Author: brlcad Date: 2020-05-23 16:59:56 +0000 (Sat, 23 May 2020) Log Message: ----------- note that MOOSE now exists as the C++ API. Modified Paths: -------------- brlcad/trunk/HACKING Modified: brlcad/trunk/HACKING =================================================================== --- brlcad/trunk/HACKING 2020-05-23 16:25:47 UTC (rev 75893) +++ brlcad/trunk/HACKING 2020-05-23 16:59:56 UTC (rev 75894) @@ -418,10 +418,12 @@ except in very specific cases (should be discussed with the development team ahead of time to get consensus on the necessity.) -There is currently no C++ interface to the core BRL-CAD libraries. If -such an interface is eventually developed, it will be done separately -rather than mixing C++ semantics into existing APIs. +There is a C++ interface to the core BRL-CAD libraries called MOOSE +that is maintained in a separate repository. It is developed with +separation in order to avoid mixing C++ semantics into existing APIs +and to ensure clean separation of responsibilities and modularity. + CODING STYLE & STANDARDS ------------------------ This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <br...@us...> - 2020-05-23 17:05:54
|
Revision: 75897 http://sourceforge.net/p/brlcad/code/75897 Author: brlcad Date: 2020-05-23 17:05:51 +0000 (Sat, 23 May 2020) Log Message: ----------- mention the EXPORT markers now required Modified Paths: -------------- brlcad/trunk/HACKING Modified: brlcad/trunk/HACKING =================================================================== --- brlcad/trunk/HACKING 2020-05-23 17:03:59 UTC (rev 75896) +++ brlcad/trunk/HACKING 2020-05-23 17:05:51 UTC (rev 75897) @@ -831,19 +831,16 @@ All public library functions and most private or application functions should be appropriately documented using Doxygen/Javadoc style -comments. Without getting into the advanced details, this minimally -means that you need to add an additional asterisk to a comment that -precedes your functions: +comments. This minimally means that you need to add an additional +asterisk to a comment that precedes your functions. Public functions +must be exported and imported using per-library macros that precede +public symbol declarations (e.g., BU_EXPORT int func();). Example: /** * Computes the answer to the meaning of life, the universe, and * everything. */ -int -the_answer(void) -{ - return 42; -} +MYLIB_EXPORT int mylib_function(); TESTING & DEBUGGING This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |