| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
It can attempt to use bin_opt_gcc_ directory before it is created.
Notes:
svn path=/head/; revision=426520
|
|
|
|
|
|
|
|
| |
- Silence patching
- Regenerate patches with `make makepatch`
Notes:
svn path=/head/; revision=416584
|
|
|
|
|
|
|
|
| |
With hat: portmgr
Sponsored by: Absolight
Notes:
svn path=/head/; revision=387021
|
|
|
|
|
|
|
| |
- Fix installation from non-root
Notes:
svn path=/head/; revision=380328
|
|
|
|
| |
Notes:
svn path=/head/; revision=340759
|
|
|
|
|
|
|
| |
devel part 1)
Notes:
svn path=/head/; revision=327722
|
|
|
|
|
|
|
| |
- Trim Makefile header
Notes:
svn path=/head/; revision=324181
|
|
|
|
| |
Notes:
svn path=/head/; revision=276999
|
|
|
|
|
|
|
|
|
|
|
| |
e-mail addresses from the pkg-descr file that could reasonably
be mistaken for maintainer contact information in order to avoid
confusion on the part of users looking for support. As a pleasant
side effect this also avoids confusion and/or frustration for people
who are no longer maintaining those ports.
Notes:
svn path=/head/; revision=246327
|
|
|
|
| |
Notes:
svn path=/head/; revision=161363
|
|
|
|
| |
Notes:
svn path=/head/; revision=149311
|
|
|
|
|
|
|
|
| |
PR: ports/77597
Submitted by: Simon Barner
Notes:
svn path=/head/; revision=129029
|
|
|
|
| |
Notes:
svn path=/head/; revision=111349
|
|
|
|
| |
Notes:
svn path=/head/; revision=101226
|
|
|
|
| |
Notes:
svn path=/head/; revision=99360
|
|
|
|
| |
Notes:
svn path=/head/; revision=95323
|
|
|
|
| |
Notes:
svn path=/head/; revision=93890
|
|
|
|
| |
Notes:
svn path=/head/; revision=91019
|
|
|
|
|
|
|
|
| |
Submitted by: Oleg Karachevtsev <ok@etrust.ru>
PR: 56998
Notes:
svn path=/head/; revision=89169
|
|
|
|
| |
Notes:
svn path=/head/; revision=76032
|
|
|
|
| |
Notes:
svn path=/head/; revision=60483
|
|
- textproc added in category (like astyle)
Ccdoc is a tool for extracting comments from C++ source code and presenting it
in HTML format, very similar to Java's JavaDoc tool. The tagging used in ccdoc
is very similar to that of Javadoc, with adaptations for the C++ specifics, of
course. Ccdoc supports extracting comments from both header and implementation
files.
In contrast to most other C++ doc'ing applications, ccdoc analyses the code
before it has been run through the pre-processor, so things such as macros can
actually be included in the documentation.
It's usage is not quite as straight forward as JavaDoc's, but considering the
quality of the output, it is well worth the effort.
WWW: http://www.joelinoff.com/ccdoc/
PR: 22794
Submitted by: lonewolf@flame.org
Notes:
svn path=/head/; revision=39837
|