AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Doxygen license12/17/2023 * This file contains the Foo struct and functions that act on it. * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. Step 1: Download and install Doxygen So head over to the Doxygen official website given in the link below and download the latest release of Doxygen. * along with this program if not, write to the Free Software See the NOTICE file distributed with this. * You should have received a copy of the GNU General Public License Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. * GNU General Public License for more details. * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Automatic C++ library API documentation generator using Doxygen, Sphinx. * but WITHOUT ANY WARRANTY without even the implied warranty of Documentation Status Latest Version Code Coverage Report License BSD-3 Clause. * This program is distributed in the hope that it will be useful, * of the License, or (at your option) any later version. Doxygen uses libiconv (or the iconv built into libc) for the transcoding. * as published by the Free Software Foundation either version 2 * modify it under the terms of the GNU General Public License * This program is free software you can redistribute it and/or This means that the first time GNU libiconv is installed, we have a circular dependency between the GNU libiconv and GNU gettext packages, which can be resolved by building and installing either. * Modifications copyright 2022 einpoklum That doesn't include licensing info (unless licensing is the reason for organizing code into files in a certain way).įor your example, that might look something like this: /* foo.c No representations are made about the suitability of this software for any purpose. Permission to use, copy, modify, and distribute this software and its documentation under the terms of the GNU General Public License is hereby granted. The file-level documentation comment should explain things like what's in the file and how it relates to other files basically, things that will be useful to someone who wants to understand how the code is organized. Doxygen license Copyright 1997-2022by Dimitri van Heesch. I think this makes sense, since the generated documentation is meant to be read by programmers, and they won't care about the license information (or at least, that's not what they'll be looking for in the documentation). What I've typically seen in source files which have documentation comments is that the license information is included in a separate, non-documentation comment block. I do not know if there's a standard for this, but given that (as I write this) nobody else has answered, I might as well.
0 Comments
Read More
Leave a Reply. |