From a45f487aa82e4bed053e86cde82a2c4d229b2e22 Mon Sep 17 00:00:00 2001 From: Yorick GEOFFRE Date: Fri, 16 Sep 2022 23:48:30 +0000 Subject: [PATCH] Initial commit --- .drone.yml | 52 + .gitignore | 62 + Documentation/doc_images/CodeFirst.png | Bin 0 -> 4677 bytes Documentation/doxygen/Doxyfile | 1526 +++++++++++++++++ Documentation/doxygen/footer.html | 8 + Documentation/doxygen/images/CodeFirst.png | Bin 0 -> 4677 bytes README.md | 22 + .../Applications/Tests/helloLibrary/main.cpp | 12 + .../Tests/helloLibrary/makefile.lnx | 7 + .../Tests/helloLibrary/makeprj.lnx | 34 + Sources/_Linux/Documentation/makefile | 5 + Sources/_Linux/helloLibrary/makefile.lnx | 7 + Sources/_Linux/helloLibrary/makeprj.lnx | 34 + Sources/_Linux/makefile.lnx | 12 + Sources/bin/.gitkeep | 0 Sources/bin/build.log | 0 Sources/bin/helloLibrary_Tests | Bin 0 -> 65248 bytes Sources/bin/helloLibrary_Testsd | Bin 0 -> 51832 bytes Sources/include/helloLibrary/Class1.h | 31 + Sources/src/helloLibrary/Class1.cpp | 13 + sonar-project.properties | 13 + 21 files changed, 1838 insertions(+) create mode 100644 .drone.yml create mode 100644 .gitignore create mode 100644 Documentation/doc_images/CodeFirst.png create mode 100755 Documentation/doxygen/Doxyfile create mode 100755 Documentation/doxygen/footer.html create mode 100644 Documentation/doxygen/images/CodeFirst.png create mode 100644 README.md create mode 100755 Sources/Applications/Tests/helloLibrary/main.cpp create mode 100755 Sources/_Linux/Applications/Tests/helloLibrary/makefile.lnx create mode 100755 Sources/_Linux/Applications/Tests/helloLibrary/makeprj.lnx create mode 100755 Sources/_Linux/Documentation/makefile create mode 100755 Sources/_Linux/helloLibrary/makefile.lnx create mode 100755 Sources/_Linux/helloLibrary/makeprj.lnx create mode 100755 Sources/_Linux/makefile.lnx create mode 100644 Sources/bin/.gitkeep create mode 100644 Sources/bin/build.log create mode 100755 Sources/bin/helloLibrary_Tests create mode 100755 Sources/bin/helloLibrary_Testsd create mode 100755 Sources/include/helloLibrary/Class1.h create mode 100755 Sources/src/helloLibrary/Class1.cpp create mode 100644 sonar-project.properties diff --git a/.drone.yml b/.drone.yml new file mode 100644 index 0000000..4b62ac4 --- /dev/null +++ b/.drone.yml @@ -0,0 +1,52 @@ +kind: pipeline +type: docker +name: default + +trigger: + event: + - push + +steps: +- name: build + image: pubhub.codefirst.ddns.net/thbellem/codefirst-drone-cppcheck:latest + volumes: + - name: work + path: /work + commands: + - find . -iname "*.cpp" | xargs cppcheck -v --enable=all --xml-version=2 --xml 2> /work/cppcheck.xml + - cd Sources/_Linux/ + - make -f makefile.lnx release + +- name: code analysis + image: aosapps/drone-sonar-plugin + volumes: + - name: work + path: /work + settings: + sonar_host: https://codefirst.ddns.net/sonar/ + sonar_token: 96864ed9ef8d6343007881fc9ef30eb70eaf846d + java_binaries: target/classes + level: DEBUG + sources: . + depends_on: [ build ] + +- name: generate-and-deploy-docs + image: pubhub.codefirst.ddns.net/thbellem/codefirst-docdeployer + volumes: + - name: docs + path: /docs + commands: + - cd Documentation/doxygen + - doxygen Doxyfile + - /entrypoint.sh + when: + branch: + - master + depends_on: [ build ] + +# image_pull_secrets: +# - DOCKERCONFIG + +volumes: +- name: work + temp: {} \ No newline at end of file diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..9abe27b --- /dev/null +++ b/.gitignore @@ -0,0 +1,62 @@ +# ---> C++ +# Prerequisites +*.d + +# Compiled Object files +*.slo +*.lo +*.o +*.obj + +# Precompiled Headers +*.gch +*.pch + +# Compiled Dynamic libraries +*.so +*.dylib +*.dll + +# Fortran module files +*.mod +*.smod + +# Compiled Static libraries +*.lai +*.la +*.a +*.lib + +# Executables +*.exe +*.out +*.app + +# ---> macOS +# General +.DS_Store +.AppleDouble +.LSOverride + +# Icon must end with two \r +Icon + +# Thumbnails +._* + +# Files that might appear in the root of a volume +.DocumentRevisions-V100 +.fseventsd +.Spotlight-V100 +.TemporaryItems +.Trashes +.VolumeIcon.icns +.com.apple.timemachine.donotpresent + +# Directories potentially created on remote AFP share +.AppleDB +.AppleDesktop +Network Trash Folder +Temporary Items +.apdisk + diff --git a/Documentation/doc_images/CodeFirst.png b/Documentation/doc_images/CodeFirst.png new file mode 100644 index 0000000000000000000000000000000000000000..7583537f5890eff06a48af575f4d1679ccc49e34 GIT binary patch literal 4677 zcmbVQ2UJr_w@xTAARVNa7!?pnCA0tnNs!{D7b%LSQ9}}vNK>REDguHCN>S;cQoT}? zDqhN!stAY(h>9WzB8nB?!M5&u>woRfTIZZOGvDksdw+8#Cmif7MTHfGK_HN*wH3(; zc+!B23WWgopt<4&;334e^5B9%o254{Fz75AQVnTv z)7>!RFgze2h|VL!!h#q~EOXc{pdHyUWY(pZM z!aB?|fdiKQa3P5OTP&0NGfY6hP+?>?3WG#%xbz)JqyEOR4|5pbmD8vwI)ffWXY#lJ z7V{g+_G9r_TtC)-Bl`F7e^LO1*4Fm7j(=%OP|$A`T%JV;;Kt8@{7W>~C7ex1InlYS z!yGEzA_OpV+lDu6Jdr~u^H>}g7K`y~p&Wjh48vlOSeT|Qnd;BnaAM~_rqD@b9^C{E ztQ!`A#vm{l7c2&k#^7}fb^&)Z`UljOMf3Lw|0h%zf!1+BWAVBMcpc0xpz#|DBn^$s zBmb{p8Wr!u;slWam;HmtzH}6u=?jPb4kVt)Vz4-XV!%3`fA(7wi4Gi=k3Rz#;5u0n zVAd8yJ&d8A9s-NRd^gwD7H`eu^2kgo-I`Tu*OF7H(dcQzX^}d1Xzv((AnvCoL3-_ z$dEP3+$HSc;sL>{F4nSlCMPE&H)%B7ym`}$EhHosBQTZfb?D5r*w(n4(vM<|+9w0P zmFG=(E!pmMZ5^FlvY%HERiCtNt*qd_iWo^<{rGn7_{W5|siNC;uzW_XR6+9H}_aNHO3>RpIgDFagCOwaWzz((^qffO&Qm0y@LNVS^A6Iq| zlGRo}ud&|0yjPmEse9m}>G>^u4tCj_WYu8Ns>We$%&C?>!JPyUrDSg4Vjce`v1-B1 zvejp{S=Oeg7}Y{V6{`bADr$N&chxEC22_{W=G5k!9I1UX+g0a!#jWP;+`wCvZBnvr zr(7T+&;`E&|9d4hlshMDKCdm+0mc|gONczY6=s>LN-wlb_1Ut^jV2_mPCEm)aC)As zpi}$TX{EaA>Zm%edZt3Yn#iGLC6b1H{?m@Q;J))ZU8C{@{v?kG)!j$C)$Q}|3d?9t z%Yhyn*qqh8YL|y+yqh0^=*mM6kzn4<5qFwGmtHGcu7COX@w4f%FYI%Ua+@OG&AUFh zvJWL|6vCK@VRwz!`TFYk_Tv_8jH26hE+r=U4CMEvZ?~p=Se)%j{rijeGN|3miZFF6 z{C33JYZVy@uo1ACDYI5-wf-=FS2b*{&u2|T&a@SrT7@w36GxM9yX5S21R0hYNmqU3k zc)QSGCy+@K-ie<*Dj3 z_m3)O$9bU5_%_D`9Rf)n-j(d}r1OM|C?vS$=*O|+;%deb1kkJ1m-nvzaUSb5kfR%T z&P8HZr}cY&cx+AR(qkxCz`(aZ*EsCRxAo=;&5O$E`x`mdrgdR&p5*R5r`^+=g&L@E zDen+9j-61qy|C=QxoT};{Psn)7G})&)=RgKi*I7QnO5&gRl9g6S>fJF9i=m=9RSj- z8nazx%PW9^iQQQzq%~HOI}Z{LpBWtf~{Dum~vD0vilhrMepKEvQJy#vKNxb&e zXw}<<_U&nj4PkHK6OCMroZXT5z{w`vy%%>kuhvam_n%#fHV!ur6W0>i4vBCR6egG% zBHM4*iAxOq*>?_+Qw%QMo0T$GSv^)EaJZ4$B_@_qI+vyG7`r%8Kj5njSA2u;x-rJL zr_?U5A!F7Yx&RgsPayN@vK~KLYWL|*i%}wAhM+ssZL3bblppNN(GP#(D1g`2zUw>e zDDdRnt5L@Cbo-4?wDR=ij}O^&(p-x_RZ&+f^kAGT8q04! z3%TY|m-wvv4AC$lHRHT?!_O0_m` ztDE}F$LREfqau$1@}x$J!>?@Bx1FD zwt$LY%pZNDCJ`n&eZSm!ue}IzyG7}GEVxQY3!E-&*)~B)vcO0bglFO-Uk(?CXC#ae z+}glfPfWB%wWb##4z}#~aBU2XUoJ-8ef|2uHLuM1cM{m5fJcI9daofzLZM|*-`0mS z?w;K#{VgR+R=(<`d|5KUm)yh76{l&l594V&%s!?{8L&FfaD|vg8jJfgaCC(RmyO@Q zXMWZB8m>dIi+T3zTGW>}DDQg71d;&p?x{chhB^dWNPF$sV8@KprkF}CcNI^hNA&b2eI^rt$ z)o=0B7o$EYTLMXVKs36T#l^Cjz6b@QB#+S=B|AXUwJCD)~VOHuCkv}XP)?p^sbtCT+E3JuQzxa zo%R^zb>k|p7rZ^kB0(-gFUWH=aQhe1tT3xPuMQMjDQ9|04y9@zn&h3UF_7eGMo(b; zm8{SYicijCG=m@#*L0W595!hXBR{Ut*Do*xbK?P$tuEf1rPz|nskRz(eKH3yUvMO( zT(@+MJ_{KHcC#Yz)=NY&sN+mWLNP?lU#`$ct5{0Xj1ocoa_ll8K_uGcn&-%};lr;c zybCN`TkID>J_jT!ZGkQKj?G*zm146gj(jR4f9*bU?u z{7j{e*qwNG*FL*|X?F)F;&Z;Van}Pk7z#IoXA@_dWp+BrgUY??D`(zrmP0n|z8xd~ zMrXU!&X1{Z+IQ7` z#wqZ1QM_dST5i6-{C|afn!8$4q8VDSK*TzlV2vYhcCKVedIx0)@ zC50?K4jL0Iw#mdERTDBT;Li2e6j^5^TK1p0z3n|SacOGf^pq%1A8EFXBW%i_sv{YT^4tfK%on;q_R=NFi_q{D&exL!zt3f~tW zUNE>fT1_VA6U@Cg8v%Q-w72x}7K&D8o|t~Vz~7G1gKh)4hIOm7w1q+ox5?KnRw4V` zdk)5Im2mOkJqj|b_)8+Wgnw7_Eq7>>WcSo&AI;3Sx?enmq_#UKnqq}g0yz?3^J~Nh z6WCEHLh!Y8_xyzVA}ljkS|lx$E)J9F{>WYb0x+vNOJj@DoP(R2ijGQy(4o3qlgXtQ zvW|Jm3qo|t9lO*+*E1?s`LqA-2EV}7tR00erXTzI>7!updh7lXGn;&9Vq=Bo-}moN zce^=-;uR{|rZ)3+hA10-_Pry0eJo);KPuivY#4F)y~-znt>70+m-#b?yoTD7@3U2NFh+@?h&AtTL2l6!BVxfXE z$K%OrumU5G>O>uHd;kb9RNYgz_dft@kuJO z8K;jlI2|0OOA64!g(5$3Df;rsab@>=R6Ft{o4l-Nb_hP{phd|GA{%B9bfepe^LR^(9+dlZNf0Y>hT0gT#?On(` z<9ddqCPDXvQ3v^EM|e~vVLR^X<%65|t(NZ>-d3_2EUnoKF3ZY!OA!<7I3Hz7x;2=u zDCf}Gp>nceGU$Gpqj6V4NkCC&@QJo)F#lM*kaUAq?Cs^JJsGXf>Rs@TI9U3cMnzh$ z$!SFiC1zsbt|r@2-YZk#lHVtW7YT#^I5k|*1r82<8)pY^kxk$Nxejv?GgUr?zLe>% aZ-QD)pYCu~^Gi1V=&`o2BUKU(#r_8}z{j5e literal 0 HcmV?d00001 diff --git a/Documentation/doxygen/Doxyfile b/Documentation/doxygen/Doxyfile new file mode 100755 index 0000000..17a7358 --- /dev/null +++ b/Documentation/doxygen/Doxyfile @@ -0,0 +1,1526 @@ +# Doxyfile 1.5.8 + +# This file describes the settings to be used by the documentation system +# doxygen (www.doxygen.org) for a project +# +# All text after a hash (#) is considered a comment and will be ignored +# The format is: +# TAG = value [value, ...] +# For lists items can also be appended using: +# TAG += value [value, ...] +# Values that contain spaces should be placed between quotes (" ") + +#--------------------------------------------------------------------------- +# Project related configuration options +#--------------------------------------------------------------------------- + +# This tag specifies the encoding used for all characters in the config file +# that follow. The default is UTF-8 which is also the encoding used for all +# text before the first occurrence of this tag. Doxygen uses libiconv (or the +# iconv built into libc) for the transcoding. See +# http://www.gnu.org/software/libiconv for the list of possible encodings. + +DOXYFILE_ENCODING = UTF-8 + +# The PROJECT_NAME tag is a single word (or a sequence of words surrounded +# by quotes) that should identify the project. + +PROJECT_NAME = "project-" + +# The PROJECT_NUMBER tag can be used to enter a project or revision number. +# This could be handy for archiving the generated documentation or +# if some version control system is used. + +PROJECT_NUMBER = 1.0.0 + +PROJECT_BRIEF = "" + +PROJECT_LOGO = images/CodeFirst.png + +# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) +# base path where the generated documentation will be put. +# If a relative path is entered, it will be relative to the location +# where doxygen was started. If left blank the current directory will be used. + +OUTPUT_DIRECTORY = /docs + +# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create +# 4096 sub-directories (in 2 levels) under the output directory of each output +# format and will distribute the generated files over these directories. +# Enabling this option can be useful when feeding doxygen a huge amount of +# source files, where putting all generated files in the same directory would +# otherwise cause performance problems for the file system. + +CREATE_SUBDIRS = NO + +# The OUTPUT_LANGUAGE tag is used to specify the language in which all +# documentation generated by doxygen is written. Doxygen will use this +# information to generate all constant output in the proper language. +# The default language is English, other supported languages are: +# Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional, +# Croatian, Czech, Danish, Dutch, Farsi, Finnish, French, German, Greek, +# Hungarian, Italian, Japanese, Japanese-en (Japanese with English messages), +# Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian, Polish, +# Portuguese, Romanian, Russian, Serbian, Serbian-Cyrilic, Slovak, Slovene, +# Spanish, Swedish, and Ukrainian. + +OUTPUT_LANGUAGE = English + +# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will +# include brief member descriptions after the members that are listed in +# the file and class documentation (similar to JavaDoc). +# Set to NO to disable this. + +BRIEF_MEMBER_DESC = YES + +# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend +# the brief description of a member or function before the detailed description. +# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the +# brief descriptions will be completely suppressed. + +REPEAT_BRIEF = YES + +# This tag implements a quasi-intelligent brief description abbreviator +# that is used to form the text in various listings. Each string +# in this list, if found as the leading text of the brief description, will be +# stripped from the text and the result after processing the whole list, is +# used as the annotated text. Otherwise, the brief description is used as-is. +# If left blank, the following values are used ("name" is automatically +# replaced with the name of the entity): "The name class" "The name widget" +# "The name file" "is" "provides" "specifies" "contains" +# "represents" "a" "an" "the" + +ABBREVIATE_BRIEF = "The name class" \ + "The name widget" \ + "The name file" \ + is \ + provides \ + specifies \ + contains \ + represents \ + a \ + an \ + the + +# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then +# Doxygen will generate a detailed section even if there is only a brief +# description. + +ALWAYS_DETAILED_SEC = NO + +# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all +# inherited members of a class in the documentation of that class as if those +# members were ordinary class members. Constructors, destructors and assignment +# operators of the base classes will not be shown. + +INLINE_INHERITED_MEMB = NO + +# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full +# path before files name in the file list and in the header files. If set +# to NO the shortest path that makes the file name unique will be used. + +FULL_PATH_NAMES = YES + +# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag +# can be used to strip a user-defined part of the path. Stripping is +# only done if one of the specified strings matches the left-hand part of +# the path. The tag can be used to show relative paths in the file list. +# If left blank the directory from which doxygen is run is used as the +# path to strip. + +STRIP_FROM_PATH = + +# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of +# the path mentioned in the documentation of a class, which tells +# the reader which header file to include in order to use a class. +# If left blank only the name of the header file containing the class +# definition is used. Otherwise one should specify the include paths that +# are normally passed to the compiler using the -I flag. + +STRIP_FROM_INC_PATH = + +# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter +# (but less readable) file names. This can be useful is your file systems +# doesn't support long names like on DOS, Mac, or CD-ROM. + +SHORT_NAMES = NO + +# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen +# will interpret the first line (until the first dot) of a JavaDoc-style +# comment as the brief description. If set to NO, the JavaDoc +# comments will behave just like regular Qt-style comments +# (thus requiring an explicit @brief command for a brief description.) + +JAVADOC_AUTOBRIEF = NO + +# If the QT_AUTOBRIEF tag is set to YES then Doxygen will +# interpret the first line (until the first dot) of a Qt-style +# comment as the brief description. If set to NO, the comments +# will behave just like regular Qt-style comments (thus requiring +# an explicit \brief command for a brief description.) + +QT_AUTOBRIEF = NO + +# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen +# treat a multi-line C++ special comment block (i.e. a block of //! or /// +# comments) as a brief description. This used to be the default behaviour. +# The new default is to treat a multi-line C++ comment block as a detailed +# description. Set this tag to YES if you prefer the old behaviour instead. + +MULTILINE_CPP_IS_BRIEF = YES + +# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented +# member inherits the documentation from any documented member that it +# re-implements. + +INHERIT_DOCS = YES + +# If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce +# a new page for each member. If set to NO, the documentation of a member will +# be part of the file/class/namespace that contains it. + +SEPARATE_MEMBER_PAGES = NO + +# The TAB_SIZE tag can be used to set the number of spaces in a tab. +# Doxygen uses this value to replace tabs by spaces in code fragments. + +TAB_SIZE = 3 + +# This tag can be used to specify a number of aliases that acts +# as commands in the documentation. An alias has the form "name=value". +# For example adding "sideeffect=\par Side Effects:\n" will allow you to +# put the command \sideeffect (or @sideeffect) in the documentation, which +# will result in a user-defined paragraph with heading "Side Effects:". +# You can put \n's in the value part of an alias to insert newlines. + +ALIASES = + +# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C +# sources only. Doxygen will then generate output that is more tailored for C. +# For instance, some of the names that are used will be different. The list +# of all members will be omitted, etc. + +OPTIMIZE_OUTPUT_FOR_C = NO + +# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java +# sources only. Doxygen will then generate output that is more tailored for +# Java. For instance, namespaces will be presented as packages, qualified +# scopes will look different, etc. + +OPTIMIZE_OUTPUT_JAVA = NO + +# Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran +# sources only. Doxygen will then generate output that is more tailored for +# Fortran. + +OPTIMIZE_FOR_FORTRAN = NO + +# Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL +# sources. Doxygen will then generate output that is tailored for +# VHDL. + +OPTIMIZE_OUTPUT_VHDL = NO + +# Doxygen selects the parser to use depending on the extension of the files it parses. +# With this tag you can assign which parser to use for a given extension. +# Doxygen has a built-in mapping, but you can override or extend it using this tag. +# The format is ext=language, where ext is a file extension, and language is one of +# the parsers supported by doxygen: IDL, Java, Javascript, C#, C, C++, D, PHP, +# Objective-C, Python, Fortran, VHDL, C, C++. For instance to make doxygen treat +# .inc files as Fortran files (default is PHP), and .f files as C (default is Fortran), +# use: inc=Fortran f=C + +EXTENSION_MAPPING = + +# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want +# to include (a tag file for) the STL sources as input, then you should +# set this tag to YES in order to let doxygen match functions declarations and +# definitions whose arguments contain STL classes (e.g. func(std::string); v.s. +# func(std::string) {}). This also make the inheritance and collaboration +# diagrams that involve STL classes more complete and accurate. + +BUILTIN_STL_SUPPORT = NO + +# If you use Microsoft's C++/CLI language, you should set this option to YES to +# enable parsing support. + +CPP_CLI_SUPPORT = NO + +# Set the SIP_SUPPORT tag to YES if your project consists of sip sources only. +# Doxygen will parse them like normal C++ but will assume all classes use public +# instead of private inheritance when no explicit protection keyword is present. + +SIP_SUPPORT = NO + +# For Microsoft's IDL there are propget and propput attributes to indicate getter +# and setter methods for a property. Setting this option to YES (the default) +# will make doxygen to replace the get and set methods by a property in the +# documentation. This will only work if the methods are indeed getting or +# setting a simple type. If this is not the case, or you want to show the +# methods anyway, you should set this option to NO. + +IDL_PROPERTY_SUPPORT = YES + +# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC +# tag is set to YES, then doxygen will reuse the documentation of the first +# member in the group (if any) for the other members of the group. By default +# all members of a group must be documented explicitly. + +DISTRIBUTE_GROUP_DOC = NO + +# Set the SUBGROUPING tag to YES (the default) to allow class member groups of +# the same type (for instance a group of public functions) to be put as a +# subgroup of that type (e.g. under the Public Functions section). Set it to +# NO to prevent subgrouping. Alternatively, this can be done per class using +# the \nosubgrouping command. + +SUBGROUPING = YES + +# When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum +# is documented as struct, union, or enum with the name of the typedef. So +# typedef struct TypeS {} TypeT, will appear in the documentation as a struct +# with name TypeT. When disabled the typedef will appear as a member of a file, +# namespace, or class. And the struct will be named TypeS. This can typically +# be useful for C code in case the coding convention dictates that all compound +# types are typedef'ed and only the typedef is referenced, never the tag name. + +TYPEDEF_HIDES_STRUCT = NO + +# The SYMBOL_CACHE_SIZE determines the size of the internal cache use to +# determine which symbols to keep in memory and which to flush to disk. +# When the cache is full, less often used symbols will be written to disk. +# For small to medium size projects (<1000 input files) the default value is +# probably good enough. For larger projects a too small cache size can cause +# doxygen to be busy swapping symbols to and from disk most of the time +# causing a significant performance penality. +# If the system has enough physical memory increasing the cache will improve the +# performance by keeping more symbols in memory. Note that the value works on +# a logarithmic scale so increasing the size by one will rougly double the +# memory usage. The cache size is given by this formula: +# 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0, +# corresponding to a cache size of 2^16 = 65536 symbols + +SYMBOL_CACHE_SIZE = 0 + +#--------------------------------------------------------------------------- +# Build related configuration options +#--------------------------------------------------------------------------- + +# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in +# documentation are documented, even if no documentation was available. +# Private class members and static file members will be hidden unless +# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES + +EXTRACT_ALL = YES + +# If the EXTRACT_PRIVATE tag is set to YES all private members of a class +# will be included in the documentation. + +EXTRACT_PRIVATE = YES + +# If the EXTRACT_STATIC tag is set to YES all static members of a file +# will be included in the documentation. + +EXTRACT_STATIC = YES + +# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) +# defined locally in source files will be included in the documentation. +# If set to NO only classes defined in header files are included. + +EXTRACT_LOCAL_CLASSES = YES + +# This flag is only useful for Objective-C code. When set to YES local +# methods, which are defined in the implementation section but not in +# the interface are included in the documentation. +# If set to NO (the default) only methods in the interface are included. + +EXTRACT_LOCAL_METHODS = NO + +# If this flag is set to YES, the members of anonymous namespaces will be +# extracted and appear in the documentation as a namespace called +# 'anonymous_namespace{file}', where file will be replaced with the base +# name of the file that contains the anonymous namespace. By default +# anonymous namespace are hidden. + +EXTRACT_ANON_NSPACES = NO + +# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all +# undocumented members of documented classes, files or namespaces. +# If set to NO (the default) these members will be included in the +# various overviews, but no documentation section is generated. +# This option has no effect if EXTRACT_ALL is enabled. + +HIDE_UNDOC_MEMBERS = NO + +# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all +# undocumented classes that are normally visible in the class hierarchy. +# If set to NO (the default) these classes will be included in the various +# overviews. This option has no effect if EXTRACT_ALL is enabled. + +HIDE_UNDOC_CLASSES = NO + +# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all +# friend (class|struct|union) declarations. +# If set to NO (the default) these declarations will be included in the +# documentation. + +HIDE_FRIEND_COMPOUNDS = NO + +# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any +# documentation blocks found inside the body of a function. +# If set to NO (the default) these blocks will be appended to the +# function's detailed documentation block. + +HIDE_IN_BODY_DOCS = NO + +# The INTERNAL_DOCS tag determines if documentation +# that is typed after a \internal command is included. If the tag is set +# to NO (the default) then the documentation will be excluded. +# Set it to YES to include the internal documentation. + +INTERNAL_DOCS = NO + +# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate +# file names in lower-case letters. If set to YES upper-case letters are also +# allowed. This is useful if you have classes or files whose names only differ +# in case and if your file system supports case sensitive file names. Windows +# and Mac users are advised to set this option to NO. + +CASE_SENSE_NAMES = YES + +# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen +# will show members with their full class and namespace scopes in the +# documentation. If set to YES the scope will be hidden. + +HIDE_SCOPE_NAMES = YES + +# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen +# will put a list of the files that are included by a file in the documentation +# of that file. + +SHOW_INCLUDE_FILES = YES + +# If the INLINE_INFO tag is set to YES (the default) then a tag [inline] +# is inserted in the documentation for inline members. + +INLINE_INFO = YES + +# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen +# will sort the (detailed) documentation of file and class members +# alphabetically by member name. If set to NO the members will appear in +# declaration order. + +SORT_MEMBER_DOCS = YES + +# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the +# brief documentation of file, namespace and class members alphabetically +# by member name. If set to NO (the default) the members will appear in +# declaration order. + +SORT_BRIEF_DOCS = NO + +# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the +# hierarchy of group names into alphabetical order. If set to NO (the default) +# the group names will appear in their defined order. + +SORT_GROUP_NAMES = NO + +# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be +# sorted by fully-qualified names, including namespaces. If set to +# NO (the default), the class list will be sorted only by class name, +# not including the namespace part. +# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES. +# Note: This option applies only to the class list, not to the +# alphabetical list. + +SORT_BY_SCOPE_NAME = NO + +# The GENERATE_TODOLIST tag can be used to enable (YES) or +# disable (NO) the todo list. This list is created by putting \todo +# commands in the documentation. + +GENERATE_TODOLIST = YES + +# The GENERATE_TESTLIST tag can be used to enable (YES) or +# disable (NO) the test list. This list is created by putting \test +# commands in the documentation. + +GENERATE_TESTLIST = YES + +# The GENERATE_BUGLIST tag can be used to enable (YES) or +# disable (NO) the bug list. This list is created by putting \bug +# commands in the documentation. + +GENERATE_BUGLIST = YES + +# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or +# disable (NO) the deprecated list. This list is created by putting +# \deprecated commands in the documentation. + +GENERATE_DEPRECATEDLIST= YES + +# The ENABLED_SECTIONS tag can be used to enable conditional +# documentation sections, marked by \if sectionname ... \endif. + +ENABLED_SECTIONS = + +# The MAX_INITIALIZER_LINES tag determines the maximum number of lines +# the initial value of a variable or define consists of for it to appear in +# the documentation. If the initializer consists of more lines than specified +# here it will be hidden. Use a value of 0 to hide initializers completely. +# The appearance of the initializer of individual variables and defines in the +# documentation can be controlled using \showinitializer or \hideinitializer +# command in the documentation regardless of this setting. + +MAX_INITIALIZER_LINES = 30 + +# Set the SHOW_USED_FILES tag to NO to disable the list of files generated +# at the bottom of the documentation of classes and structs. If set to YES the +# list will mention the files that were used to generate the documentation. + +SHOW_USED_FILES = NO + +# If the sources in your project are distributed over multiple directories +# then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy +# in the documentation. The default is NO. + +SHOW_DIRECTORIES = NO + +# Set the SHOW_FILES tag to NO to disable the generation of the Files page. +# This will remove the Files entry from the Quick Index and from the +# Folder Tree View (if specified). The default is YES. + +SHOW_FILES = YES + +# Set the SHOW_NAMESPACES tag to NO to disable the generation of the +# Namespaces page. +# This will remove the Namespaces entry from the Quick Index +# and from the Folder Tree View (if specified). The default is YES. + +SHOW_NAMESPACES = YES + +# The FILE_VERSION_FILTER tag can be used to specify a program or script that +# doxygen should invoke to get the current version for each file (typically from +# the version control system). Doxygen will invoke the program by executing (via +# popen()) the command , where is the value of +# the FILE_VERSION_FILTER tag, and is the name of an input file +# provided by doxygen. Whatever the program writes to standard output +# is used as the file version. See the manual for examples. + +FILE_VERSION_FILTER = + +# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed by +# doxygen. The layout file controls the global structure of the generated output files +# in an output format independent way. The create the layout file that represents +# doxygen's defaults, run doxygen with the -l option. You can optionally specify a +# file name after the option, if omitted DoxygenLayout.xml will be used as the name +# of the layout file. + +LAYOUT_FILE = + +#--------------------------------------------------------------------------- +# configuration options related to warning and progress messages +#--------------------------------------------------------------------------- + +# The QUIET tag can be used to turn on/off the messages that are generated +# by doxygen. Possible values are YES and NO. If left blank NO is used. + +QUIET = NO + +# The WARNINGS tag can be used to turn on/off the warning messages that are +# generated by doxygen. Possible values are YES and NO. If left blank +# NO is used. + +WARNINGS = YES + +# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings +# for undocumented members. If EXTRACT_ALL is set to YES then this flag will +# automatically be disabled. + +WARN_IF_UNDOCUMENTED = YES + +# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for +# potential errors in the documentation, such as not documenting some +# parameters in a documented function, or documenting parameters that +# don't exist or using markup commands wrongly. + +WARN_IF_DOC_ERROR = YES + +# This WARN_NO_PARAMDOC option can be abled to get warnings for +# functions that are documented, but have no documentation for their parameters +# or return value. If set to NO (the default) doxygen will only warn about +# wrong or incomplete parameter documentation, but not about the absence of +# documentation. + +WARN_NO_PARAMDOC = NO + +# The WARN_FORMAT tag determines the format of the warning messages that +# doxygen can produce. The string should contain the file, line, and text +# tags, which will be replaced by the file and line number from which the +# warning originated and the warning text. Optionally the format may contain +# version, which will be replaced by the version of the file (if it could +# be obtained via FILE_VERSION_FILTER) + +WARN_FORMAT = "file:line: text" + +# The WARN_LOGFILE tag can be used to specify a file to which warning +# and error messages should be written. If left blank the output is written +# to stderr. + +WARN_LOGFILE = + +#--------------------------------------------------------------------------- +# configuration options related to the input files +#--------------------------------------------------------------------------- + +# The INPUT tag can be used to specify the files and/or directories that contain +# documented source files. You may enter file names like "myfile.cpp" or +# directories like "/usr/src/myproject". Separate the files or directories +# with spaces. + +INPUT = ../../Sources + +# This tag can be used to specify the character encoding of the source files +# that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is +# also the default input encoding. Doxygen uses libiconv (or the iconv built +# into libc) for the transcoding. See http://www.gnu.org/software/libiconv for +# the list of possible encodings. + +INPUT_ENCODING = UTF-8 + +# If the value of the INPUT tag contains directories, you can use the +# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp +# and *.h) to filter out the source-files in the directories. If left +# blank the following patterns are tested: +# *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx +# *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.py *.f90 + +FILE_PATTERNS = *.cpp \ + *.h + +# The RECURSIVE tag can be used to turn specify whether or not subdirectories +# should be searched for input files as well. Possible values are YES and NO. +# If left blank NO is used. + +RECURSIVE = YES + +# The EXCLUDE tag can be used to specify files and/or directories that should +# excluded from the INPUT source files. This way you can easily exclude a +# subdirectory from a directory tree whose root is specified with the INPUT tag. + +EXCLUDE = + +# The EXCLUDE_SYMLINKS tag can be used select whether or not files or +# directories that are symbolic links (a Unix filesystem feature) are excluded +# from the input. + +EXCLUDE_SYMLINKS = NO + +# If the value of the INPUT tag contains directories, you can use the +# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude +# certain files from those directories. Note that the wildcards are matched +# against the file with absolute path, so to exclude all test directories +# for example use the pattern */test/* + +EXCLUDE_PATTERNS = */Tests/* +EXCLUDE_PATTERNS += */bin/* + +# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names +# (namespaces, classes, functions, etc.) that should be excluded from the +# output. The symbol name can be a fully qualified name, a word, or if the +# wildcard * is used, a substring. Examples: ANamespace, AClass, +# AClass::ANamespace, ANamespace::*Test + +EXCLUDE_SYMBOLS = + +# The EXAMPLE_PATH tag can be used to specify one or more files or +# directories that contain example code fragments that are included (see +# the \include command). + +EXAMPLE_PATH = + +# If the value of the EXAMPLE_PATH tag contains directories, you can use the +# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp +# and *.h) to filter out the source-files in the directories. If left +# blank all files are included. + +EXAMPLE_PATTERNS = * + +# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be +# searched for input files to be used with the \include or \dontinclude +# commands irrespective of the value of the RECURSIVE tag. +# Possible values are YES and NO. If left blank NO is used. + +EXAMPLE_RECURSIVE = NO + +# The IMAGE_PATH tag can be used to specify one or more files or +# directories that contain image that are included in the documentation (see +# the \image command). + +IMAGE_PATH = ../../ + +# The INPUT_FILTER tag can be used to specify a program that doxygen should +# invoke to filter for each input file. Doxygen will invoke the filter program +# by executing (via popen()) the command , where +# is the value of the INPUT_FILTER tag, and is the name of an +# input file. Doxygen will then use the output that the filter program writes +# to standard output. +# If FILTER_PATTERNS is specified, this tag will be +# ignored. + +INPUT_FILTER = + +# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern +# basis. +# Doxygen will compare the file name with each pattern and apply the +# filter if there is a match. +# The filters are a list of the form: +# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further +# info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER +# is applied to all files. + +FILTER_PATTERNS = + +# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using +# INPUT_FILTER) will be used to filter the input files when producing source +# files to browse (i.e. when SOURCE_BROWSER is set to YES). + +FILTER_SOURCE_FILES = NO + +#--------------------------------------------------------------------------- +# configuration options related to source browsing +#--------------------------------------------------------------------------- + +# If the SOURCE_BROWSER tag is set to YES then a list of source files will +# be generated. Documented entities will be cross-referenced with these sources. +# Note: To get rid of all source code in the generated output, make sure also +# VERBATIM_HEADERS is set to NO. + +SOURCE_BROWSER = YES + +# Setting the INLINE_SOURCES tag to YES will include the body +# of functions and classes directly in the documentation. + +INLINE_SOURCES = NO + +# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct +# doxygen to hide any special comment blocks from generated source code +# fragments. Normal C and C++ comments will always remain visible. + +STRIP_CODE_COMMENTS = YES + +# If the REFERENCED_BY_RELATION tag is set to YES +# then for each documented function all documented +# functions referencing it will be listed. + +REFERENCED_BY_RELATION = NO + +# If the REFERENCES_RELATION tag is set to YES +# then for each documented function all documented entities +# called/used by that function will be listed. + +REFERENCES_RELATION = NO + +# If the REFERENCES_LINK_SOURCE tag is set to YES (the default) +# and SOURCE_BROWSER tag is set to YES, then the hyperlinks from +# functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will +# link to the source code. +# Otherwise they will link to the documentation. + +REFERENCES_LINK_SOURCE = YES + +# If the USE_HTAGS tag is set to YES then the references to source code +# will point to the HTML generated by the htags(1) tool instead of doxygen +# built-in source browser. The htags tool is part of GNU's global source +# tagging system (see http://www.gnu.org/software/global/global.html). You +# will need version 4.8.6 or higher. + +USE_HTAGS = NO + +# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen +# will generate a verbatim copy of the header file for each class for +# which an include is specified. Set to NO to disable this. + +VERBATIM_HEADERS = NO + +#--------------------------------------------------------------------------- +# configuration options related to the alphabetical class index +#--------------------------------------------------------------------------- + +# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index +# of all compounds will be generated. Enable this if the project +# contains a lot of classes, structs, unions or interfaces. + +ALPHABETICAL_INDEX = YES + +# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then +# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns +# in which this list will be split (can be a number in the range [1..20]) + +COLS_IN_ALPHA_INDEX = 5 + +# In case all classes in a project start with a common prefix, all +# classes will be put under the same header in the alphabetical index. +# The IGNORE_PREFIX tag can be used to specify one or more prefixes that +# should be ignored while generating the index headers. + +IGNORE_PREFIX = + +#--------------------------------------------------------------------------- +# configuration options related to the HTML output +#--------------------------------------------------------------------------- + +# If the GENERATE_HTML tag is set to YES (the default) Doxygen will +# generate HTML output. + +GENERATE_HTML = YES + +# The HTML_OUTPUT tag is used to specify where the HTML docs will be put. +# If a relative path is entered the value of OUTPUT_DIRECTORY will be +# put in front of it. If left blank `html' will be used as the default path. + +HTML_OUTPUT = html + +# The HTML_FILE_EXTENSION tag can be used to specify the file extension for +# each generated HTML page (for example: .htm,.php,.asp). If it is left blank +# doxygen will generate files with .html extension. + +HTML_FILE_EXTENSION = .html + +# The HTML_HEADER tag can be used to specify a personal HTML header for +# each generated HTML page. If it is left blank doxygen will generate a +# standard header. + +HTML_HEADER = + +# The HTML_FOOTER tag can be used to specify a personal HTML footer for +# each generated HTML page. If it is left blank doxygen will generate a +# standard footer. + +HTML_FOOTER = footer.html + +# The HTML_STYLESHEET tag can be used to specify a user-defined cascading +# style sheet that is used by each HTML page. It can be used to +# fine-tune the look of the HTML output. If the tag is left blank doxygen +# will generate a default style sheet. Note that doxygen will try to copy +# the style sheet file to the HTML output directory, so don't put your own +# stylesheet in the HTML output directory as well, or it will be erased! + +HTML_STYLESHEET = + +# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes, +# files or namespaces will be aligned in HTML using tables. If set to +# NO a bullet list will be used. + +HTML_ALIGN_MEMBERS = YES + +# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML +# documentation will contain sections that can be hidden and shown after the +# page has loaded. For this to work a browser that supports +# JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox +# Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari). + +HTML_DYNAMIC_SECTIONS = NO + +# If the GENERATE_DOCSET tag is set to YES, additional index files +# will be generated that can be used as input for Apple's Xcode 3 +# integrated development environment, introduced with OSX 10.5 (Leopard). +# To create a documentation set, doxygen will generate a Makefile in the +# HTML output directory. Running make will produce the docset in that +# directory and running "make install" will install the docset in +# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find +# it at startup. +# See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html for more information. + +GENERATE_DOCSET = NO + +# When GENERATE_DOCSET tag is set to YES, this tag determines the name of the +# feed. A documentation feed provides an umbrella under which multiple +# documentation sets from a single provider (such as a company or product suite) +# can be grouped. + +DOCSET_FEEDNAME = "Doxygen generated docs" + +# When GENERATE_DOCSET tag is set to YES, this tag specifies a string that +# should uniquely identify the documentation set bundle. This should be a +# reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen +# will append .docset to the name. + +DOCSET_BUNDLE_ID = org.doxygen.Project + +# If the GENERATE_HTMLHELP tag is set to YES, additional index files +# will be generated that can be used as input for tools like the +# Microsoft HTML help workshop to generate a compiled HTML help file (.chm) +# of the generated HTML documentation. + +GENERATE_HTMLHELP = NO + +# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can +# be used to specify the file name of the resulting .chm file. You +# can add a path in front of the file if the result should not be +# written to the html output directory. + +CHM_FILE = + +# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can +# be used to specify the location (absolute path including file name) of +# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run +# the HTML help compiler on the generated index.hhp. + +HHC_LOCATION = + +# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag +# controls if a separate .chi index file is generated (YES) or that +# it should be included in the master .chm file (NO). + +GENERATE_CHI = NO + +# If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING +# is used to encode HtmlHelp index (hhk), content (hhc) and project file +# content. + +CHM_INDEX_ENCODING = + +# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag +# controls whether a binary table of contents is generated (YES) or a +# normal table of contents (NO) in the .chm file. + +BINARY_TOC = NO + +# The TOC_EXPAND flag can be set to YES to add extra items for group members +# to the contents of the HTML help documentation and to the tree view. + +TOC_EXPAND = NO + +# If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and QHP_VIRTUAL_FOLDER +# are set, an additional index file will be generated that can be used as input for +# Qt's qhelpgenerator to generate a Qt Compressed Help (.qch) of the generated +# HTML documentation. + +GENERATE_QHP = NO + +# If the QHG_LOCATION tag is specified, the QCH_FILE tag can +# be used to specify the file name of the resulting .qch file. +# The path specified is relative to the HTML output folder. + +QCH_FILE = + +# The QHP_NAMESPACE tag specifies the namespace to use when generating +# Qt Help Project output. For more information please see +# http://doc.trolltech.com/qthelpproject.html#namespace + +QHP_NAMESPACE = + +# The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating +# Qt Help Project output. For more information please see +# http://doc.trolltech.com/qthelpproject.html#virtual-folders + +QHP_VIRTUAL_FOLDER = doc + +# If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to add. +# For more information please see +# http://doc.trolltech.com/qthelpproject.html#custom-filters + +QHP_CUST_FILTER_NAME = + +# The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the custom filter to add.For more information please see +# Qt Help Project / Custom Filters. + +QHP_CUST_FILTER_ATTRS = + +# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this project's +# filter section matches. +# Qt Help Project / Filter Attributes. + +QHP_SECT_FILTER_ATTRS = + +# If the GENERATE_QHP tag is set to YES, the QHG_LOCATION tag can +# be used to specify the location of Qt's qhelpgenerator. +# If non-empty doxygen will try to run qhelpgenerator on the generated +# .qhp file. + +QHG_LOCATION = + +# The DISABLE_INDEX tag can be used to turn on/off the condensed index at +# top of each HTML page. The value NO (the default) enables the index and +# the value YES disables it. + +DISABLE_INDEX = NO + +# This tag can be used to set the number of enum values (range [1..20]) +# that doxygen will group on one line in the generated HTML documentation. + +ENUM_VALUES_PER_LINE = 4 + +# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index +# structure should be generated to display hierarchical information. +# If the tag value is set to FRAME, a side panel will be generated +# containing a tree-like index structure (just like the one that +# is generated for HTML Help). For this to work a browser that supports +# JavaScript, DHTML, CSS and frames is required (for instance Mozilla 1.0+, +# Netscape 6.0+, Internet explorer 5.0+, or Konqueror). Windows users are +# probably better off using the HTML help feature. Other possible values +# for this tag are: HIERARCHIES, which will generate the Groups, Directories, +# and Class Hierarchy pages using a tree view instead of an ordered list; +# ALL, which combines the behavior of FRAME and HIERARCHIES; and NONE, which +# disables this behavior completely. For backwards compatibility with previous +# releases of Doxygen, the values YES and NO are equivalent to FRAME and NONE +# respectively. + +GENERATE_TREEVIEW = YES + +# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be +# used to set the initial width (in pixels) of the frame in which the tree +# is shown. + +TREEVIEW_WIDTH = 250 + +# Use this tag to change the font size of Latex formulas included +# as images in the HTML documentation. The default is 10. Note that +# when you change the font size after a successful doxygen run you need +# to manually remove any form_*.png images from the HTML output directory +# to force them to be regenerated. + +FORMULA_FONTSIZE = 10 + +#--------------------------------------------------------------------------- +# configuration options related to the LaTeX output +#--------------------------------------------------------------------------- + +# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will +# generate Latex output. + +GENERATE_LATEX = NO + +# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. +# If a relative path is entered the value of OUTPUT_DIRECTORY will be +# put in front of it. If left blank `latex' will be used as the default path. + +LATEX_OUTPUT = latex + +# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be +# invoked. If left blank `latex' will be used as the default command name. + +LATEX_CMD_NAME = latex + +# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to +# generate index for LaTeX. If left blank `makeindex' will be used as the +# default command name. + +MAKEINDEX_CMD_NAME = makeindex + +# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact +# LaTeX documents. This may be useful for small projects and may help to +# save some trees in general. + +COMPACT_LATEX = NO + +# The PAPER_TYPE tag can be used to set the paper type that is used +# by the printer. Possible values are: a4, a4wide, letter, legal and +# executive. If left blank a4wide will be used. + +PAPER_TYPE = a4wide + +# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX +# packages that should be included in the LaTeX output. + +EXTRA_PACKAGES = + +# The LATEX_HEADER tag can be used to specify a personal LaTeX header for +# the generated latex document. The header should contain everything until +# the first chapter. If it is left blank doxygen will generate a +# standard header. Notice: only use this tag if you know what you are doing! + +LATEX_HEADER = + +# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated +# is prepared for conversion to pdf (using ps2pdf). The pdf file will +# contain links (just like the HTML output) instead of page references +# This makes the output suitable for online browsing using a pdf viewer. + +PDF_HYPERLINKS = NO + +# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of +# plain latex in the generated Makefile. Set this option to YES to get a +# higher quality PDF documentation. + +USE_PDFLATEX = YES + +# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode. +# command to the generated LaTeX files. This will instruct LaTeX to keep +# running if errors occur, instead of asking the user for help. +# This option is also used when generating formulas in HTML. + +LATEX_BATCHMODE = NO + +# If LATEX_HIDE_INDICES is set to YES then doxygen will not +# include the index chapters (such as File Index, Compound Index, etc.) +# in the output. + +LATEX_HIDE_INDICES = NO + +#--------------------------------------------------------------------------- +# configuration options related to the RTF output +#--------------------------------------------------------------------------- + +# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output +# The RTF output is optimized for Word 97 and may not look very pretty with +# other RTF readers or editors. + +GENERATE_RTF = NO + +# The RTF_OUTPUT tag is used to specify where the RTF docs will be put. +# If a relative path is entered the value of OUTPUT_DIRECTORY will be +# put in front of it. If left blank `rtf' will be used as the default path. + +RTF_OUTPUT = rtf + +# If the COMPACT_RTF tag is set to YES Doxygen generates more compact +# RTF documents. This may be useful for small projects and may help to +# save some trees in general. + +COMPACT_RTF = NO + +# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated +# will contain hyperlink fields. The RTF file will +# contain links (just like the HTML output) instead of page references. +# This makes the output suitable for online browsing using WORD or other +# programs which support those fields. +# Note: wordpad (write) and others do not support links. + +RTF_HYPERLINKS = NO + +# Load stylesheet definitions from file. Syntax is similar to doxygen's +# config file, i.e. a series of assignments. You only have to provide +# replacements, missing definitions are set to their default value. + +RTF_STYLESHEET_FILE = + +# Set optional variables used in the generation of an rtf document. +# Syntax is similar to doxygen's config file. + +RTF_EXTENSIONS_FILE = + +#--------------------------------------------------------------------------- +# configuration options related to the man page output +#--------------------------------------------------------------------------- + +# If the GENERATE_MAN tag is set to YES (the default) Doxygen will +# generate man pages + +GENERATE_MAN = NO + +# The MAN_OUTPUT tag is used to specify where the man pages will be put. +# If a relative path is entered the value of OUTPUT_DIRECTORY will be +# put in front of it. If left blank `man' will be used as the default path. + +MAN_OUTPUT = man + +# The MAN_EXTENSION tag determines the extension that is added to +# the generated man pages (default is the subroutine's section .3) + +MAN_EXTENSION = .3 + +# If the MAN_LINKS tag is set to YES and Doxygen generates man output, +# then it will generate one additional man file for each entity +# documented in the real man page(s). These additional files +# only source the real man page, but without them the man command +# would be unable to find the correct page. The default is NO. + +MAN_LINKS = NO + +#--------------------------------------------------------------------------- +# configuration options related to the XML output +#--------------------------------------------------------------------------- + +# If the GENERATE_XML tag is set to YES Doxygen will +# generate an XML file that captures the structure of +# the code including all documentation. + +GENERATE_XML = NO + +# The XML_OUTPUT tag is used to specify where the XML pages will be put. +# If a relative path is entered the value of OUTPUT_DIRECTORY will be +# put in front of it. If left blank `xml' will be used as the default path. + +XML_OUTPUT = xml + +# The XML_SCHEMA tag can be used to specify an XML schema, +# which can be used by a validating XML parser to check the +# syntax of the XML files. + +XML_SCHEMA = + +# The XML_DTD tag can be used to specify an XML DTD, +# which can be used by a validating XML parser to check the +# syntax of the XML files. + +XML_DTD = + +# If the XML_PROGRAMLISTING tag is set to YES Doxygen will +# dump the program listings (including syntax highlighting +# and cross-referencing information) to the XML output. Note that +# enabling this will significantly increase the size of the XML output. + +XML_PROGRAMLISTING = YES + +#--------------------------------------------------------------------------- +# configuration options for the AutoGen Definitions output +#--------------------------------------------------------------------------- + +# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will +# generate an AutoGen Definitions (see autogen.sf.net) file +# that captures the structure of the code including all +# documentation. Note that this feature is still experimental +# and incomplete at the moment. + +GENERATE_AUTOGEN_DEF = NO + +#--------------------------------------------------------------------------- +# configuration options related to the Perl module output +#--------------------------------------------------------------------------- + +# If the GENERATE_PERLMOD tag is set to YES Doxygen will +# generate a Perl module file that captures the structure of +# the code including all documentation. Note that this +# feature is still experimental and incomplete at the +# moment. + +GENERATE_PERLMOD = NO + +# If the PERLMOD_LATEX tag is set to YES Doxygen will generate +# the necessary Makefile rules, Perl scripts and LaTeX code to be able +# to generate PDF and DVI output from the Perl module output. + +PERLMOD_LATEX = NO + +# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be +# nicely formatted so it can be parsed by a human reader. +# This is useful +# if you want to understand what is going on. +# On the other hand, if this +# tag is set to NO the size of the Perl module output will be much smaller +# and Perl will parse it just the same. + +PERLMOD_PRETTY = YES + +# The names of the make variables in the generated doxyrules.make file +# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. +# This is useful so different doxyrules.make files included by the same +# Makefile don't overwrite each other's variables. + +PERLMOD_MAKEVAR_PREFIX = + +#--------------------------------------------------------------------------- +# Configuration options related to the preprocessor +#--------------------------------------------------------------------------- + +# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will +# evaluate all C-preprocessor directives found in the sources and include +# files. + +ENABLE_PREPROCESSING = YES + +# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro +# names in the source code. If set to NO (the default) only conditional +# compilation will be performed. Macro expansion can be done in a controlled +# way by setting EXPAND_ONLY_PREDEF to YES. + +MACRO_EXPANSION = NO + +# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES +# then the macro expansion is limited to the macros specified with the +# PREDEFINED and EXPAND_AS_DEFINED tags. + +EXPAND_ONLY_PREDEF = NO + +# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files +# in the INCLUDE_PATH (see below) will be search if a #include is found. + +SEARCH_INCLUDES = YES + +# The INCLUDE_PATH tag can be used to specify one or more directories that +# contain include files that are not input files but should be processed by +# the preprocessor. + +INCLUDE_PATH = + +# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard +# patterns (like *.h and *.hpp) to filter out the header-files in the +# directories. If left blank, the patterns specified with FILE_PATTERNS will +# be used. + +INCLUDE_FILE_PATTERNS = + +# The PREDEFINED tag can be used to specify one or more macro names that +# are defined before the preprocessor is started (similar to the -D option of +# gcc). The argument of the tag is a list of macros of the form: name +# or name=definition (no spaces). If the definition and the = are +# omitted =1 is assumed. To prevent a macro definition from being +# undefined via #undef or recursively expanded use the := operator +# instead of the = operator. + +PREDEFINED = + +# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then +# this tag can be used to specify a list of macro names that should be expanded. +# The macro definition that is found in the sources will be used. +# Use the PREDEFINED tag if you want to use a different macro definition. + +EXPAND_AS_DEFINED = + +# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then +# doxygen's preprocessor will remove all function-like macros that are alone +# on a line, have an all uppercase name, and do not end with a semicolon. Such +# function macros are typically used for boiler-plate code, and will confuse +# the parser if not removed. + +SKIP_FUNCTION_MACROS = YES + +#--------------------------------------------------------------------------- +# Configuration::additions related to external references +#--------------------------------------------------------------------------- + +# The TAGFILES option can be used to specify one or more tagfiles. +# Optionally an initial location of the external documentation +# can be added for each tagfile. The format of a tag file without +# this location is as follows: +# +# TAGFILES = file1 file2 ... +# Adding location for the tag files is done as follows: +# +# TAGFILES = file1=loc1 "file2 = loc2" ... +# where "loc1" and "loc2" can be relative or absolute paths or +# URLs. If a location is present for each tag, the installdox tool +# does not have to be run to correct the links. +# Note that each tag file must have a unique name +# (where the name does NOT include the path) +# If a tag file is not located in the directory in which doxygen +# is run, you must also specify the path to the tagfile here. + +TAGFILES = + +# When a file name is specified after GENERATE_TAGFILE, doxygen will create +# a tag file that is based on the input files it reads. + +GENERATE_TAGFILE = + +# If the ALLEXTERNALS tag is set to YES all external classes will be listed +# in the class index. If set to NO only the inherited external classes +# will be listed. + +ALLEXTERNALS = NO + +# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed +# in the modules index. If set to NO, only the current project's groups will +# be listed. + +EXTERNAL_GROUPS = YES + +# The PERL_PATH should be the absolute path and name of the perl script +# interpreter (i.e. the result of `which perl'). + +PERL_PATH = /usr/bin/perl + +#--------------------------------------------------------------------------- +# Configuration options related to the dot tool +#--------------------------------------------------------------------------- + +# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will +# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base +# or super classes. Setting the tag to NO turns the diagrams off. Note that +# this option is superseded by the HAVE_DOT option below. This is only a +# fallback. It is recommended to install and use dot, since it yields more +# powerful graphs. + +CLASS_DIAGRAMS = YES + +# You can define message sequence charts within doxygen comments using the \msc +# command. Doxygen will then run the mscgen tool (see +# http://www.mcternan.me.uk/mscgen/) to produce the chart and insert it in the +# documentation. The MSCGEN_PATH tag allows you to specify the directory where +# the mscgen tool resides. If left empty the tool is assumed to be found in the +# default search path. + +MSCGEN_PATH = + +# If set to YES, the inheritance and collaboration graphs will hide +# inheritance and usage relations if the target is undocumented +# or is not a class. + +HIDE_UNDOC_RELATIONS = NO + +# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is +# available from the path. This tool is part of Graphviz, a graph visualization +# toolkit from AT&T and Lucent Bell Labs. The other options in this section +# have no effect if this option is set to NO (the default) + +HAVE_DOT = NO + +# By default doxygen will write a font called FreeSans.ttf to the output +# directory and reference it in all dot files that doxygen generates. This +# font does not include all possible unicode characters however, so when you need +# these (or just want a differently looking font) you can specify the font name +# using DOT_FONTNAME. You need need to make sure dot is able to find the font, +# which can be done by putting it in a standard location or by setting the +# DOTFONTPATH environment variable or by setting DOT_FONTPATH to the directory +# containing the font. + +DOT_FONTNAME = FreeSans + +# The DOT_FONTSIZE tag can be used to set the size of the font of dot graphs. +# The default size is 10pt. + +DOT_FONTSIZE = 10 + +# By default doxygen will tell dot to use the output directory to look for the +# FreeSans.ttf font (which doxygen will put there itself). If you specify a +# different font using DOT_FONTNAME you can set the path where dot +# can find it using this tag. + +DOT_FONTPATH = + +# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen +# will generate a graph for each documented class showing the direct and +# indirect inheritance relations. Setting this tag to YES will force the +# the CLASS_DIAGRAMS tag to NO. + +CLASS_GRAPH = YES + +# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen +# will generate a graph for each documented class showing the direct and +# indirect implementation dependencies (inheritance, containment, and +# class references variables) of the class with other documented classes. + +COLLABORATION_GRAPH = YES + +# If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen +# will generate a graph for groups, showing the direct groups dependencies + +GROUP_GRAPHS = YES + +# If the UML_LOOK tag is set to YES doxygen will generate inheritance and +# collaboration diagrams in a style similar to the OMG's Unified Modeling +# Language. + +UML_LOOK = NO + +# If set to YES, the inheritance and collaboration graphs will show the +# relations between templates and their instances. + +TEMPLATE_RELATIONS = NO + +# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT +# tags are set to YES then doxygen will generate a graph for each documented +# file showing the direct and indirect include dependencies of the file with +# other documented files. + +INCLUDE_GRAPH = YES + +# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and +# HAVE_DOT tags are set to YES then doxygen will generate a graph for each +# documented header file showing the documented files that directly or +# indirectly include this file. + +INCLUDED_BY_GRAPH = YES + +# If the CALL_GRAPH and HAVE_DOT options are set to YES then +# doxygen will generate a call dependency graph for every global function +# or class method. Note that enabling this option will significantly increase +# the time of a run. So in most cases it will be better to enable call graphs +# for selected functions only using the \callgraph command. + +CALL_GRAPH = NO + +# If the CALLER_GRAPH and HAVE_DOT tags are set to YES then +# doxygen will generate a caller dependency graph for every global function +# or class method. Note that enabling this option will significantly increase +# the time of a run. So in most cases it will be better to enable caller +# graphs for selected functions only using the \callergraph command. + +CALLER_GRAPH = NO + +# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen +# will graphical hierarchy of all classes instead of a textual one. + +GRAPHICAL_HIERARCHY = YES + +# If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES +# then doxygen will show the dependencies a directory has on other directories +# in a graphical way. The dependency relations are determined by the #include +# relations between the files in the directories. + +DIRECTORY_GRAPH = YES + +# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images +# generated by dot. Possible values are png, jpg, or gif +# If left blank png will be used. + +DOT_IMAGE_FORMAT = png + +# The tag DOT_PATH can be used to specify the path where the dot tool can be +# found. If left blank, it is assumed the dot tool can be found in the path. + +DOT_PATH = + +# The DOTFILE_DIRS tag can be used to specify one or more directories that +# contain dot files that are included in the documentation (see the +# \dotfile command). + +DOTFILE_DIRS = + +# The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of +# nodes that will be shown in the graph. If the number of nodes in a graph +# becomes larger than this value, doxygen will truncate the graph, which is +# visualized by representing a node as a red box. Note that doxygen if the +# number of direct children of the root node in a graph is already larger than +# DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note +# that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH. + +DOT_GRAPH_MAX_NODES = 50 + +# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the +# graphs generated by dot. A depth value of 3 means that only nodes reachable +# from the root by following a path via at most 3 edges will be shown. Nodes +# that lay further from the root node will be omitted. Note that setting this +# option to 1 or 2 may greatly reduce the computation time needed for large +# code bases. Also note that the size of a graph can be further restricted by +# DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction. + +MAX_DOT_GRAPH_DEPTH = 0 + +# Set the DOT_TRANSPARENT tag to YES to generate images with a transparent +# background. This is disabled by default, because dot on Windows does not +# seem to support this out of the box. Warning: Depending on the platform used, +# enabling this option may lead to badly anti-aliased labels on the edges of +# a graph (i.e. they become hard to read). + +DOT_TRANSPARENT = NO + +# Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output +# files in one run (i.e. multiple -o and -T options on the command line). This +# makes dot run faster, but since only newer versions of dot (>1.8.10) +# support this, this feature is disabled by default. + +DOT_MULTI_TARGETS = NO + +# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will +# generate a legend page explaining the meaning of the various boxes and +# arrows in the dot generated graphs. + +GENERATE_LEGEND = YES + +# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will +# remove the intermediate dot files that are used to generate +# the various graphs. + +DOT_CLEANUP = YES + +#--------------------------------------------------------------------------- +# Options related to the search engine +#--------------------------------------------------------------------------- + +# The SEARCHENGINE tag specifies whether or not a search engine should be +# used. If set to NO the values of all tags below this one will be ignored. + +SEARCHENGINE = NO diff --git a/Documentation/doxygen/footer.html b/Documentation/doxygen/footer.html new file mode 100755 index 0000000..e163833 --- /dev/null +++ b/Documentation/doxygen/footer.html @@ -0,0 +1,8 @@ + +

+

Generated on $datetime at   + +Code#0 by Doxygen version $doxygenversion
+

+ + \ No newline at end of file diff --git a/Documentation/doxygen/images/CodeFirst.png b/Documentation/doxygen/images/CodeFirst.png new file mode 100644 index 0000000000000000000000000000000000000000..7583537f5890eff06a48af575f4d1679ccc49e34 GIT binary patch literal 4677 zcmbVQ2UJr_w@xTAARVNa7!?pnCA0tnNs!{D7b%LSQ9}}vNK>REDguHCN>S;cQoT}? zDqhN!stAY(h>9WzB8nB?!M5&u>woRfTIZZOGvDksdw+8#Cmif7MTHfGK_HN*wH3(; zc+!B23WWgopt<4&;334e^5B9%o254{Fz75AQVnTv z)7>!RFgze2h|VL!!h#q~EOXc{pdHyUWY(pZM z!aB?|fdiKQa3P5OTP&0NGfY6hP+?>?3WG#%xbz)JqyEOR4|5pbmD8vwI)ffWXY#lJ z7V{g+_G9r_TtC)-Bl`F7e^LO1*4Fm7j(=%OP|$A`T%JV;;Kt8@{7W>~C7ex1InlYS z!yGEzA_OpV+lDu6Jdr~u^H>}g7K`y~p&Wjh48vlOSeT|Qnd;BnaAM~_rqD@b9^C{E ztQ!`A#vm{l7c2&k#^7}fb^&)Z`UljOMf3Lw|0h%zf!1+BWAVBMcpc0xpz#|DBn^$s zBmb{p8Wr!u;slWam;HmtzH}6u=?jPb4kVt)Vz4-XV!%3`fA(7wi4Gi=k3Rz#;5u0n zVAd8yJ&d8A9s-NRd^gwD7H`eu^2kgo-I`Tu*OF7H(dcQzX^}d1Xzv((AnvCoL3-_ z$dEP3+$HSc;sL>{F4nSlCMPE&H)%B7ym`}$EhHosBQTZfb?D5r*w(n4(vM<|+9w0P zmFG=(E!pmMZ5^FlvY%HERiCtNt*qd_iWo^<{rGn7_{W5|siNC;uzW_XR6+9H}_aNHO3>RpIgDFagCOwaWzz((^qffO&Qm0y@LNVS^A6Iq| zlGRo}ud&|0yjPmEse9m}>G>^u4tCj_WYu8Ns>We$%&C?>!JPyUrDSg4Vjce`v1-B1 zvejp{S=Oeg7}Y{V6{`bADr$N&chxEC22_{W=G5k!9I1UX+g0a!#jWP;+`wCvZBnvr zr(7T+&;`E&|9d4hlshMDKCdm+0mc|gONczY6=s>LN-wlb_1Ut^jV2_mPCEm)aC)As zpi}$TX{EaA>Zm%edZt3Yn#iGLC6b1H{?m@Q;J))ZU8C{@{v?kG)!j$C)$Q}|3d?9t z%Yhyn*qqh8YL|y+yqh0^=*mM6kzn4<5qFwGmtHGcu7COX@w4f%FYI%Ua+@OG&AUFh zvJWL|6vCK@VRwz!`TFYk_Tv_8jH26hE+r=U4CMEvZ?~p=Se)%j{rijeGN|3miZFF6 z{C33JYZVy@uo1ACDYI5-wf-=FS2b*{&u2|T&a@SrT7@w36GxM9yX5S21R0hYNmqU3k zc)QSGCy+@K-ie<*Dj3 z_m3)O$9bU5_%_D`9Rf)n-j(d}r1OM|C?vS$=*O|+;%deb1kkJ1m-nvzaUSb5kfR%T z&P8HZr}cY&cx+AR(qkxCz`(aZ*EsCRxAo=;&5O$E`x`mdrgdR&p5*R5r`^+=g&L@E zDen+9j-61qy|C=QxoT};{Psn)7G})&)=RgKi*I7QnO5&gRl9g6S>fJF9i=m=9RSj- z8nazx%PW9^iQQQzq%~HOI}Z{LpBWtf~{Dum~vD0vilhrMepKEvQJy#vKNxb&e zXw}<<_U&nj4PkHK6OCMroZXT5z{w`vy%%>kuhvam_n%#fHV!ur6W0>i4vBCR6egG% zBHM4*iAxOq*>?_+Qw%QMo0T$GSv^)EaJZ4$B_@_qI+vyG7`r%8Kj5njSA2u;x-rJL zr_?U5A!F7Yx&RgsPayN@vK~KLYWL|*i%}wAhM+ssZL3bblppNN(GP#(D1g`2zUw>e zDDdRnt5L@Cbo-4?wDR=ij}O^&(p-x_RZ&+f^kAGT8q04! z3%TY|m-wvv4AC$lHRHT?!_O0_m` ztDE}F$LREfqau$1@}x$J!>?@Bx1FD zwt$LY%pZNDCJ`n&eZSm!ue}IzyG7}GEVxQY3!E-&*)~B)vcO0bglFO-Uk(?CXC#ae z+}glfPfWB%wWb##4z}#~aBU2XUoJ-8ef|2uHLuM1cM{m5fJcI9daofzLZM|*-`0mS z?w;K#{VgR+R=(<`d|5KUm)yh76{l&l594V&%s!?{8L&FfaD|vg8jJfgaCC(RmyO@Q zXMWZB8m>dIi+T3zTGW>}DDQg71d;&p?x{chhB^dWNPF$sV8@KprkF}CcNI^hNA&b2eI^rt$ z)o=0B7o$EYTLMXVKs36T#l^Cjz6b@QB#+S=B|AXUwJCD)~VOHuCkv}XP)?p^sbtCT+E3JuQzxa zo%R^zb>k|p7rZ^kB0(-gFUWH=aQhe1tT3xPuMQMjDQ9|04y9@zn&h3UF_7eGMo(b; zm8{SYicijCG=m@#*L0W595!hXBR{Ut*Do*xbK?P$tuEf1rPz|nskRz(eKH3yUvMO( zT(@+MJ_{KHcC#Yz)=NY&sN+mWLNP?lU#`$ct5{0Xj1ocoa_ll8K_uGcn&-%};lr;c zybCN`TkID>J_jT!ZGkQKj?G*zm146gj(jR4f9*bU?u z{7j{e*qwNG*FL*|X?F)F;&Z;Van}Pk7z#IoXA@_dWp+BrgUY??D`(zrmP0n|z8xd~ zMrXU!&X1{Z+IQ7` z#wqZ1QM_dST5i6-{C|afn!8$4q8VDSK*TzlV2vYhcCKVedIx0)@ zC50?K4jL0Iw#mdERTDBT;Li2e6j^5^TK1p0z3n|SacOGf^pq%1A8EFXBW%i_sv{YT^4tfK%on;q_R=NFi_q{D&exL!zt3f~tW zUNE>fT1_VA6U@Cg8v%Q-w72x}7K&D8o|t~Vz~7G1gKh)4hIOm7w1q+ox5?KnRw4V` zdk)5Im2mOkJqj|b_)8+Wgnw7_Eq7>>WcSo&AI;3Sx?enmq_#UKnqq}g0yz?3^J~Nh z6WCEHLh!Y8_xyzVA}ljkS|lx$E)J9F{>WYb0x+vNOJj@DoP(R2ijGQy(4o3qlgXtQ zvW|Jm3qo|t9lO*+*E1?s`LqA-2EV}7tR00erXTzI>7!updh7lXGn;&9Vq=Bo-}moN zce^=-;uR{|rZ)3+hA10-_Pry0eJo);KPuivY#4F)y~-znt>70+m-#b?yoTD7@3U2NFh+@?h&AtTL2l6!BVxfXE z$K%OrumU5G>O>uHd;kb9RNYgz_dft@kuJO z8K;jlI2|0OOA64!g(5$3Df;rsab@>=R6Ft{o4l-Nb_hP{phd|GA{%B9bfepe^LR^(9+dlZNf0Y>hT0gT#?On(` z<9ddqCPDXvQ3v^EM|e~vVLR^X<%65|t(NZ>-d3_2EUnoKF3ZY!OA!<7I3Hz7x;2=u zDCf}Gp>nceGU$Gpqj6V4NkCC&@QJo)F#lM*kaUAq?Cs^JJsGXf>Rs@TI9U3cMnzh$ z$!SFiC1zsbt|r@2-YZk#lHVtW7YT#^I5k|*1r82<8)pY^kxk$Nxejv?GgUr?zLe>% aZ-QD)pYCu~^Gi1V=&`o2BUKU(#r_8}z{j5e literal 0 HcmV?d00001 diff --git a/README.md b/README.md new file mode 100644 index 0000000..2a08ace --- /dev/null +++ b/README.md @@ -0,0 +1,22 @@ +[![Build Status](https://codefirst.ddns.net/api/badges/yorick.geoffre/project-/status.svg)](https://codefirst.ddns.net/yorick.geoffre/project-) +[![Quality Gate Status](https://codefirst.ddns.net/sonar/api/project_badges/measure?project=yorick.geoffre%3Aproject-&metric=alert_status)](https://codefirst.ddns.net/sonar/dashboard?id=yorick.geoffre%3Aproject-) +[![Bugs](https://codefirst.ddns.net/sonar/api/project_badges/measure?project=yorick.geoffre%3Aproject-&metric=bugs)](https://codefirst.ddns.net/sonar/dashboard?id=yorick.geoffre%3Aproject-) +[![Code Smells](https://codefirst.ddns.net/sonar/api/project_badges/measure?project=yorick.geoffre%3Aproject-&metric=code_smells)](https://codefirst.ddns.net/sonar/dashboard?id=yorick.geoffre%3Aproject-) +[![Coverage](https://codefirst.ddns.net/sonar/api/project_badges/measure?project=yorick.geoffre%3Aproject-&metric=coverage)](https://codefirst.ddns.net/sonar/dashboard?id=yorick.geoffre%3Aproject-) +[![Duplicated Lines (%)](https://codefirst.ddns.net/sonar/api/project_badges/measure?project=yorick.geoffre%3Aproject-&metric=duplicated_lines_density)](https://codefirst.ddns.net/sonar/dashboard?id=yorick.geoffre%3Aproject-) +[![Lines of Code](https://codefirst.ddns.net/sonar/api/project_badges/measure?project=yorick.geoffre%3Aproject-&metric=ncloc)](https://codefirst.ddns.net/sonar/dashboard?id=yorick.geoffre%3Aproject-) +[![Maintainability Rating](https://codefirst.ddns.net/sonar/api/project_badges/measure?project=yorick.geoffre%3Aproject-&metric=sqale_rating)](https://codefirst.ddns.net/sonar/dashboard?id=yorick.geoffre%3Aproject-) +[![Reliability Rating](https://codefirst.ddns.net/sonar/api/project_badges/measure?project=yorick.geoffre%3Aproject-&metric=reliability_rating)](https://codefirst.ddns.net/sonar/dashboard?id=yorick.geoffre%3Aproject-) +[![Security Rating](https://codefirst.ddns.net/sonar/api/project_badges/measure?project=yorick.geoffre%3Aproject-&metric=security_rating)](https://codefirst.ddns.net/sonar/dashboard?id=yorick.geoffre%3Aproject-) +[![Technical Debt](https://codefirst.ddns.net/sonar/api/project_badges/measure?project=yorick.geoffre%3Aproject-&metric=sqale_index)](https://codefirst.ddns.net/sonar/dashboard?id=yorick.geoffre%3Aproject-) +[![Vulnerabilities](https://codefirst.ddns.net/sonar/api/project_badges/measure?project=yorick.geoffre%3Aproject-&metric=vulnerabilities)](https://codefirst.ddns.net/sonar/dashboard?id=yorick.geoffre%3Aproject-) + + +# project- + +Welcome on the project- project! + + + +_Generated with a_ **Code#0** _template_ + \ No newline at end of file diff --git a/Sources/Applications/Tests/helloLibrary/main.cpp b/Sources/Applications/Tests/helloLibrary/main.cpp new file mode 100755 index 0000000..d308e1c --- /dev/null +++ b/Sources/Applications/Tests/helloLibrary/main.cpp @@ -0,0 +1,12 @@ +#include "helloLibrary/Class1.h" +#include + +using namespace helloLibrary; +using namespace std; + +int main() +{ + Class1 c("Hello World!"); + cout< $(BINDIR)/build.log +# ld -o $(BINDIR)/$(DLL)$(SUFFIX).so -shared $(OBJDIR)/*.o \ No newline at end of file diff --git a/Sources/_Linux/makefile.lnx b/Sources/_Linux/makefile.lnx new file mode 100755 index 0000000..c3ac875 --- /dev/null +++ b/Sources/_Linux/makefile.lnx @@ -0,0 +1,12 @@ +debug : + cd helloLibrary && make -f makefile.lnx CONFIG=debug + cd Applications/Tests/helloLibrary && make -f makefile.lnx CONFIG=debug + +release : + cd helloLibrary && make -f makefile.lnx CONFIG=release + cd Applications/Tests/helloLibrary && make -f makefile.lnx CONFIG=release + # cd Documentation && make -f makefile + +clean : + cd helloLibraryh && make clean -f makefile.lnx + cd Applications/Tests/helloLibrary && make clean -f makefile.lnx diff --git a/Sources/bin/.gitkeep b/Sources/bin/.gitkeep new file mode 100644 index 0000000..e69de29 diff --git a/Sources/bin/build.log b/Sources/bin/build.log new file mode 100644 index 0000000..e69de29 diff --git a/Sources/bin/helloLibrary_Tests b/Sources/bin/helloLibrary_Tests new file mode 100755 index 0000000000000000000000000000000000000000..b8b2b64924a8529429da4ecf494bd525f66f2a44 GIT binary patch literal 65248 zcmeHP3ve98nVyyGU_(Gl2w(`{wK2xwA??bRY+(ay?1A-JHZro36e%)VNh517tKDTE zesEDvV3g8&F{pAOags|#m0aC9kE_#N1>#(RO9T=-2MG$f)Hw-9bV-gHB_t>niYS4L z?)$s{-klw-uq@kLU8={Pnf`kE`}^;&AJenbqv!wl>pz`i7`|%5FsiV>3%mavhB45; z3?aj~40{B-WwmU)!@S$P>rRR--+bk;A|gAhkb!0GG(WJjJc;0k%i|2j3lU8_ToRjQ zW$nFL1~_@`g>OV*5dXy*nTGI!QgQ@*U2?S15CY3~FZAWXU!w;BHJ>g=@ay`6R{Yh|MyUVA%lk@kMU1_+ngD;kyo z%j(Qz)3L-Zj`!MIcdN8_K3^y7-n_OgE0@?4OLSSWM0XMiz4jt(?+6S`;SMA<~!UvlPQmKr5gX&V zq>hN1?7UCWi*6vh`;nwzz8Ts7OzNJe zBl+(~^52f+bEElfPmp`ga>be0Oit#X%8wzZ(Y*P@L_kE86Na7NV(p~JQsq1DT&28F z{*5}1AXOxP%vlW^HA@ZF#}758ko#n$fO8=?>0AveT=U=aba!pd(g%@Rq;GMag8}C$ z9BP)rG3EzKd=qxeaoCx3?!*#E07rl{fkGdy|_O8!i@O-fI^ z{uV@D?DIL1LfDD;jvYN0o;t7LNZHmLopfHpVrhh@oS%pQNTOVB|7H0p4J~MWtLp`_ zF@qm0m7jF%8$$zeA_v>Xo$JY7!JLE+Cxi~`q&H*G;RNYWD-8zkdAeq4c&48DHj+=& zNuVWz6!@imU`eI>XEwyk-I^rxq6j#$>_=)nU_T*fKOXz*u zMudfeIdaVi==-MvH3Jw*B&!;YJZ}z9(9&l%GaM;w8-`>3IHTxj4!++44od4ak-`?l zJdY9#IsbvKK|X$7b9NarSJuORF7@)AI z%!8=IKf+kCjN64jR2-GzQ7XG*;wab?H&6;5T*mU|a}%^Gxi}h)<+nX2MExrI(*!MU zmU)uSpQb3p7!%aS*_XaC=PR=7x$<=SRZ{0O;v(AL{m)Pxx&}VV%K0mmuw?F~#pKU1 z=Ycn-r#<5X_1CSCT#RRQo;hBXjZajsXq(P1q%BH>(Hd2T*pSG`bSBV)WX!D`gBo>U z8$*?9-=e)AFjn|#9v^jg33>hgSH@ss^C0?BAKE63cWvXS`xDLRSA*vBvV{zM0M+LF z3MDw2KfYCm%ZL#vM`YtXW>V`VE8`_Aha>y@4jVNOZxUDFGd0&j+hOM)$?$sfaLt2P zl~@0J~Gq~>Vb^I!}{@=u1T$b&>Ih_K`iL@0XM zpU{d6Pg0m}g@v{er&eS^&AkP&+$IJn45vnF9_%BhzC@ykKC#Y~h{BQlK#EQWpQMvB zQcM_hC8RKfEEeO~KpZh}-I!QKa;O_~fBxV{C@Bi!d<>s?OayUNCPsj!3WH7p@dd#j z7_E5_ZJ9gB0~Df;H!(m-WetwYdQsYM5m$uvs2OM3Q6$MgNK_=_Ve z-+P=NkfB-n7mxpi@FI6#@Q(kY&ydni9kR_IBex18L-58~f{0>=MGtFh6^o4<|4;rG>Fa<==ulD zW3sb_UAOG<{I(a#wDTFH5b2ezapzhZFEF$``#apWi%$@x`F)`wgpMQ{9a@`nZpGoH z*q;6F^7Ks|*oI=AQ*-pU(=F?YV}QH-elo23&a#z z?1w!hn0cK(h=b0N{l|O`zTH%#j%Pd+dQi8nIREDMS26$diZ)C7zE%1H+9Ld=Zc)+S z592z@|J0N(a){GRUvtSO!kH;Lm0alAzw!{T_GIBpil+i^6E=7U$72yASfzUEOho}r#g5IONO z3eXd#(2ErMB86U{5ZzZNj#KD03LT};9k@eJe2qefDD-6t{hUI>6biuV#3w0aQRpEG z{T+oKpwP<{+DoD8YJ?IL+C-r)3UyQHZVG*rLM;?JM4{U$^f-k!PzbIV6ZI7O9>uLf zX!^4az8j5e4ddFy_|!9q=kQz3KkhSHZupVUxZk%J!2>=_=^yiLd$h{;KowdTJjOQt z*_(a!S1tZwmG6enSG`>2`(4%I*QK%qJxETD!hOZry#Q;88?Z*eGlQ<92yx*WP zOKyG?ot)I0RzNGD70?Q31+)TM0j+>mKr5gX&mKr5gX&mKr5gX&m zKr5gX&NfeV)}+Htkfe%ZUimUZ{`*6eD_3a#l(=CY=-BW(=1VjDWM`%?Cn zPP0DNWg7j9=$f@_?_Miqr!&b!G#<1ZsQfxS@3zSoK+vKHAlV=-e#W|cc*Z~E1CvfJEU=9@Q3W86;c%J!HoTRY3r z)vvLvR4!|g1JTZ`owhRey*WG4iE?dkwY+9b)4YqKS9e4+u}&+Q$)@dS@0Oj`&Y)$Q zt!u58t*vXUUZa1V+ut>IqANZ>dq!HwswyH5c`CVuxTa`4p6rZflW8b;5< zdRYvVB9_>-rM1yQ33i515+ifSHzeCs#<&Po)t13??l*JO+Shvd7 z+DJOY?WSDDwz{L8c9!ZaXo*&e#DTKJ>te}_1sUwdU3L~k>2uiK`e(XU$uqBGjTV}4 zEK4n}mwb$zIg`C;!$zj%^bKwf$>M&X%#^2bS8QFS7OttdK3XEKqA zVSuyJcD5&-+#}04RGHt<8MmWp^Dn6c!!k*0wh4n!Z!8hb+M@Ry7V%c+-l)}K?}{ZX zbn(s}VvLlopt;AbT*BU)vN48r(bXfRs~CMstWh7jGdeuRLnNckXBi8PD$DTqMq>$M zwNcgEW7&J{&Ro{Edh95T)^%$9G1gUqQEiOgZ5RvQw!!H6s?!-k|GmmPiW@(wI!ojJ zf$Hi7!}l1~3x+-fncO#>f$AA|wMVM?#`OtewG*oYhyE-M!&y-`IE>ysTov@U1X==t zmSCXW?+*n0{R@IEfzgG*Kq?gs`U631ftL0Ft_=GS_9J01;Kx7k+ZGze1^B}{?fmz1 zz6yMmuiqGA{0v{8WL)(QdA+?({=J<5<9^1s0F%98#*Z?dWW4koc|FX359mvbhZ(=g zc!cqTi)8vy#{bE9obewR8~pcyLW^a3|7z*qeT>75pJqJ7*mtfh&j{ljF!`Tql>F~7 z9%lS9<59+!pC{7?*UI!CWIW9He! z#=jxFz%X{IzZ3N?i63Ho5##3=uVg&QxQX$CTcy9vjF&LB2%`-i@0ZsTz+LEvYMb(4 z-$jPeUF|desqWqmN<)7Gs}_gwjWXPe>nmKCuCKrzpa3>HZO6fliLd&5hWQFpdg7yd ziB0j{nD}aZ_&4S&toW#gGQJxVU;VwVpD|xy#c%QO-I(}lJZgKlEWg5vAMo(qnD~Ak zkN$@F3M;-lzwL;0W8$mv??=p6Sn=KY5#No8ug1&YGhgAk@`u^~i!YYtS6K1g{#No| zjmL53E3EiIkA7}U{s$02X92wnSaG4(tm{&zul9+8&m$n%>R4lE3Ei_ z58sW6ukJ5@V7|h0<&Sdy_g^agS6J}_p8VaI@*ijZkD0IVT>0vL_d4?xR(yAPNq;w{ z{MFynt6d`fS6J~4n#o}!Onf&M{MGW>BZ|*h@lianDZU#MU)_&SFkfNCZ}ITmnE2}c zz3ejSzruqjft=32R~rG!iw)M?{-AGG4a)W;@Zol{|YO< z+h5|lG4a*>V>9y=R{WHw{BBHqHDB4we1+%ASM!^1DF1nWqxkOflK*Z@`K$TRB=Z%X zD__l@YThIDQ&{o+p7Ogf<*(*jcQapM#dqsX{<|^pgFL_5!+eDm-(6nfyD{R#q6 ztoVM9|87kFtNHw=nXjCT-{L918xvnW?|gM+ol!*^riPqJR; zES35xtoQ*B-;If{o~JD4E3EkL{I(;~jfo%LAnWT0^A%QncYefoW8$|ne+4ek^NYd= zisuhM&a@FGz8e!?J>PvMAo&U_KBC2@_-;)6ANyh5=bd0fjKK(gk^?dp| zWA%LMLw;R!;Ekq1HTXS9jZb*&6j+Tn+Z9FwAzGHPnos^vVSZkD4-%0*^}P46z*24E ze?efhFMhr~42=KPxFohC65}Yh7d^NM4kLgLl^(o7Vw6H|n?3kCkgvyn1NIxS zQ`=pR{c7ygZ|blIv4^nNV_%JZ4fY1?*I-|Vy$SnG*ssOD9{UFDH)FpAdl-8o_LbPz zV!svpM(l4#zEt9XQF@Q*{ULb9PqMQo<)3P2PvHKsx0LEE{mxv<;B?@#4Yzj**-@+1tfg)0~O-ie!8aZxmh0iZ6yr?-J>%d@Fed-XfkUV|agfx~9aN zF_)23d1rX4wBp;sQzd%d6V8+FDJrjpC>bkX22qN4ze6m=7Td_&ULIB;7T+4;TKVfj zEWhx+C*&ya3qp=Ay&0^$azni+oUwePax3|xp-ErMzFHcU1sY>tnj#Vr*$V5 zt+)$#wmcCMoQfySYrB)_J<)WRP@+;1g#ThCPGj2cP42c)?ru9R*6p;`Tjm!M< z`uZ6%TXx*;J#DRamo?s#wf9`cb~Jr8yRY;m}+SmyzL1S<}T@lteOt z1y-@$v1r_ib#Ecd)C0>G4HbEO-cYCFSxUF2I~I?Zb56y}#_nh=Zg-U_ zd(u4DVVz7Si$yJ1?NS<3n?o3}uJFVe%3_u^tHa+*HdXN7*giercc_08q!^;?%8U!!o`zYL{qR6SjFaQk)>6G)Y^)3 zJ6ce=b*Ef5$rHP>9$8G-Fw;NxHn~!REs$C;Cr5N0){DrT#9Y}$myi=B1~i^roKaXV;uV?t|ZMAe68Mm5Zc zTHQD!YE1~*h=-#TrdGJS8Fg(LEPk)+jix(0d+goOcvmu!u#2;&zte`!(#>F#e)y%9C|mnm-37~^ME_48e%aZx z^JS20QZT=JseZZ^V;fI#^wTwc>^0kig?_r`k*D|wMvrHB`qxj_pIx#xLq ztMhx6s($A=*-us#o~oPmle+tx*$Thr>L+#aLvH!Z!o--U-jV1h^%-vf{*0g0dHu`( E0=)skj{pDw literal 0 HcmV?d00001 diff --git a/Sources/bin/helloLibrary_Testsd b/Sources/bin/helloLibrary_Testsd new file mode 100755 index 0000000000000000000000000000000000000000..7fda4e86fcc41fab0a772a2c2c2611f49c8b17a5 GIT binary patch literal 51832 zcmeI4e{3AZ6~|}KHpJwIouo|y1me&@lTszV{KAH$_=r#J!Nu6I6RdzUz8@R=;CwcB zdxA+d^7oPr4b71C1ZrYXN^!jF>c_wDYT zeH*6`#2;1lMxL4XX5PGc^V!+C{b&5*CvTm(Pza?+2;o7VgIs=r5dFQ2AqjCYvWhHa zz3)c9cTZBDz} zU;KJIzL`!x>64S&x0LC`&R8NUV~OpZFm(I7+ws@!I3eBbW3qqRC;KcvwZ0~w+;B@> zqrF>d?6?GKE4gagzm)0Omm^Er);VdLK%d%Q1#GQUV~=+Qz`SKO`3&#=^5KfPHXD}8{hLSzegC?$SWGNz*%!{U2*+rlePd5b*E*Kp;0&=sxe6t%V+_xM zp4&1NfC(@GCcp%k025#WOn?b60Vco%m;e)C0!)AjFaajO z1egF5U;<2l2`~XBzyz286JP>NfC(@GCcp%k025#WOn?b6fkFbCRpSlcmPWPjpY@0Q z`xmJDRk|Bgacie)_@6oKe>NG9E!@(*+$Q8Vk`#vLK^1R_w4Q8gpfOqZ!D z$1vVBAHrBQv*u-3So-%ZeVS?bUtmOC7S+VRI)`?}*y>T>WjnZ7rji{Nyz#tYxgHWt?0|0Z|yMVR~{pW;N+XmSvRp zT3P6IF;trS1>CdRUbbkr1-9Othh{U2wz5UFLRfrn^=_@bx0qGH9?bUmkCL(3Lh&5*AN3i#myjzgdSs(=#`oPfhN1cTKC1{C zp9IQkU#TrS2-jzV#(Nu$?}VietSidsMHPL&EivcOWLSgwDekPP#;d@) z^fuq^z82p$pKKXDIWJ&6uQBs4=(mx+b|#y(TZhf(skI1N&^T@Wm0ZxuyRjc$GoONL zzDx!`#}hDrL%jeUw(7&?KDf#8cJr-L`?F=cOJTXucrIYP7%)DoH8vhljWKoEyMc_l z!0$b!E_*gucFTLJvH4Necu8IMf!hDad*%f)ei1a@QH?)j>s!_8SIhcGvHFeur^w0Pm?am;F_=;;v{PY5 zFWk8K7{yZkL3$b9uSWyRPH*hb-ZRG;f@cW(VD(4o>4C$wOXw~i82i0%1q~CAr)tvU zDRjC8h7>&w$X==5K;=zV8MMketE{)mO;*`tm0PT`*($eM{1GHjJmtK4pt z?N)gQN-SmIvKRzkWA@4uKsVSDFN z%u}BCn$0TZ;waX3RGG2gBVJcI$b`f*NZPN196-%4_WVqjUv# z9rCYm7o8I6bgz`|dW-9Dza4j~TVc?Q8iyP1eip+oc@ds^MJTP92$5Q8vG6q55|>PX z2`~XBzyz286JP>NfC(@GCcp%k025#WOn?b60Vco%m;e)C0!)AjFaajO1egF5U;<2l z2`~XBzyz286JP>NfC(@GCcp%k025#WOn?b60Vco%m;e)C0!)AjFaajO1en183V{Ro z9|H7$2r8ZWTBojc>N=-xcIvQG$DMkIQ};UceNKJ9Q$Os~?)5(Ev_Ik0ht6T=9>+Qp zU;<2l2`~XBzyz286JP>NfC(@GCcp%k025#WOn?b60Vco%m;e)C0!)AjFaajO1egF5 zU;<2l2`~XBzyz286JP>NfC(@GCcp%k025#WOn?b60Vco%m;e)C0!)AjFoFL^0<*s% zT5f0*Vor^eTk9J2RZ@CaM>^BGUo<4e;H1_y5xu8N3q<@YV^P1|6OGsJ5UKW|kFriu ztO1Fg9m3Tn+q%1DmzGR*CPML;-XnKZie&lV+?r@lJStOqIxNGnL{!6+Hf5UFa^LXz z{%J%?%*Bw+iJkBwH)*MKhXz-vX|t^rcvrS-@pxx27EXqeJ!?0_L#dSanj1B}N$b}A zJIJ#9zgTYY`W-ahmElk-7D2?xSfVWuscZB~uQ$>jN=iK$is>ovfvs0ohcI6xq<1E% z#SdU2wZMjavrTy|^~bg9bV`%kLlI5)Z>npolr~+Fswgn7igl(Wrq^U52nF0`tP9dTP=%5y;|3j9kE16*Q~A7P0cdW9g<RavxyBQ0z1{yWM{joY3t>B}REWV| zyPv`+Q_8I<=>Le!vveVbs_p)T(9sSrcKWuhlc|;JQ9{Y{+OuhCAe_ki@`3}pU#pgTF zbqasU;no>DG1mEHm}n^cT9{~`d_+&Q<}rS;!+DB<`C}Py;(H}`LZ9`?LgVA1L>mtDcwFXx3oun~C#+m8C4P7%eJF$?u)r_SU1=>5!S~dZ zKhyLrAl>_?Nj6nVzrXPsS$}imYDsI!P2gRN2|`ip*9;$TnCo1Q$#1pujSx<6moY?R zeWv8RueH55R!RI(82N|e$E4!M4IA)_6w$hLsfWUGt@5mvm1niALZlY8u4HTnekF0f F{0Ak+^9cX| literal 0 HcmV?d00001 diff --git a/Sources/include/helloLibrary/Class1.h b/Sources/include/helloLibrary/Class1.h new file mode 100755 index 0000000..dbcdd15 --- /dev/null +++ b/Sources/include/helloLibrary/Class1.h @@ -0,0 +1,31 @@ +#ifndef HL_CLASS1_POINTER_H +#define HL_CLASS1_POINTER_H + +#include + +using namespace std; + +///a simple namespace +/** a full description + */ +namespace helloLibrary +{ + ///a simple class + class Class1 + { + public: + ///initializes the Class1 instance + /** @param text a simple text + */ + Class1(string text); + + string GetText(); + + private: + ///a simple text + string _text; + + }; +} + +#endif //HL_CLASS1_POINTER_H diff --git a/Sources/src/helloLibrary/Class1.cpp b/Sources/src/helloLibrary/Class1.cpp new file mode 100755 index 0000000..2c715e6 --- /dev/null +++ b/Sources/src/helloLibrary/Class1.cpp @@ -0,0 +1,13 @@ +#include "helloLibrary/Class1.h" + +using namespace helloLibrary; + +Class1::Class1(string text) +{ + _text = text; +} + +string Class1::GetText() +{ + return _text; +} \ No newline at end of file diff --git a/sonar-project.properties b/sonar-project.properties new file mode 100644 index 0000000..4207346 --- /dev/null +++ b/sonar-project.properties @@ -0,0 +1,13 @@ +sonar.projectKey=testCpp +#sonar.language=cpp + +sonar.sources=. +sonar.sourceEncoding=UTF-8 + +sonar.cxx.file.suffixes=.cpp,.h +sonar.cxx.includeDirectories=./ + +sonar.cxx.cppcheck.reportPaths=/work/**/*cppcheck.xml +sonar.cxx.gcc.reportPaths=/work/**/*build.log +sonar.cxx.gcc.encoding=UTF-8 +sonar.cxx.gcc.regex=(?.*):(?[0-9]+):[0-9]+:\\x20warning:\\x20(?.*)\\x20\\[(?.*)\\] \ No newline at end of file