diff -Nru libetonyek-0.1.7/ChangeLog libetonyek-0.1.8/ChangeLog --- libetonyek-0.1.7/ChangeLog 2017-10-23 08:04:19.000000000 +0000 +++ libetonyek-0.1.8/ChangeLog 2018-04-21 17:55:25.000000000 +0000 @@ -1,3 +1,897 @@ +2018-04-21 David Tardon [4e979303c9cc4412ccd5788e399941a823f6ac3c] + + prepare for a release + + Change-Id: I3e9362cdf0f0bf278e8f8ab90d30344a863b39ea + +2018-04-21 David Tardon [2cd34af83c74e7dd2c4fc49527760d895bd7bfb0] + + cid#1434976 workaround coverity false positive + + Change-Id: Ic31acb44691c6faa709679632f982c72a4d7b3ca + +2018-04-21 David Tardon [79dd7d7ce45ebfde1aa7e0e733b93a6c1af9e4d0] + + cid#1434975 workaround coverity false positive + + Change-Id: I7d90b15e82b0476562551e526c01f72c7e813cee + +2018-04-21 David Tardon [d8748ab56d2d33ae3dcc6e5142be10f28a77218f] + + cid#1434978 convert constant to bool + + Change-Id: I679fd8f79b1f2cb4cda03cd0f53000a45def6612 + +2018-04-21 David Tardon [466d91d574a48fba50a1a533ae2a9eaee0ddc77d] + + cid#1434980 initialize variable + + Change-Id: Ie4114485c14d20efc78d8418000eb54b3c354216 + +2018-04-21 David Tardon [b40ea4301a08b02996580ea842773fdce8699a0b] + + cid#1434979 use meaningful default for star path + + Change-Id: I872cf2ddac564d03dfe564896d9331d32669dea8 + +2018-04-21 David Tardon [97734c2b2e4e430e5b14c758f40b3625ca63aafa] + + cid#1434977 remove dead code + + Change-Id: I18a73a200a0adedd2fc4987391a7e9025b62326b + +2018-04-21 David Tardon [40500fc00951e2dda1ecf7ced347316a5de7c291] + + cid#1434974 refactor to avoid warning + + Change-Id: Iab1a2776748b88f4a0e2d2c60c6ecc13b8b68aad + +2018-04-21 David Tardon [b9413fbbac820f3d62d027ba1458363f85add111] + + cid#1434972 remove dead code + + Change-Id: I457354003baa94b4b37097d6463c9d36e6653e48 + +2018-04-20 David Tardon [19ce4cad10e5b438d506179826ae899fc2a6bc53] + + WaE: declaration of id shadows a parameter + + Change-Id: I9f4e59813689bb455717d270d7089d281798f0b5 + +2018-04-20 David Tardon [e6660bd317d32ecee2ffa1a6e74a92ec0b3c6b9d] + + WaE: ignore problems in mdds + + Change-Id: Icf01acde5b9c2a01067355d6be2d5f107238f47d + +2018-04-02 David Tardon [43b5f686de941fc10163e35be219e76ae78c943e] + + fix copypasta + + Change-Id: Ic4e976ac1012ac799b6b747fe32fbcad0ad0c3de + +2018-04-02 David Tardon [4061a9a24a07d3feffb1cb824bc3d27112aa7549] + + parse text background color + + Change-Id: Ica177a71f12da7dfd5b483eff94855a408c4ac21 + +2018-04-01 osnola [3878b6316dd16217b16ebe95157c713db1656a57] + + iwa[table]: try to retrieve the vertical alignment, ... + + Change-Id: Id1d1d4e7be90292b1c0414f3ee6a24d5e59b9f2c + +2018-03-28 osnola [20baee0c8406f52ef16d5629f6e096b7829a8329] + + iwa[table]: try to retrieve some borders(but not the header's borders). + + Change-Id: Iaf61f021d4b2c601812bf7c12ff54b704995e38a + +2018-03-28 osnola [3c6994598b2673aa7b8f00474de1a1979ed5f4a4] + + all[.xml]: try to retrieve sf:ghost-text and sf:ghost-text-ref... + + Change-Id: Ibbc7582c45d9e886af8b16e1b7ffd50bfd479f8b + +2018-03-27 David Tardon [437faa917b950c22f8d2aea0821b4364a4dd9daf] + + revert the logic + + Change-Id: I1cae65d607d990d18c2a35b983e6d67e6c701e5b + +2018-03-27 David Tardon [d4f800e55e465295fbcfa2e959a292f1f73ac899] + + ofz#7114 break out of the switch too + + Change-Id: I235958335b0b1d2b3b059d611fa2b4f48711c62a + +2018-03-24 Julien Nabet [78d2bbb97daf21cb782891ea0feda05e37d98624] + + cppcheck: fix some errors + + [src/lib/contexts/KEY1FillElement.cpp:81]: (style) Consecutive return, break, continue, goto or throw statements are unnecessary + [src/lib/contexts/IWORKTableInfoElement.cpp:318] -> [src/lib/contexts/IWORKTableInfoElement.cpp:318]: (style) Same expression on both sides of '&&' + +2018-03-21 osnola [f7a995a63e4fe036cebf086de33b7f10875237ea] + + iwa[table]: try to retrieve more styles... + + Change-Id: Ia07a001a1a2f57207402070c14576c9830b74619 + +2018-03-18 David Tardon [b14bf53fe5d7e54f376a8745a4554deffcf6eb5e] + + WaE: base class has accessible non-virtual dtor + + Change-Id: I8db9c49ec1cf742c4299c120b50eeed6af3c2fb8 + +2018-03-18 David Tardon [84eb6e19dd2e56c89c9c5db40a6d965810f34bb1] + + WaE: initialize member + + Change-Id: I7f20e096e702b109eb4e8203b327bdea8a434c17 + +2018-03-18 David Tardon [02466e1f0f7c7d38d7a530bc67ac0d56e3326b18] + + WaE: initialize member + + Change-Id: I2b748f4e9a630cc04067554af2f24bdca17f33df + +2018-03-18 osnola [7a2ac5646394cdbce106b295f366918cf1ffff89] + + Numbers[.iwa]: begin to retrieve some data... + + Change-Id: Ib47d34d46c2d4d0033aa46bd28e9e7f7efb88547 + +2018-03-18 osnola [7d7e491a2d1a9711aaa3f8d95cd5675315068317] + + .iwa[line spacings]: try to retrieve more attributes, ... + + Change-Id: I5d29b6a17fa02f0a3c5067c60a7685dfbe49ac30 + +2018-03-18 osnola [a0538b7ba153e0b6b0d726d6b67777f16af41b6f] + + .iwa: line spacing, try to differentiate unit in percent and in point... + + Change-Id: Idace3087c0df26c0633f5469834ac174f74798e3 + +2018-03-18 osnola [0caa1418b50a1e74487ef5743c8e3e06f731c998] + + .iwa[pages]: try to retrieve some pages' attachment, ... + + Change-Id: I1af9375bb810ddbc8a758a65e22266eed4101976 + +2018-03-18 osnola [e90278ca8632ea95f2e16028f29312a9d544feba] + + list: finish to open/close the list element correctly... + + Change-Id: I94d55fc93681e6c9642c29b1ea3926175dbc9287 + +2018-03-18 osnola [bd63a48942f9238ea237f1cd9b5121d3180ab24b] + + list: try to open/close the list element correctly... + + Change-Id: Idbfa804438811a1977e3a1f26c39d5578e88e848 + +2018-03-18 osnola [e07686b3425ddf9c4174ee2a23c87e091416bbe1] + + paragraph style:iwa line spacing is giving in percent + correct margins. + + Change-Id: I757f48209edeb5ee5610cce1f9559145ee296486 + +2018-03-18 osnola [aa5e799ba7f2e94448e6303c905a0b187cd7e1a5] + + .iwa: try to read/retrieve the images' style... + + Change-Id: I50188a08275ca56aaf799345ae16a0586dca7d07 + +2018-03-18 osnola [264bf1d773d97d203015f1541e52218c23c355f3] + + .xml: try to retrieve some basic pictures when there are absent... + + Change-Id: I78949f636b60a74fadb4bb3faf5a7e4bf145c4a9 + +2018-03-18 osnola [e3cfb225387d204223ce7472cab5fe30d6bd8e70] + + Keynote 5: try to recover some connection's styles... + + Change-Id: Ie85c64c8b32fdcbfba87c23a2a62b016897cfe68 + +2018-03-18 osnola [e82bda41717f4a3c917bbeefb1b09a60df71f758] + + Try to fix some rotation's problem... + + Change-Id: Iab809a894523ca38ba9f3dd6b8e1e4d23bac2e95 + +2018-03-18 osnola [2b16d8cd74f8773d55a7519f33ab464454f19aea] + + KEY2Parser.cpp: fix transformations when a connection-line appears + + Change-Id: I848b62990690cf042363d9abda4e9757a292bfcc + +2018-03-18 osnola [eab6780641d8073292d34498a1c089e6337b80e8] + + try to retrieve some connection's lines... + + Change-Id: Ia79c825779569e6aee8235ed1de78d652792fae7 + +2018-03-18 osnola [d0ff0a8ce861b26fa02d7508f75809c18a262ea5] + + .iwa: try to retrieve complex bezier curves... + + Change-Id: Idad2669752a58935d2892dddc048604831a89bf5 + +2018-03-18 osnola [9637cb43608480556f846dff1d8ab62f26feecd1] + + .iwa: retrieve arrow in Keynote 6 files, ... + + Change-Id: I0ca104ee22ffebd2b9dff7cf1de593ee519419d8 + +2018-03-18 osnola [5bdab2fdd7ae3a63bafe4c57ad12f4ca4a4cc6d4] + + .iwa: try to retrieve some arrows... + + Change-Id: Ieb6a0c342f3baf15b7fe87b68f091f5be4aaf3fc + +2018-03-18 osnola [4c77f6481cd4ae476f8f7ebe40d12d490ca9a047] + + Key6Parser.cpp: better transformation's management... + + Change-Id: I56961451893c623db3c73f8162638569498af289 + +2018-03-18 osnola [cf89acc16188bc4c80c84662e69d818f1fd05b5a] + + Keynote[v5]: retrieve some title/body zones... + + Change-Id: I89768fcfdf8835a87d6e6ee4a9e33dfb3d408c99 + +2018-03-18 osnola [ac0a5a5b6df1213a2d2aaaa97ffc90364d85a1cb] + + text boxes: do not send width/height if unknown... + + Change-Id: I7784ff93e7adb07eb64e6eeb83b44b85163a8390 + +2018-03-18 osnola [f4bcb97e4fcae19551053849c7fa35c2767dcf92] + + .iwa: try to retrieve some textboxes... + + Change-Id: I80f9d77c77ab1a6b479d2ee0c09ca058977ff087 + +2018-03-18 osnola [f907903c7f5df636a9b02c7f54fcf97615f01db8] + + .iwa: add support for date/time and for text's reference... + + Change-Id: Ia641498b23fd8056404e676790df66b6ec4ac78a + +2018-03-18 osnola [58c5a84ac5a685580ba12e172ad9b7b687b69a95] + + IWAParser.cpp: correct rotation angle+read cell's content with flag=80 + + Change-Id: I7f975fff090cee9e310ebb7d96d11b58fd48d896 + +2018-03-18 osnola [e14f4ed2412c0ffdd8f9ce6d4354aea49b18e17a] + + table: try to retrieve some float[.iwa] and correct padding... + + Change-Id: I1ce32f1f3e36ef274f209d6899cbfa610ae89b66 + +2018-03-18 osnola [a84b8f68a87f86f5d529a32fb6e441dcd1d50a34] + + iwa[tables]: read first data + simplify the code + + Change-Id: I3e8998a659fc52b7e7b9b61fe09cf0804b441681 + +2018-03-18 osnola [4a8d31285cce3766961bf9989e3a09cb80bbfd8d] + + IWAParser.cpp[.pages]: try to retrieve some tables... + + Change-Id: Ia57d1aac6e0a88b420f7c9c4f160741bb3f7246e + +2018-03-18 osnola [422599803191509509891e17f1335f2709129edb] + + PAGCollector[drawShape]: use the geometry's transformation, ... + + Change-Id: I1ab41bddceef70503514208446766b2d3df29a17 + +2018-03-18 osnola [20254a8faf23a1691266e9786933b88159e92155] + + .iwa[pages]: try to retrieve some char's attachment, must be improved... + + Change-Id: Ib926a53f24f9260de884b39e9d479be10ab2fc6f + +2018-03-18 osnola [c4eec7de8abad22c7c5c2a085e221805b80ccd56] + + .iwa[pages]: try to retrieve some header/footer... + + Change-Id: Ibec119ff6de8de19c13e9ae663e1fb710b6524eb + +2018-03-18 osnola [41bcb0944f8abf262abc93b74fab1a993fd9a013] + + .iwa[pages]: try to retrieve the sections and to read the master's page... + + Change-Id: Ie86ed0f8b13fb50caf68729a626849b6ed19352c + +2018-03-18 osnola [e0fb3027f8b171a377160a4e42eb515390c4b2d4] + + iwa[pages]: add code to retrieve comments... + + Change-Id: I83ac81490f9eda8fa3636d03c69917f96bebf662 + +2018-03-18 osnola [011c7b0a24a7e05f0c72e298a538a11f2ff4ace1] + + IWORKProperties.{h,cpp}: create a TextShadow's property... + + Change-Id: I41b0d9a1b5b65e12549a93f6be849c692bbeed93 + +2018-03-18 osnola [a0dab214960a334c241325a72721a489ce5a163c] + + iwa[text]: ignore the first character in a footnote which is bad... + + Change-Id: Ic1a07b62684d24c524ec47a455fa42bea30933ee + +2018-03-18 osnola [bb6a02d91deb68b015bd4bec30c61f8ca1383581] + + .iwa[text]: add code to retrieve footnote/endnote as footnote... + + Change-Id: I32c083581623250900a14bd378be6fcbf3b9f741 + +2018-03-18 osnola [b08379964d5ab2b7069fb83aaa9053e6af631a6f] + + IWAText.*: try to retrieve page number/count fields... + + Change-Id: I72f2624f8140b9228e07f6c20b7a84558a214b99 + +2018-03-18 osnola [a677743b4cca93ed38a7e55cceaf622c58242c8a] + + Pages[.iwa]: retrieve the page's dimensions... + + Change-Id: Ia487ea1f77eff82ebe295d703e6d4a38bf48cf05 + +2018-03-18 osnola [e419cc562e45b74d12a7736badb7af78e5fdd1e1] + + IWA: try to retrieve character's shadow properties... + + Change-Id: I7ba23e76ab10fa4216060bbe7084e613571cd0fc + +2018-03-18 osnola [886cc206d30e276bcc9c4d56d549bd318fa239db] + + EtonyekDocument.cpp[keynote,v1]: check that DocType is APXL... + + Change-Id: I35408df74cf73460d4c24fc1f24313a52a7a16b1 + +2018-03-18 osnola [853992a65cd2a2b36a241d0ec88240c2545a47a0] + + KeyNote[v1]: allow to read files with no namespace... + + Change-Id: I9c7b57772531e47ca16d1e4c106d447cb8799e28 + +2018-03-18 osnola [02fc02fdbc297d4361aefb6e057a464d3db760b3] + + all: replace makeContext by std::shared_ptr, ... + + Change-Id: Ic1dcfed3617084621c7f089b14df9dd8840bdc80 + +2018-03-18 osnola [2ff123ec999455a1ba32d292726041f132ea7c24] + + clang-tidy: fix modernize-make-shared + + Change-Id: I471547ceda9557b353d373e37c3bf2ef5128749a + +2018-03-18 osnola [9626818923e03500ec44c66552ac9351e11036ff] + + clang-tidy: apply modernize-use-auto... + + Change-Id: I42427043e994dfc6e79d7bb15974591e4112a884 + +2018-03-18 osnola [c06a0e578c507513ef3f8c8039aacebc42253345] + + clang-tidy: uses auto in some loops... + + Change-Id: Ie74a649d02ec3e74e369c68f8a1ed07a9b2a7586 + +2018-03-18 osnola [3bc1c32a1b9e458ff92fe2afe7b0e286a4e4ebce] + + clang-tidy: replace some virtual keywords by override... + + Change-Id: I7c05bba8acae04d74f02c51c7c992fdcdf958484 + +2018-03-18 osnola [c4cb781f266dca8276e5e5609597674d64e937bf] + + all: replace 0 with nullptr (when possible) + + Change-Id: I267175b7fbbfe19e84471db0ae562a41ab68da53 + +2018-03-18 osnola [5af3cf122f007c047a62d9a53b41abdf9a546b01] + + Remove unused using declarations... + + Change-Id: Ib197df709a13760fe953118db740585a0b9f5511 + +2018-03-18 osnola [d55d3506f0263998b405722fe24b8070989008dd] + + clang++/g++: do not make std::enable_shared_from_this<> protected... + + Change-Id: I25a580db56c30a6f1f2323236b61a125e587e94b + +2018-03-18 osnola [e1fa080f24339510e7fa29b0d9339261e029c9ea] + + g++: correct a compilation's error and some warnings... + + Change-Id: Iefa59836f1b9a09c5cffd678efd67e7107435bc3 + +2018-03-18 osnola [bd8323e7a31e03ec15864910fb34ead07ebb1d4f] + + clang: remove all warnings.. + + Change-Id: I14dd06650a7471838e25c1005719c7bac746a81e + +2018-03-18 osnola [5ff53ea8914eba6dff3d50215d57ad027d113852] + + Add more debug message, retrieve external-text-wrap-ref, ... + + Change-Id: Ideca74aabcb875872876508e580e5ccb5105e1d1 + +2018-03-18 osnola [3228f3ca401a0d8decb21f52ff688bf6c865f34d] + + Try to read the transition elements... + + Change-Id: I28fda75f35a3da6ed0add8ae1fed6ff50eee5ded + +2018-03-18 osnola [17a2bf083dd915c055b48e98a9ee72ac6336afcf] + + Try to retrieve more layout's properties... + + Change-Id: Ie7ec7b68dedbcdd259201b97474a472307f01e8c + +2018-03-18 osnola [361058896630c5f5321c5a92c6473ac94827f24f] + + Keynote 2: try to recover some title and body content, to be improved... + + Change-Id: I6e219a90e34459c1d0bf2a3ddfb4ff0bdaccebf8 + +2018-03-18 osnola [2ef2b06866ff1e46ac1c949b7a1ed8cac33c5a2e] + + Keynote 1: try to retrieve group's data... + + Change-Id: I2461804048f2ee8e3bce026d75f693c91b703f86 + +2018-03-18 osnola [c694d1299eaee12f4a280c4ede2986e542a48463] + + Try to recover some vertical alignment... + + Change-Id: Ifc982b700e3450b49b8f17b6dd1089af09a209a0 + +2018-03-18 osnola [cbf6c60d9fbd48e1b59ed9fa4031e2185bed9dc6] + + Keynote v1: try to recover some files... + + Change-Id: I647f6d2fc326cf4bd12b212e965ec490796682d5 + +2018-03-18 osnola [06b048e571e5e49e23e834b921c61bb5d53ec9b3] + + Pages: try to recover some z-index, ... + + Change-Id: I820930ca46d986d2bb9ba0015b7853e1857ed30d + +2018-03-18 osnola [e05d0710a45bf74e356a21648688924999839d84] + + Try to recover some wrapping... + + Change-Id: I634ed2d5eafe42d55a95cc63954481868e106b57 + +2018-03-18 osnola [251f2cd96a21600d1a37ef5a9b02dd9d3853f8d9] + + Try to read the external-text-wrap elements... + + Change-Id: I94f2a3693b96217b262df5625b80f647b87cd940 + +2018-03-18 osnola [dcdcd285154c91418f5a5a35ba22867caf1397b3] + + Add code to read sf:wrap element... + + Change-Id: Ia7f4b8335e4e4a111dee3b695ff4b429e08c5874 + +2018-03-18 osnola [3f06be8643654caf2bc1d6c0752c8ddfed7cd1a1] + + Keynote: try to generate simple textbox when possible... + + Change-Id: I67a4aa33d8c6ba0ca2039e050b0bd22900c91c83 + +2018-03-18 osnola [fe7c880a52723ea962dbcb41aef2cf5d2e72a612] + + Try to "read" some frame's elements... + + Change-Id: Idb45b904775bf6f553a49ba97d34d8c696ae6039 + +2018-03-18 osnola [411da99e376ffccaa4b04f17333434fb0ca13bde] + + Pages: retrieve basic textbox's borders... + + Change-Id: Id770ffebde620f1342f53b0cded4d7b8043ac25f + +2018-03-18 osnola [4f59646b61eac498f76d816202fcfd1f8c050fe8] + + Pages: try to simplify the drawing of basic textboxes... + + Change-Id: I64337e109265e1ffaf151a3ad5e45af87f2af3fb + +2018-03-18 osnola [78fff169eaeb2ee8bc7f37df35ce9d1b8fa4a962] + + Try to recover some attached shapes(without text)... + + Change-Id: Ic0fae4f1f7208d9b1aed918e4e4c70843d600082 + +2018-03-18 osnola [c00fac1f8fd9600f27a2c16d3b7d8b374b57afac] + + Try to improve position of cropped image and reading of sf:media... + + Change-Id: If0af59954dd37071bf63c9b072b28ccc3d5e70a4 + +2018-03-18 osnola [2d028399c7ce20e95c1b5026466d320bbc90de81] + + Try to recreate some groups, to be improved... + + Change-Id: Idc485fb73c9c0c8057ee7e2a480450e68f584b25 + +2018-03-18 osnola [96af42a416e9b516b6d822c266c181bedaa71c7a] + + Try also to recreate Keynote 6's master slides... + + Change-Id: I6e81af49761eb2270e33f564bfdd984d381fd111 + +2018-03-18 osnola [902d2905d0f5433ceb5d3199b5f3c17f1d7469c1] + + Try to recreate some master slides... + + Change-Id: Icdab0da7b26102cfaeef674f535a1ab1c1e98e17 + +2018-03-18 osnola [58f4dd5b1348e45071bca783f26edb07b1964a1d] + + Check if image are mirrored and if transformations are "correctly" applied. + + Change-Id: I1de6f1e310a831cd9a4b6a662015689f485c5d82 + +2018-03-18 osnola [4c9a5cb6bccf9a80b800d89b9feba37a917c17f0] + + Pages: use the page's dimensions to define the page's sizes... + + Change-Id: I640a74739eab17c3c087a59e127ba9980521167c + +2018-03-18 osnola [98febb009f731138d9d40b088be82305b1004b8f] + + Retrieve sf:rd element(+ corrections)... + + Change-Id: Ib612c8e69cac8a2744afb459ad9b9b4a98bb06ae + +2018-03-18 osnola [0b248c9f1f0bb079253e4fce5851004a084e8420] + + Try to retrieve some crop's geometry to create image with good size... + + Change-Id: I515b6ba736707f4593241d099609f5dce1c879ea + +2018-03-18 osnola [d97460ff8196e6e2fd57acccaa455521a891ebcd] + + Add code to retrieve some sf:table-info data... + + Change-Id: Ic63d959a33cde9343ca44c29f58472eebdb7fddf + +2018-03-18 osnola [39442cac1f5efab1940546dddc38da6f63a63cdf] + + Try to retrieve more columns/format/padding properties... + + Change-Id: Ie0f34c8f1af3aa37256ff5c78378782dae219eea + +2018-03-18 osnola [39a1262c9dce0bb99d0b385fcabbad0eadfd262c] + + Try to retrieve more Fill elements... + + Change-Id: Ib27bba1c1d7f12a64c8c2bbff4578795c1f3dbc2 + +2018-03-18 osnola [492728fa0d18b4175a10d0265d5f13fa2f740022] + + retrieve more slide styles + little cleaning... + + Change-Id: I1f7fa887259bb1285eaac31cc3c9f4acb0eb6d2b + +2018-03-18 osnola [48ce77448361504ec941479406898fd0604488f3] + + Try to retrieve some sf:image... + + Change-Id: I9d788429e2cfc68a3fca28241e01f6b5f5d50e8d + +2018-03-18 osnola [c0b321092e810f4e34235bc90d08eb64dd7fff7b] + + Try also to retrieve gradient-stop-ref... + + Change-Id: Id089d95cd4ed4a1517a31935f96cd9f32c73c24e + +2018-03-18 osnola [ea569e7c866a22472e51678c0f627b039b7bdd4b] + + Try to retrieve some linespacing-ref, stroke-ref, ... + + Change-Id: I7a1e5a02a8d40e6f2bc317b073c602e2286a302e + +2018-03-18 osnola [9cf0dcbbc3fafb70f38e3310c3bc9b288aa75d49] + + Respect absolute attribute in offset formula + remove other warnings. + + Change-Id: I6c9261b1cb25ab62259cd4aa220f32292333a908 + +2018-03-18 osnola [c4846c874a17136a5030723db6473e0faaf0295a] + + Pages: allow to retrieve tables in group + correct some warnings... + + Change-Id: Ia6c07db5e2b6abc2d4df26e7c1fcf172a26d5649 + +2018-03-18 osnola [bb042ed1eb98775933c82304cd5d1b9af3aa56d7] + + Try to retrieve some arrows and to parse multi-polygons + + Change-Id: I63209494907a3e345e5827e402a4a4cd8a9ab096 + +2018-03-18 osnola [e3a0b7a2f04b33585011e7d6788dc4b69cf7894d] + + Try to retrieve callout, to be improved... + + Change-Id: I4755b2ae173dedb5ce36401417b48b7eb81b14fa + +2018-03-18 osnola [bc6062297dffc0578994865c428c5c8727f90f97] + + Retrieve round rectangle shapes + check if Bezier curves are closed... + + Change-Id: I27bd07e5f758cbd32a806a7d7f65d6de88979e52 + +2018-03-18 osnola [a02fd5fefcc565e8dae8ba365c1ea1c2f237e0de] + + Pages: try to recover some group's content, ie. the groups with page's anchor. + + Change-Id: I16bf7ea30e30a7fe4ac29389d35684e9bf81740d + +2018-03-18 osnola [d4dbfb1f2eb83f9eb21aec92d1e1d58db2b6a894] + + Try to retrieve tables defined with tabular-model-ref... + + Change-Id: I73b810d900a79cb6b7b2c9d96e14ebb03a5249de + +2018-03-18 osnola [7484d468df693252197a32be257050039b8680eb] + + Pages: try to retrieve attachments in textbox... + + Change-Id: I29f377c4ba15f36cd1f3b000ab9b3ee1a53d31b0 + +2018-03-18 osnola [36b854f1afd22576f986a4edd75b803e495487be] + + Try to retrieve more tables in Pages documents... + + Change-Id: I3e22556b96ea6fcec51e79be220a52f374a056df + +2018-03-18 osnola [b260affa25ac91632e3d89e35a8d871bb5255a51] + + Try to retrieve more attachment and to improve attachment positions... + + Change-Id: I5624fe176f1f380bfbeb8194618af161017c318d + +2018-03-18 osnola [e71bc48693ff8694f00aebf989881f56ba4b55bf] + + Read grouping elements and restart-list + + Change-Id: Ic38fde59835af8b25ab72746c94ecf8d5752cf3e + +2018-03-18 osnola [c84961dd26cb2fb88b31bfe195381fbbd89c537c] + + Try to read some formula's result.. + + Change-Id: Ibbea2c0576dfe538bdc70cf996fbf3c2dd8b3d6b + +2018-03-18 osnola [f53df18509263a4401933a70553a7e2cd9f28982] + + make --enable-wparanoic works + retrieve more lines... + + Change-Id: Ia638dd120fd4fb36267842b68adc259b22ca98f9 + +2018-03-18 osnola [0ef797f7259e99a8355dd1abd69bb8d357c5e80d] + + Continue to retrieve more style + some old keynote cell's attributes... + + Change-Id: I41349125f1b6d136500f72f7a2803cd4aa047dd7 + +2018-03-18 osnola [26c4948d78eb51a6e09b2dd3032d5f12b7007e9c] + + Retrieve Pages annotations and some Number' offset formula. + + Change-Id: I8bb064589cbc015d168e6739406a44944706e463 + +2018-03-18 osnola [57d571d9cba35eb700f5fe6bcaa51c7488cb4c31] + + IWORKText.cpp: correct fo:orphans and fo:widows + + Change-Id: I523ede2dc73126800271e51c6f2f9ee3cdbcce0a + +2018-03-18 osnola [67563ff55197b61600d04fe564272b48a5e6b264] + + retrieve more list's styles attributes + do not open span in a link, ... + + Change-Id: I38c92cc2351cdc53cd4b388f52f2dd6649a43d8e + +2018-03-18 osnola [49b8aa0e989949cdd0f390cd4da0ecc5757118c2] + + Pages[4.3]: Add basic code to retrieve field... + + Change-Id: I0c328151364685d8c89923c04961586171cd54d5 + +2018-03-18 osnola [11e5d3598616dd1031e31daae5f744f47388a18d] + + IWORKFormula.cpp: retrieve true and false function... + + +2018-03-17 osnola [a32ac53758f03b064cd398add74e5acfebde28a5] + + m4/dlp_fallthrough.m4: check correctly for clang::fallthrough + + +2018-03-17 osnola [8ee70ecb0e2cd374517dee203b4eb2f51d5ecb4a] + + IWAObjectIndex.cpp: make IWAObjectIndex.cpp compile with -DDEBUG. + + +2018-03-12 David Tardon [7b66cce346be6238a1051c4d7cb5d64adc347772] + + ofz#6294 speed up angle normalization + + Change-Id: I24fde3b0434c0b94c564249ec1cf0cc81f5e48bb + +2018-03-04 David Tardon [4f165cc047b86cf5fade74fd96e3b2d08e17d4a6] + + implement own printing of glm types + + Change-Id: I284fac56580b4bb0bb2c0ad096d57987c22f1f85 + +2018-03-04 David Tardon [1f18f0a872a967103ede3b6a4154fea8568893de] + + make tests less picky + + Change-Id: Icb41844779a55105cd431d4372c4fa88ba45555d + +2018-03-04 David Tardon [e8c81e8c368a03f51e7b2e3f55c421fc5755fa4e] + + fix order of tested and expected values + + Change-Id: Ia06b4e49569d884fb1cef8f7dbe7afe600ce29c4 + +2018-03-04 David Tardon [dd8da8597acd655df54187de86ba657fd34a345d] + + enable construction tests again + + Change-Id: Id13116f4f15ede04d7952f97565fd44e20688c63 + +2018-03-04 David Tardon [e157f1f5c76d8408b44c98d7d40d2dc37bb14c7b] + + fix build with glm 0.9.9 + + Change-Id: Ife0c761f9ca30ed94115b9e51e123642bd44bf3b + +2018-03-04 David Tardon [6aacf0ced2a49a000095339671489db2c07f3ddf] + + drop no longer needed tests + + glm matrix transformations are--I sincerely hope--tested in glm. So + these tests haven't been needed since the switch to glm. + + Change-Id: Ib10153c6b6ce4bd792b634ac1a3718203227c58f + +2018-01-31 David Tardon [5c69eb4808564f429d38f1ee6107e73f846805bc] + + ofz#5840 fix division by 0 + + Change-Id: I613ebc63f7a2af20efce15774b30f1d6db701eb6 + +2018-01-22 David Tardon [f64ef0e7356f2ed0ab4db715497af090f50fb5e6] + + tdf#113737 improve recognition of Keynote 6 files + + Change-Id: I925166227ede64d0ed38c4619217d23dbee7d138 + +2018-01-21 David Tardon [a42078df8a1ef9172b3fe229d4ba1d836a098d03] + + remove one level of indentation + + Change-Id: I1d973ad0f83b4f0ab6eebe20b573fb18977f8ea8 + +2018-01-21 David Tardon [5dfcf612b1815d57d3b003df1056453cae33f06c] + + ofz#4939 do not prune unavailable objects + + Change-Id: I8b3b88d62c5b3c3dafa17c414d7f40a367ed9e58 + +2018-01-21 David Tardon [5135265a289dbf6621fc8662f297e807b3391b2d] + + change map of fragments into a queue + + Change-Id: Ia2efb50ecaadfa08a0a051c9a81ce6873e0e6d0b + +2018-01-21 David Tardon [c2a1dd5283d154191ab77cc0705dcabac4e47d9d] + + move handling of object index to a separate source + + Change-Id: I211ced82fcc622ca8acab219490052d5112d5e30 + +2018-01-19 David Tardon [c512f4e875a336e4271469a2b663c383fe654546] + + ofz#4972 m_package is empty in partial or broken file + + Change-Id: I4c0d59c6635e0c900f7d1354ce7fdcdda8c104d3 + +2018-01-19 David Tardon [1cb10c4033433930055c17d221e2f38277fefd55] + + ofz#4936 check existence of stream + + Change-Id: I79301ef522e476d8202e406e46557bc7a3617da7 + +2018-01-05 Miklos Vajna [90536a95035db90782af14d474ffb650771f1271] + + m4: MSVC defines __cplusplus as 199711L still + + See e.g. + , + on MSVC we can't depend on the value of __cplusplus, since that one is a + too low value, even if everything else works fine. + +2018-01-05 David Tardon [f7d8a7839fcc0d2b8acdbd1a5a88fab555937865] + + save some vertical space + + Change-Id: I14128c94b1423eeb29f27aa7ccb0b0d4ec4c50b6 + +2018-01-05 David Tardon [f42dd8d6e4e29c35e718f5cf0bc657cd6b46ec0a] + + rely on pkg-config to find zlib + + Change-Id: I145f02096f0d089bf6aa26c7255aadcb61e104c9 + +2017-11-28 Mike Kaganski [56bb8f32b91977daea35d9eb62459cc6911dbc16] + + Remove unreachable code + + Fixes warning C4702 in MSVC + + Change-Id: I72aa0f7ae44d39632ee022814aa7a7c2ec1989fb + Reviewed-on: https://gerrit.libreoffice.org/43800 + Reviewed-by: David Tardon + Tested-by: David Tardon + +2017-11-28 Mike Kaganski [939e379c4c3a6f98654adda74ded63eb5210683a] + + Silence MSVC warning C4100 for boost + + Change-Id: Ic703e19504da06181f3d7f22cf8af09aa3ce346b + Reviewed-on: https://gerrit.libreoffice.org/43799 + Reviewed-by: David Tardon + Tested-by: David Tardon + +2017-11-09 Miklos Vajna [6d1da35a6f78eb2d1c607021f022123228ac1989] + + Use auto when declaring iterators and when initializing with a cast + + Change-Id: I4770e709c9567b8fe7b606c6da215240d995109c + +2017-10-31 Fridrich Štrba [6902c18043fd0bcfac73012650ce2b6976f5d04a] + + doxygen -u + + Change-Id: I0bc1bd223bcdfa064e161a558cae5aec9888e4e6 + +2017-10-23 David Tardon [cc71d75b4d9b88b5c920cd039bab3e707e71568b] + + add missing include for std::min + + Change-Id: I2088057657f3ce23b91dbbc7b4f5840914dbcaa8 + +2017-10-23 David Tardon [5634c05b8f2ee456fc3bcc969bf688905d2011ac] + + bump version + + Change-Id: Ic8f0c5bcda18c02f0e7e3e4945589bccc82e5d4e + 2017-10-23 David Tardon [423b931132454d3a0661b210afdbff3a44bb5999] prepare for a release diff -Nru libetonyek-0.1.7/compile libetonyek-0.1.8/compile --- libetonyek-0.1.7/compile 2017-04-07 12:01:12.000000000 +0000 +++ libetonyek-0.1.8/compile 2018-03-18 10:16:12.000000000 +0000 @@ -1,9 +1,9 @@ #! /bin/sh # Wrapper for compilers which do not understand '-c -o'. -scriptversion=2012-10-14.11; # UTC +scriptversion=2016-01-11.22; # UTC -# Copyright (C) 1999-2014 Free Software Foundation, Inc. +# Copyright (C) 1999-2017 Free Software Foundation, Inc. # Written by Tom Tromey . # # This program is free software; you can redistribute it and/or modify @@ -255,7 +255,8 @@ echo "compile $scriptversion" exit $? ;; - cl | *[/\\]cl | cl.exe | *[/\\]cl.exe ) + cl | *[/\\]cl | cl.exe | *[/\\]cl.exe | \ + icl | *[/\\]icl | icl.exe | *[/\\]icl.exe ) func_cl_wrapper "$@" # Doesn't return... ;; esac @@ -342,6 +343,6 @@ # eval: (add-hook 'write-file-hooks 'time-stamp) # time-stamp-start: "scriptversion=" # time-stamp-format: "%:y-%02m-%02d.%02H" -# time-stamp-time-zone: "UTC" +# time-stamp-time-zone: "UTC0" # time-stamp-end: "; # UTC" # End: diff -Nru libetonyek-0.1.7/configure libetonyek-0.1.8/configure --- libetonyek-0.1.7/configure 2017-10-23 08:03:59.000000000 +0000 +++ libetonyek-0.1.8/configure 2018-03-18 13:51:51.000000000 +0000 @@ -1,6 +1,6 @@ #! /bin/sh # Guess values for system-dependent variables and create Makefiles. -# Generated by GNU Autoconf 2.69 for libetonyek 0.1.7. +# Generated by GNU Autoconf 2.69 for libetonyek 0.1.8. # # # Copyright (C) 1992-1996, 1998-2012 Free Software Foundation, Inc. @@ -587,8 +587,8 @@ # Identity of this package. PACKAGE_NAME='libetonyek' PACKAGE_TARNAME='libetonyek' -PACKAGE_VERSION='0.1.7' -PACKAGE_STRING='libetonyek 0.1.7' +PACKAGE_VERSION='0.1.8' +PACKAGE_STRING='libetonyek 0.1.8' PACKAGE_BUGREPORT='' PACKAGE_URL='' @@ -1407,7 +1407,7 @@ # Omit some internal or obsolete options to make the list less imposing. # This message is too long to be a string in the A/UX 3.1 sh. cat <<_ACEOF -\`configure' configures libetonyek 0.1.7 to adapt to many kinds of systems. +\`configure' configures libetonyek 0.1.8 to adapt to many kinds of systems. Usage: $0 [OPTION]... [VAR=VALUE]... @@ -1477,7 +1477,7 @@ if test -n "$ac_init_help"; then case $ac_init_help in - short | recursive ) echo "Configuration of libetonyek 0.1.7:";; + short | recursive ) echo "Configuration of libetonyek 0.1.8:";; esac cat <<\_ACEOF @@ -1633,7 +1633,7 @@ test -n "$ac_init_help" && exit $ac_status if $ac_init_version; then cat <<\_ACEOF -libetonyek configure 0.1.7 +libetonyek configure 0.1.8 generated by GNU Autoconf 2.69 Copyright (C) 2012 Free Software Foundation, Inc. @@ -2029,93 +2029,6 @@ } # ac_fn_cxx_try_link -# ac_fn_cxx_check_header_mongrel LINENO HEADER VAR INCLUDES -# --------------------------------------------------------- -# Tests whether HEADER exists, giving a warning if it cannot be compiled using -# the include files in INCLUDES and setting the cache variable VAR -# accordingly. -ac_fn_cxx_check_header_mongrel () -{ - as_lineno=${as_lineno-"$1"} as_lineno_stack=as_lineno_stack=$as_lineno_stack - if eval \${$3+:} false; then : - { $as_echo "$as_me:${as_lineno-$LINENO}: checking for $2" >&5 -$as_echo_n "checking for $2... " >&6; } -if eval \${$3+:} false; then : - $as_echo_n "(cached) " >&6 -fi -eval ac_res=\$$3 - { $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_res" >&5 -$as_echo "$ac_res" >&6; } -else - # Is the header compilable? -{ $as_echo "$as_me:${as_lineno-$LINENO}: checking $2 usability" >&5 -$as_echo_n "checking $2 usability... " >&6; } -cat confdefs.h - <<_ACEOF >conftest.$ac_ext -/* end confdefs.h. */ -$4 -#include <$2> -_ACEOF -if ac_fn_cxx_try_compile "$LINENO"; then : - ac_header_compiler=yes -else - ac_header_compiler=no -fi -rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext -{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_header_compiler" >&5 -$as_echo "$ac_header_compiler" >&6; } - -# Is the header present? -{ $as_echo "$as_me:${as_lineno-$LINENO}: checking $2 presence" >&5 -$as_echo_n "checking $2 presence... " >&6; } -cat confdefs.h - <<_ACEOF >conftest.$ac_ext -/* end confdefs.h. */ -#include <$2> -_ACEOF -if ac_fn_cxx_try_cpp "$LINENO"; then : - ac_header_preproc=yes -else - ac_header_preproc=no -fi -rm -f conftest.err conftest.i conftest.$ac_ext -{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_header_preproc" >&5 -$as_echo "$ac_header_preproc" >&6; } - -# So? What about this header? -case $ac_header_compiler:$ac_header_preproc:$ac_cxx_preproc_warn_flag in #(( - yes:no: ) - { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $2: accepted by the compiler, rejected by the preprocessor!" >&5 -$as_echo "$as_me: WARNING: $2: accepted by the compiler, rejected by the preprocessor!" >&2;} - { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $2: proceeding with the compiler's result" >&5 -$as_echo "$as_me: WARNING: $2: proceeding with the compiler's result" >&2;} - ;; - no:yes:* ) - { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $2: present but cannot be compiled" >&5 -$as_echo "$as_me: WARNING: $2: present but cannot be compiled" >&2;} - { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $2: check for missing prerequisite headers?" >&5 -$as_echo "$as_me: WARNING: $2: check for missing prerequisite headers?" >&2;} - { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $2: see the Autoconf documentation" >&5 -$as_echo "$as_me: WARNING: $2: see the Autoconf documentation" >&2;} - { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $2: section \"Present But Cannot Be Compiled\"" >&5 -$as_echo "$as_me: WARNING: $2: section \"Present But Cannot Be Compiled\"" >&2;} - { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $2: proceeding with the compiler's result" >&5 -$as_echo "$as_me: WARNING: $2: proceeding with the compiler's result" >&2;} - ;; -esac - { $as_echo "$as_me:${as_lineno-$LINENO}: checking for $2" >&5 -$as_echo_n "checking for $2... " >&6; } -if eval \${$3+:} false; then : - $as_echo_n "(cached) " >&6 -else - eval "$3=\$ac_header_compiler" -fi -eval ac_res=\$$3 - { $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_res" >&5 -$as_echo "$ac_res" >&6; } -fi - eval $as_lineno_stack; ${as_lineno_stack:+:} unset as_lineno - -} # ac_fn_cxx_check_header_mongrel - # ac_fn_cxx_check_header_compile LINENO HEADER VAR INCLUDES # --------------------------------------------------------- # Tests whether HEADER exists and can be compiled using the include files in @@ -2150,7 +2063,7 @@ This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. -It was created by libetonyek $as_me 0.1.7, which was +It was created by libetonyek $as_me 0.1.8, which was generated by GNU Autoconf 2.69. Invocation command line was $ $0 $@ @@ -3016,7 +2929,7 @@ # Define the identity of the package. PACKAGE='libetonyek' - VERSION='0.1.7' + VERSION='0.1.8' cat >>confdefs.h <<_ACEOF @@ -17490,7 +17403,7 @@ #error "This is not a C++ compiler" -#elif __cplusplus < 201103L +#elif __cplusplus < 201103L && !(defined _MSC_VER) #error "This is not a C++11 compiler" @@ -17802,7 +17715,7 @@ #error "This is not a C++ compiler" -#elif __cplusplus < 201103L +#elif __cplusplus < 201103L && !(defined _MSC_VER) #error "This is not a C++11 compiler" @@ -18123,7 +18036,7 @@ #error "This is not a C++ compiler" -#elif __cplusplus < 201103L +#elif __cplusplus < 201103L && !(defined _MSC_VER) #error "This is not a C++11 compiler" @@ -18558,8 +18471,8 @@ - { $as_echo "$as_me:${as_lineno-$LINENO}: checking for [[clang:fallthrough]]" >&5 -$as_echo_n "checking for [[clang:fallthrough]]... " >&6; } + { $as_echo "$as_me:${as_lineno-$LINENO}: checking for [[clang::fallthrough]]" >&5 +$as_echo_n "checking for [[clang::fallthrough]]... " >&6; } if ${ax_cv_have_clang_attribute_falltrough+:} false; then : $as_echo_n "(cached) " >&6 else @@ -18573,7 +18486,7 @@ { case 0: i += 1; - [[clang:fallthrough]]; + [[clang::fallthrough]]; default: i += 1; } @@ -18628,18 +18541,12 @@ pkg_cv_REVENGE_CFLAGS="$REVENGE_CFLAGS" elif test -n "$PKG_CONFIG"; then if test -n "$PKG_CONFIG" && \ - { { $as_echo "$as_me:${as_lineno-$LINENO}: \$PKG_CONFIG --exists --print-errors \" - librevenge-0.0 -\""; } >&5 - ($PKG_CONFIG --exists --print-errors " - librevenge-0.0 -") 2>&5 + { { $as_echo "$as_me:${as_lineno-$LINENO}: \$PKG_CONFIG --exists --print-errors \"librevenge-0.0\""; } >&5 + ($PKG_CONFIG --exists --print-errors "librevenge-0.0") 2>&5 ac_status=$? $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5 test $ac_status = 0; }; then - pkg_cv_REVENGE_CFLAGS=`$PKG_CONFIG --cflags " - librevenge-0.0 -" 2>/dev/null` + pkg_cv_REVENGE_CFLAGS=`$PKG_CONFIG --cflags "librevenge-0.0" 2>/dev/null` test "x$?" != "x0" && pkg_failed=yes else pkg_failed=yes @@ -18651,18 +18558,12 @@ pkg_cv_REVENGE_LIBS="$REVENGE_LIBS" elif test -n "$PKG_CONFIG"; then if test -n "$PKG_CONFIG" && \ - { { $as_echo "$as_me:${as_lineno-$LINENO}: \$PKG_CONFIG --exists --print-errors \" - librevenge-0.0 -\""; } >&5 - ($PKG_CONFIG --exists --print-errors " - librevenge-0.0 -") 2>&5 + { { $as_echo "$as_me:${as_lineno-$LINENO}: \$PKG_CONFIG --exists --print-errors \"librevenge-0.0\""; } >&5 + ($PKG_CONFIG --exists --print-errors "librevenge-0.0") 2>&5 ac_status=$? $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5 test $ac_status = 0; }; then - pkg_cv_REVENGE_LIBS=`$PKG_CONFIG --libs " - librevenge-0.0 -" 2>/dev/null` + pkg_cv_REVENGE_LIBS=`$PKG_CONFIG --libs "librevenge-0.0" 2>/dev/null` test "x$?" != "x0" && pkg_failed=yes else pkg_failed=yes @@ -18683,20 +18584,14 @@ _pkg_short_errors_supported=no fi if test $_pkg_short_errors_supported = yes; then - REVENGE_PKG_ERRORS=`$PKG_CONFIG --short-errors --print-errors --cflags --libs " - librevenge-0.0 -" 2>&1` + REVENGE_PKG_ERRORS=`$PKG_CONFIG --short-errors --print-errors --cflags --libs "librevenge-0.0" 2>&1` else - REVENGE_PKG_ERRORS=`$PKG_CONFIG --print-errors --cflags --libs " - librevenge-0.0 -" 2>&1` + REVENGE_PKG_ERRORS=`$PKG_CONFIG --print-errors --cflags --libs "librevenge-0.0" 2>&1` fi # Put the nasty error message in config.log where it belongs echo "$REVENGE_PKG_ERRORS" >&5 - as_fn_error $? "Package requirements ( - librevenge-0.0 -) were not met: + as_fn_error $? "Package requirements (librevenge-0.0) were not met: $REVENGE_PKG_ERRORS @@ -18743,18 +18638,12 @@ pkg_cv_XML_CFLAGS="$XML_CFLAGS" elif test -n "$PKG_CONFIG"; then if test -n "$PKG_CONFIG" && \ - { { $as_echo "$as_me:${as_lineno-$LINENO}: \$PKG_CONFIG --exists --print-errors \" - libxml-2.0 -\""; } >&5 - ($PKG_CONFIG --exists --print-errors " - libxml-2.0 -") 2>&5 + { { $as_echo "$as_me:${as_lineno-$LINENO}: \$PKG_CONFIG --exists --print-errors \"libxml-2.0\""; } >&5 + ($PKG_CONFIG --exists --print-errors "libxml-2.0") 2>&5 ac_status=$? $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5 test $ac_status = 0; }; then - pkg_cv_XML_CFLAGS=`$PKG_CONFIG --cflags " - libxml-2.0 -" 2>/dev/null` + pkg_cv_XML_CFLAGS=`$PKG_CONFIG --cflags "libxml-2.0" 2>/dev/null` test "x$?" != "x0" && pkg_failed=yes else pkg_failed=yes @@ -18766,18 +18655,12 @@ pkg_cv_XML_LIBS="$XML_LIBS" elif test -n "$PKG_CONFIG"; then if test -n "$PKG_CONFIG" && \ - { { $as_echo "$as_me:${as_lineno-$LINENO}: \$PKG_CONFIG --exists --print-errors \" - libxml-2.0 -\""; } >&5 - ($PKG_CONFIG --exists --print-errors " - libxml-2.0 -") 2>&5 + { { $as_echo "$as_me:${as_lineno-$LINENO}: \$PKG_CONFIG --exists --print-errors \"libxml-2.0\""; } >&5 + ($PKG_CONFIG --exists --print-errors "libxml-2.0") 2>&5 ac_status=$? $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5 test $ac_status = 0; }; then - pkg_cv_XML_LIBS=`$PKG_CONFIG --libs " - libxml-2.0 -" 2>/dev/null` + pkg_cv_XML_LIBS=`$PKG_CONFIG --libs "libxml-2.0" 2>/dev/null` test "x$?" != "x0" && pkg_failed=yes else pkg_failed=yes @@ -18798,20 +18681,14 @@ _pkg_short_errors_supported=no fi if test $_pkg_short_errors_supported = yes; then - XML_PKG_ERRORS=`$PKG_CONFIG --short-errors --print-errors --cflags --libs " - libxml-2.0 -" 2>&1` + XML_PKG_ERRORS=`$PKG_CONFIG --short-errors --print-errors --cflags --libs "libxml-2.0" 2>&1` else - XML_PKG_ERRORS=`$PKG_CONFIG --print-errors --cflags --libs " - libxml-2.0 -" 2>&1` + XML_PKG_ERRORS=`$PKG_CONFIG --print-errors --cflags --libs "libxml-2.0" 2>&1` fi # Put the nasty error message in config.log where it belongs echo "$XML_PKG_ERRORS" >&5 - as_fn_error $? "Package requirements ( - libxml-2.0 -) were not met: + as_fn_error $? "Package requirements (libxml-2.0) were not met: $XML_PKG_ERRORS @@ -18848,7 +18725,6 @@ # Find zlib # ========= - pkg_failed=no { $as_echo "$as_me:${as_lineno-$LINENO}: checking for ZLIB" >&5 $as_echo_n "checking for ZLIB... " >&6; } @@ -18907,113 +18783,31 @@ # Put the nasty error message in config.log where it belongs echo "$ZLIB_PKG_ERRORS" >&5 + as_fn_error $? "Package requirements (zlib) were not met: - ac_fn_cxx_check_header_mongrel "$LINENO" "zlib.h" "ac_cv_header_zlib_h" "$ac_includes_default" -if test "x$ac_cv_header_zlib_h" = xyes; then : - ZLIB_CFLAGS= -else - as_fn_error $? "zlib.h not found. install zlib" "$LINENO" 5 -fi - - - { $as_echo "$as_me:${as_lineno-$LINENO}: checking for inflate in -lz" >&5 -$as_echo_n "checking for inflate in -lz... " >&6; } -if ${ac_cv_lib_z_inflate+:} false; then : - $as_echo_n "(cached) " >&6 -else - ac_check_lib_save_LIBS=$LIBS -LIBS="-lz $LIBS" -cat confdefs.h - <<_ACEOF >conftest.$ac_ext -/* end confdefs.h. */ - -/* Override any GCC internal prototype to avoid an error. - Use char because int might match the return type of a GCC - builtin and then its argument prototype would still apply. */ -#ifdef __cplusplus -extern "C" -#endif -char inflate (); -int -main () -{ -return inflate (); - ; - return 0; -} -_ACEOF -if ac_fn_cxx_try_link "$LINENO"; then : - ac_cv_lib_z_inflate=yes -else - ac_cv_lib_z_inflate=no -fi -rm -f core conftest.err conftest.$ac_objext \ - conftest$ac_exeext conftest.$ac_ext -LIBS=$ac_check_lib_save_LIBS -fi -{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_lib_z_inflate" >&5 -$as_echo "$ac_cv_lib_z_inflate" >&6; } -if test "x$ac_cv_lib_z_inflate" = xyes; then : - ZLIB_LIBS=-lz -else - as_fn_error $? "zlib not found or functional" "$LINENO" 5 -fi +$ZLIB_PKG_ERRORS +Consider adjusting the PKG_CONFIG_PATH environment variable if you +installed software in a non-standard prefix. +Alternatively, you may set the environment variables ZLIB_CFLAGS +and ZLIB_LIBS to avoid the need to call pkg-config. +See the pkg-config man page for more details." "$LINENO" 5 elif test $pkg_failed = untried; then { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5 $as_echo "no" >&6; } + { { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5 +$as_echo "$as_me: error: in \`$ac_pwd':" >&2;} +as_fn_error $? "The pkg-config script could not be found or is too old. Make sure it +is in your PATH or set the PKG_CONFIG environment variable to the full +path to pkg-config. - ac_fn_cxx_check_header_mongrel "$LINENO" "zlib.h" "ac_cv_header_zlib_h" "$ac_includes_default" -if test "x$ac_cv_header_zlib_h" = xyes; then : - ZLIB_CFLAGS= -else - as_fn_error $? "zlib.h not found. install zlib" "$LINENO" 5 -fi - - - { $as_echo "$as_me:${as_lineno-$LINENO}: checking for inflate in -lz" >&5 -$as_echo_n "checking for inflate in -lz... " >&6; } -if ${ac_cv_lib_z_inflate+:} false; then : - $as_echo_n "(cached) " >&6 -else - ac_check_lib_save_LIBS=$LIBS -LIBS="-lz $LIBS" -cat confdefs.h - <<_ACEOF >conftest.$ac_ext -/* end confdefs.h. */ - -/* Override any GCC internal prototype to avoid an error. - Use char because int might match the return type of a GCC - builtin and then its argument prototype would still apply. */ -#ifdef __cplusplus -extern "C" -#endif -char inflate (); -int -main () -{ -return inflate (); - ; - return 0; -} -_ACEOF -if ac_fn_cxx_try_link "$LINENO"; then : - ac_cv_lib_z_inflate=yes -else - ac_cv_lib_z_inflate=no -fi -rm -f core conftest.err conftest.$ac_objext \ - conftest$ac_exeext conftest.$ac_ext -LIBS=$ac_check_lib_save_LIBS -fi -{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_lib_z_inflate" >&5 -$as_echo "$ac_cv_lib_z_inflate" >&6; } -if test "x$ac_cv_lib_z_inflate" = xyes; then : - ZLIB_LIBS=-lz -else - as_fn_error $? "zlib not found or functional" "$LINENO" 5 -fi - +Alternatively, you may set the environment variables ZLIB_CFLAGS +and ZLIB_LIBS to avoid the need to call pkg-config. +See the pkg-config man page for more details. +To get pkg-config, see . +See \`config.log' for more details" "$LINENO" 5; } else ZLIB_CFLAGS=$pkg_cv_ZLIB_CFLAGS ZLIB_LIBS=$pkg_cv_ZLIB_LIBS @@ -19047,18 +18841,12 @@ pkg_cv_LANGTAG_CFLAGS="$LANGTAG_CFLAGS" elif test -n "$PKG_CONFIG"; then if test -n "$PKG_CONFIG" && \ - { { $as_echo "$as_me:${as_lineno-$LINENO}: \$PKG_CONFIG --exists --print-errors \" - liblangtag - \""; } >&5 - ($PKG_CONFIG --exists --print-errors " - liblangtag - ") 2>&5 + { { $as_echo "$as_me:${as_lineno-$LINENO}: \$PKG_CONFIG --exists --print-errors \"liblangtag\""; } >&5 + ($PKG_CONFIG --exists --print-errors "liblangtag") 2>&5 ac_status=$? $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5 test $ac_status = 0; }; then - pkg_cv_LANGTAG_CFLAGS=`$PKG_CONFIG --cflags " - liblangtag - " 2>/dev/null` + pkg_cv_LANGTAG_CFLAGS=`$PKG_CONFIG --cflags "liblangtag" 2>/dev/null` test "x$?" != "x0" && pkg_failed=yes else pkg_failed=yes @@ -19070,18 +18858,12 @@ pkg_cv_LANGTAG_LIBS="$LANGTAG_LIBS" elif test -n "$PKG_CONFIG"; then if test -n "$PKG_CONFIG" && \ - { { $as_echo "$as_me:${as_lineno-$LINENO}: \$PKG_CONFIG --exists --print-errors \" - liblangtag - \""; } >&5 - ($PKG_CONFIG --exists --print-errors " - liblangtag - ") 2>&5 + { { $as_echo "$as_me:${as_lineno-$LINENO}: \$PKG_CONFIG --exists --print-errors \"liblangtag\""; } >&5 + ($PKG_CONFIG --exists --print-errors "liblangtag") 2>&5 ac_status=$? $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5 test $ac_status = 0; }; then - pkg_cv_LANGTAG_LIBS=`$PKG_CONFIG --libs " - liblangtag - " 2>/dev/null` + pkg_cv_LANGTAG_LIBS=`$PKG_CONFIG --libs "liblangtag" 2>/dev/null` test "x$?" != "x0" && pkg_failed=yes else pkg_failed=yes @@ -19102,20 +18884,14 @@ _pkg_short_errors_supported=no fi if test $_pkg_short_errors_supported = yes; then - LANGTAG_PKG_ERRORS=`$PKG_CONFIG --short-errors --print-errors --cflags --libs " - liblangtag - " 2>&1` + LANGTAG_PKG_ERRORS=`$PKG_CONFIG --short-errors --print-errors --cflags --libs "liblangtag" 2>&1` else - LANGTAG_PKG_ERRORS=`$PKG_CONFIG --print-errors --cflags --libs " - liblangtag - " 2>&1` + LANGTAG_PKG_ERRORS=`$PKG_CONFIG --print-errors --cflags --libs "liblangtag" 2>&1` fi # Put the nasty error message in config.log where it belongs echo "$LANGTAG_PKG_ERRORS" >&5 - as_fn_error $? "Package requirements ( - liblangtag - ) were not met: + as_fn_error $? "Package requirements (liblangtag) were not met: $LANGTAG_PKG_ERRORS @@ -19453,9 +19229,9 @@ ETONYEK_MINOR_VERSION=1 -ETONYEK_MICRO_VERSION=7 +ETONYEK_MICRO_VERSION=8 -KN_VERSION=0.1.7 +KN_VERSION=0.1.8 # AC_SUBST(LT_RELEASE, [libetonyek_version_major.libetonyek_version_minor]) LT_CURRENT=`expr 100 '*' 0 + 1` @@ -19463,7 +19239,7 @@ LT_AGE=0 # LT_AGE=libetonyek_version_minor -LT_REVISION=7 +LT_REVISION=8 @@ -19743,7 +19519,15 @@ fi CFLAGS="$CFLAGS -Wall -Wextra -pedantic" - CXXFLAGS="$CXXFLAGS -Wall -Wextra -pedantic -Wshadow -Wunused-variable" + CXXFLAGS="$CXXFLAGS -Wall -Wextra -pedantic -Wshadow -Wunused-variable" + +else + + if test x"$GCC" = xyes; then : + + # Be tough with warnings and produce less careless code + CFLAGS="$CFLAGS -Wall -Wextra -pedantic" + CXXFLAGS="$CXXFLAGS -Wall -Wextra -Wshadow -pedantic" if test x"$enable_weffc" != "xno"; then : CXXFLAGS="$CXXFLAGS -Weffc++" @@ -19769,14 +19553,6 @@ fi -else - - if test x"$GCC" = xyes; then : - - # Be tough with warnings and produce less careless code - CFLAGS="$CFLAGS -Wall -Wextra -pedantic" - CXXFLAGS="$CXXFLAGS -Wall -Wextra -Wshadow -pedantic" - fi fi @@ -20149,18 +19925,12 @@ pkg_cv_REVENGE_GENERATORS_CFLAGS="$REVENGE_GENERATORS_CFLAGS" elif test -n "$PKG_CONFIG"; then if test -n "$PKG_CONFIG" && \ - { { $as_echo "$as_me:${as_lineno-$LINENO}: \$PKG_CONFIG --exists --print-errors \" - librevenge-generators-0.0 - \""; } >&5 - ($PKG_CONFIG --exists --print-errors " - librevenge-generators-0.0 - ") 2>&5 + { { $as_echo "$as_me:${as_lineno-$LINENO}: \$PKG_CONFIG --exists --print-errors \"librevenge-generators-0.0\""; } >&5 + ($PKG_CONFIG --exists --print-errors "librevenge-generators-0.0") 2>&5 ac_status=$? $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5 test $ac_status = 0; }; then - pkg_cv_REVENGE_GENERATORS_CFLAGS=`$PKG_CONFIG --cflags " - librevenge-generators-0.0 - " 2>/dev/null` + pkg_cv_REVENGE_GENERATORS_CFLAGS=`$PKG_CONFIG --cflags "librevenge-generators-0.0" 2>/dev/null` test "x$?" != "x0" && pkg_failed=yes else pkg_failed=yes @@ -20172,18 +19942,12 @@ pkg_cv_REVENGE_GENERATORS_LIBS="$REVENGE_GENERATORS_LIBS" elif test -n "$PKG_CONFIG"; then if test -n "$PKG_CONFIG" && \ - { { $as_echo "$as_me:${as_lineno-$LINENO}: \$PKG_CONFIG --exists --print-errors \" - librevenge-generators-0.0 - \""; } >&5 - ($PKG_CONFIG --exists --print-errors " - librevenge-generators-0.0 - ") 2>&5 + { { $as_echo "$as_me:${as_lineno-$LINENO}: \$PKG_CONFIG --exists --print-errors \"librevenge-generators-0.0\""; } >&5 + ($PKG_CONFIG --exists --print-errors "librevenge-generators-0.0") 2>&5 ac_status=$? $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5 test $ac_status = 0; }; then - pkg_cv_REVENGE_GENERATORS_LIBS=`$PKG_CONFIG --libs " - librevenge-generators-0.0 - " 2>/dev/null` + pkg_cv_REVENGE_GENERATORS_LIBS=`$PKG_CONFIG --libs "librevenge-generators-0.0" 2>/dev/null` test "x$?" != "x0" && pkg_failed=yes else pkg_failed=yes @@ -20204,20 +19968,14 @@ _pkg_short_errors_supported=no fi if test $_pkg_short_errors_supported = yes; then - REVENGE_GENERATORS_PKG_ERRORS=`$PKG_CONFIG --short-errors --print-errors --cflags --libs " - librevenge-generators-0.0 - " 2>&1` + REVENGE_GENERATORS_PKG_ERRORS=`$PKG_CONFIG --short-errors --print-errors --cflags --libs "librevenge-generators-0.0" 2>&1` else - REVENGE_GENERATORS_PKG_ERRORS=`$PKG_CONFIG --print-errors --cflags --libs " - librevenge-generators-0.0 - " 2>&1` + REVENGE_GENERATORS_PKG_ERRORS=`$PKG_CONFIG --print-errors --cflags --libs "librevenge-generators-0.0" 2>&1` fi # Put the nasty error message in config.log where it belongs echo "$REVENGE_GENERATORS_PKG_ERRORS" >&5 - as_fn_error $? "Package requirements ( - librevenge-generators-0.0 - ) were not met: + as_fn_error $? "Package requirements (librevenge-generators-0.0) were not met: $REVENGE_GENERATORS_PKG_ERRORS @@ -20258,18 +20016,12 @@ pkg_cv_REVENGE_STREAM_CFLAGS="$REVENGE_STREAM_CFLAGS" elif test -n "$PKG_CONFIG"; then if test -n "$PKG_CONFIG" && \ - { { $as_echo "$as_me:${as_lineno-$LINENO}: \$PKG_CONFIG --exists --print-errors \" - librevenge-stream-0.0 - \""; } >&5 - ($PKG_CONFIG --exists --print-errors " - librevenge-stream-0.0 - ") 2>&5 + { { $as_echo "$as_me:${as_lineno-$LINENO}: \$PKG_CONFIG --exists --print-errors \"librevenge-stream-0.0\""; } >&5 + ($PKG_CONFIG --exists --print-errors "librevenge-stream-0.0") 2>&5 ac_status=$? $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5 test $ac_status = 0; }; then - pkg_cv_REVENGE_STREAM_CFLAGS=`$PKG_CONFIG --cflags " - librevenge-stream-0.0 - " 2>/dev/null` + pkg_cv_REVENGE_STREAM_CFLAGS=`$PKG_CONFIG --cflags "librevenge-stream-0.0" 2>/dev/null` test "x$?" != "x0" && pkg_failed=yes else pkg_failed=yes @@ -20281,18 +20033,12 @@ pkg_cv_REVENGE_STREAM_LIBS="$REVENGE_STREAM_LIBS" elif test -n "$PKG_CONFIG"; then if test -n "$PKG_CONFIG" && \ - { { $as_echo "$as_me:${as_lineno-$LINENO}: \$PKG_CONFIG --exists --print-errors \" - librevenge-stream-0.0 - \""; } >&5 - ($PKG_CONFIG --exists --print-errors " - librevenge-stream-0.0 - ") 2>&5 + { { $as_echo "$as_me:${as_lineno-$LINENO}: \$PKG_CONFIG --exists --print-errors \"librevenge-stream-0.0\""; } >&5 + ($PKG_CONFIG --exists --print-errors "librevenge-stream-0.0") 2>&5 ac_status=$? $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5 test $ac_status = 0; }; then - pkg_cv_REVENGE_STREAM_LIBS=`$PKG_CONFIG --libs " - librevenge-stream-0.0 - " 2>/dev/null` + pkg_cv_REVENGE_STREAM_LIBS=`$PKG_CONFIG --libs "librevenge-stream-0.0" 2>/dev/null` test "x$?" != "x0" && pkg_failed=yes else pkg_failed=yes @@ -20313,20 +20059,14 @@ _pkg_short_errors_supported=no fi if test $_pkg_short_errors_supported = yes; then - REVENGE_STREAM_PKG_ERRORS=`$PKG_CONFIG --short-errors --print-errors --cflags --libs " - librevenge-stream-0.0 - " 2>&1` + REVENGE_STREAM_PKG_ERRORS=`$PKG_CONFIG --short-errors --print-errors --cflags --libs "librevenge-stream-0.0" 2>&1` else - REVENGE_STREAM_PKG_ERRORS=`$PKG_CONFIG --print-errors --cflags --libs " - librevenge-stream-0.0 - " 2>&1` + REVENGE_STREAM_PKG_ERRORS=`$PKG_CONFIG --print-errors --cflags --libs "librevenge-stream-0.0" 2>&1` fi # Put the nasty error message in config.log where it belongs echo "$REVENGE_STREAM_PKG_ERRORS" >&5 - as_fn_error $? "Package requirements ( - librevenge-stream-0.0 - ) were not met: + as_fn_error $? "Package requirements (librevenge-stream-0.0) were not met: $REVENGE_STREAM_PKG_ERRORS @@ -20936,7 +20676,7 @@ # report actual input values of CONFIG_FILES etc. instead of their # values after options handling. ac_log=" -This file was extended by libetonyek $as_me 0.1.7, which was +This file was extended by libetonyek $as_me 0.1.8, which was generated by GNU Autoconf 2.69. Invocation command line was CONFIG_FILES = $CONFIG_FILES @@ -21002,7 +20742,7 @@ cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1 ac_cs_config="`$as_echo "$ac_configure_args" | sed 's/^ //; s/[\\""\`\$]/\\\\&/g'`" ac_cs_version="\\ -libetonyek config.status 0.1.7 +libetonyek config.status 0.1.8 configured by $0, generated by GNU Autoconf 2.69, with options \\"\$ac_cs_config\\" diff -Nru libetonyek-0.1.7/configure.ac libetonyek-0.1.8/configure.ac --- libetonyek-0.1.7/configure.ac 2017-10-23 08:03:31.000000000 +0000 +++ libetonyek-0.1.8/configure.ac 2018-03-18 13:51:31.000000000 +0000 @@ -7,7 +7,7 @@ # ==================== m4_define([libetonyek_version_major],[0]) m4_define([libetonyek_version_minor],[1]) -m4_define([libetonyek_version_micro],[7]) +m4_define([libetonyek_version_micro],[8]) m4_define([libetonyek_version],[libetonyek_version_major.libetonyek_version_minor.libetonyek_version_micro]) # ============= @@ -54,28 +54,19 @@ # =============== # Find librevenge # =============== -PKG_CHECK_MODULES([REVENGE],[ - librevenge-0.0 -]) +PKG_CHECK_MODULES([REVENGE],[librevenge-0.0]) AC_SUBST([REVENGE_CFLAGS]) AC_SUBST([REVENGE_LIBS]) # ============ # Find libxml2 # ============ -PKG_CHECK_MODULES([XML],[ - libxml-2.0 -]) +PKG_CHECK_MODULES([XML],[libxml-2.0]) # ========= # Find zlib # ========= -PKG_CHECK_MODULES([ZLIB],[zlib],[],[ - AC_CHECK_HEADER(zlib.h, [ZLIB_CFLAGS=], - [AC_MSG_ERROR(zlib.h not found. install zlib)], []) - AC_CHECK_LIB(z, inflate, [ ZLIB_LIBS=-lz ], - [AC_MSG_ERROR(zlib not found or functional)], []) -]) +PKG_CHECK_MODULES([ZLIB],[zlib]) AC_SUBST(ZLIB_CFLAGS) AC_SUBST(ZLIB_LIBS) @@ -88,9 +79,7 @@ [with_liblangtag="yes"] ) AS_IF([test "x$with_liblangtag" = "xyes"], [ - PKG_CHECK_MODULES([LANGTAG],[ - liblangtag - ]) + PKG_CHECK_MODULES([LANGTAG],[liblangtag]) AC_DEFINE([WITH_LIBLANGTAG], [1], [Build with liblangtag]) ], [] @@ -295,7 +284,12 @@ ]) ]) CFLAGS="$CFLAGS -Wall -Wextra -pedantic" - CXXFLAGS="$CXXFLAGS -Wall -Wextra -pedantic -Wshadow -Wunused-variable" + CXXFLAGS="$CXXFLAGS -Wall -Wextra -pedantic -Wshadow -Wunused-variable" +], [ + AS_IF([test x"$GCC" = xyes], [ + # Be tough with warnings and produce less careless code + CFLAGS="$CFLAGS -Wall -Wextra -pedantic" + CXXFLAGS="$CXXFLAGS -Wall -Wextra -Wshadow -pedantic" AS_IF([test x"$enable_weffc" != "xno"], [ CXXFLAGS="$CXXFLAGS -Weffc++" ]) @@ -316,11 +310,6 @@ CXXFLAGS="$CXXFLAGS -Wunused-value -Wvariadic-macros" CXXFLAGS="$CXXFLAGS -Wvolatile-register-var -Wwrite-strings" ]) -], [ - AS_IF([test x"$GCC" = xyes], [ - # Be tough with warnings and produce less careless code - CFLAGS="$CFLAGS -Wall -Wextra -pedantic" - CXXFLAGS="$CXXFLAGS -Wall -Wextra -Wshadow -pedantic" ]) ]) @@ -397,12 +386,8 @@ AM_CONDITIONAL(BUILD_FUZZERS, [test "x$enable_fuzzers" = "xyes"]) AS_IF([test "x$build_tools" = "xyes" -o "x$enable_fuzzers" = "xyes"], [ - PKG_CHECK_MODULES([REVENGE_GENERATORS],[ - librevenge-generators-0.0 - ]) - PKG_CHECK_MODULES([REVENGE_STREAM],[ - librevenge-stream-0.0 - ]) + PKG_CHECK_MODULES([REVENGE_GENERATORS],[librevenge-generators-0.0]) + PKG_CHECK_MODULES([REVENGE_STREAM],[librevenge-stream-0.0]) ]) AC_SUBST([REVENGE_GENERATORS_CFLAGS]) AC_SUBST([REVENGE_GENERATORS_LIBS]) diff -Nru libetonyek-0.1.7/debian/changelog libetonyek-0.1.8/debian/changelog --- libetonyek-0.1.7/debian/changelog 2018-03-05 07:35:06.000000000 +0000 +++ libetonyek-0.1.8/debian/changelog 2018-04-22 09:20:51.000000000 +0000 @@ -1,3 +1,9 @@ +libetonyek (0.1.8-1) unstable; urgency=medium + + * New upstream version 0.1.8 + + -- Rene Engelhard Sun, 22 Apr 2018 11:20:51 +0200 + libetonyek (0.1.7-3) unstable; urgency=medium * debian/patches/drop-lo-longer-needed-tests.diff, diff -Nru libetonyek-0.1.7/debian/patches/drop-lo-longer-needed-tests.diff libetonyek-0.1.8/debian/patches/drop-lo-longer-needed-tests.diff --- libetonyek-0.1.7/debian/patches/drop-lo-longer-needed-tests.diff 2018-03-05 07:32:53.000000000 +0000 +++ libetonyek-0.1.8/debian/patches/drop-lo-longer-needed-tests.diff 1970-01-01 00:00:00.000000000 +0000 @@ -1,118 +0,0 @@ -From 6aacf0ced2a49a000095339671489db2c07f3ddf Mon Sep 17 00:00:00 2001 -From: David Tardon -Date: Fri, 2 Mar 2018 10:15:13 +0100 -Subject: drop no longer needed tests - -glm matrix transformations are--I sincerely hope--tested in glm. So -these tests haven't been needed since the switch to glm. - -Change-Id: Ib10153c6b6ce4bd792b634ac1a3718203227c58f ---- - src/test/IWORKTransformationTest.cpp | 63 ------------------------------------ - 1 file changed, 63 deletions(-) - -diff --git a/src/test/IWORKTransformationTest.cpp b/src/test/IWORKTransformationTest.cpp -index f6908bc..d94ec1c 100644 ---- a/src/test/IWORKTransformationTest.cpp -+++ b/src/test/IWORKTransformationTest.cpp -@@ -21,10 +21,7 @@ namespace test - { - - using libetonyek::approxEqual; --using libetonyek::etonyek_third_pi; - using libetonyek::etonyek_half_pi; --using libetonyek::etonyek_two_pi; --using libetonyek::etonyek_pi; - - namespace - { -@@ -46,18 +43,12 @@ public: - private: - CPPUNIT_TEST_SUITE(IWORKTransformationTest); - CPPUNIT_TEST(testConstruction); -- CPPUNIT_TEST(testConstructionIdentity); - CPPUNIT_TEST(testConstructionFromGeometry); -- CPPUNIT_TEST(testIdentities); -- CPPUNIT_TEST(testInverseOperations); - CPPUNIT_TEST_SUITE_END(); - - private: - void testConstruction(); -- void testConstructionIdentity(); - void testConstructionFromGeometry(); -- void testIdentities(); -- void testInverseOperations(); - }; - - void IWORKTransformationTest::setUp() -@@ -103,22 +94,6 @@ void IWORKTransformationTest::testConstruction() - #endif - } - --void IWORKTransformationTest::testConstructionIdentity() --{ -- using namespace libetonyek::transformations; -- -- glm::dmat3 eye; -- -- CPPUNIT_ASSERT_EQUAL(eye, center(0, 0)); -- CPPUNIT_ASSERT_EQUAL(eye, origin(0, 0)); -- CPPUNIT_ASSERT_EQUAL(eye, flip(false, false)); -- CPPUNIT_ASSERT_EQUAL(eye, rotate(0)); -- CPPUNIT_ASSERT(approxEqual(rotate(etonyek_two_pi), eye)); -- CPPUNIT_ASSERT_EQUAL(eye, scale(1, 1)); -- CPPUNIT_ASSERT_EQUAL(eye, shear(0, 0)); -- CPPUNIT_ASSERT_EQUAL(eye, translate(0, 0)); --} -- - void IWORKTransformationTest::testConstructionFromGeometry() - { - using namespace libetonyek::transformations; -@@ -203,44 +178,6 @@ void IWORKTransformationTest::testConstructionFromGeometry() - } - } - --void IWORKTransformationTest::testIdentities() --{ -- using namespace libetonyek::transformations; -- -- CPPUNIT_ASSERT_EQUAL(translate(50, 25), center(100, 50)); -- CPPUNIT_ASSERT_EQUAL(translate(-50, -25), origin(100, 50)); -- CPPUNIT_ASSERT_EQUAL(flip(true, true), (flip(true, false) * flip(false, true))); -- CPPUNIT_ASSERT_EQUAL(flip(true, true), (flip(false, true) * flip(true, false))); -- CPPUNIT_ASSERT(approxEqual(rotate(etonyek_half_pi) * rotate(etonyek_third_pi), rotate(etonyek_third_pi) * rotate(etonyek_half_pi))); -- CPPUNIT_ASSERT_EQUAL(flip(true, true), scale(-1, -1)); -- CPPUNIT_ASSERT_EQUAL((translate(10, 20) * translate(80, 40)), (translate(80, 40) * translate(10, 20))); -- CPPUNIT_ASSERT_EQUAL(translate(2, 4) * scale(2, 2), scale(2, 2) * translate(1, 2)); --} -- --void IWORKTransformationTest::testInverseOperations() --{ -- using namespace libetonyek::transformations; -- -- glm::dmat3 eye; -- -- CPPUNIT_ASSERT_EQUAL(eye, center(10, 20) * origin(10, 20)); -- CPPUNIT_ASSERT_EQUAL(eye, origin(10, 20) * center(10, 20)); -- -- CPPUNIT_ASSERT_EQUAL(eye, flip(true, false) * flip(true, false)); -- CPPUNIT_ASSERT_EQUAL(eye, flip(false, true) * flip(false, true)); -- CPPUNIT_ASSERT_EQUAL(eye, flip(true, true) * flip(true, true)); -- -- CPPUNIT_ASSERT_EQUAL(eye, rotate(etonyek_pi) * rotate(-etonyek_pi)); -- -- CPPUNIT_ASSERT_EQUAL(eye, scale(2, 1) * scale(0.5, 1)); -- CPPUNIT_ASSERT_EQUAL(eye, scale(1, 2) * scale(1, 0.5)); -- CPPUNIT_ASSERT_EQUAL(eye, scale(3, 2) * scale(1.0 / 3, 0.5)); -- -- // CPPUNIT_ASSERT_EQUAL(eye, shear()); -- -- CPPUNIT_ASSERT_EQUAL(eye, translate(10, 20) * translate(-10, -20)); --} -- - CPPUNIT_TEST_SUITE_REGISTRATION(IWORKTransformationTest); - - } --- -cgit v1.1 - diff -Nru libetonyek-0.1.7/debian/patches/glm-0.9.9.diff libetonyek-0.1.8/debian/patches/glm-0.9.9.diff --- libetonyek-0.1.7/debian/patches/glm-0.9.9.diff 2018-03-05 07:33:52.000000000 +0000 +++ libetonyek-0.1.8/debian/patches/glm-0.9.9.diff 1970-01-01 00:00:00.000000000 +0000 @@ -1,34 +0,0 @@ -From e157f1f5c76d8408b44c98d7d40d2dc37bb14c7b Mon Sep 17 00:00:00 2001 -From: David Tardon -Date: Sun, 4 Mar 2018 14:21:36 +0100 -Subject: fix build with glm 0.9.9 - -Change-Id: Ife0c761f9ca30ed94115b9e51e123642bd44bf3b ---- - src/test/IWORKTransformationTest.cpp | 3 ++- - 1 file changed, 2 insertions(+), 1 deletion(-) - -diff --git a/src/test/IWORKTransformationTest.cpp b/src/test/IWORKTransformationTest.cpp -index d94ec1c..b40a0e6 100644 ---- a/src/test/IWORKTransformationTest.cpp -+++ b/src/test/IWORKTransformationTest.cpp -@@ -10,6 +10,7 @@ - #include - #include - -+#define GLM_ENABLE_EXPERIMENTAL - #include - - #include "IWORKTransformation.h" -@@ -108,7 +109,7 @@ void IWORKTransformationTest::testConstructionFromGeometry() - g.m_position = IWORKPosition(0, 0); - - const glm::dmat3 tr = makeTransformation(g); -- CPPUNIT_ASSERT_EQUAL(tr, glm::dmat3()); -+ CPPUNIT_ASSERT_EQUAL(tr, glm::dmat3(1, 0, 0, 0, 1, 0, 0, 0, 1)); - } - - { --- -cgit v1.1 - diff -Nru libetonyek-0.1.7/debian/patches/series libetonyek-0.1.8/debian/patches/series --- libetonyek-0.1.7/debian/patches/series 2018-03-05 07:34:14.000000000 +0000 +++ libetonyek-0.1.8/debian/patches/series 1970-01-01 00:00:00.000000000 +0000 @@ -1,2 +0,0 @@ -drop-lo-longer-needed-tests.diff -glm-0.9.9.diff diff -Nru libetonyek-0.1.7/debian/watch libetonyek-0.1.8/debian/watch --- libetonyek-0.1.7/debian/watch 2018-03-05 07:35:06.000000000 +0000 +++ libetonyek-0.1.8/debian/watch 2018-04-22 09:20:25.000000000 +0000 @@ -1,2 +1,2 @@ version=3 -http://dev-www.libreoffice.org/src/libetonyek-(.+)\.tar\.xz +http://dev-www.libreoffice.org/src/libetonyek-(.+)\.tar\.bz2 diff -Nru libetonyek-0.1.7/depcomp libetonyek-0.1.8/depcomp --- libetonyek-0.1.7/depcomp 2017-04-07 12:01:12.000000000 +0000 +++ libetonyek-0.1.8/depcomp 2018-03-18 10:16:13.000000000 +0000 @@ -1,9 +1,9 @@ #! /bin/sh # depcomp - compile a program generating dependencies as side-effects -scriptversion=2013-05-30.07; # UTC +scriptversion=2016-01-11.22; # UTC -# Copyright (C) 1999-2014 Free Software Foundation, Inc. +# Copyright (C) 1999-2017 Free Software Foundation, Inc. # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by @@ -786,6 +786,6 @@ # eval: (add-hook 'write-file-hooks 'time-stamp) # time-stamp-start: "scriptversion=" # time-stamp-format: "%:y-%02m-%02d.%02H" -# time-stamp-time-zone: "UTC" +# time-stamp-time-zone: "UTC0" # time-stamp-end: "; # UTC" # End: diff -Nru libetonyek-0.1.7/docs/doxygen/doxygen.cfg libetonyek-0.1.8/docs/doxygen/doxygen.cfg --- libetonyek-0.1.7/docs/doxygen/doxygen.cfg 2017-04-05 12:02:04.000000000 +0000 +++ libetonyek-0.1.8/docs/doxygen/doxygen.cfg 2018-03-18 10:31:39.000000000 +0000 @@ -1,107 +1,129 @@ -# Doxyfile 1.7.3 +# Doxyfile 1.8.13 # 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. +# All text after a double hash (##) is considered a comment and is placed in +# front of the TAG it is preceding. +# +# All text after a single 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 (" "). +# 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. +# 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. +# The default value is: UTF-8. 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. +# The PROJECT_NAME tag is a single word (or a sequence of words surrounded by +# double-quotes, unless you are using Doxywizard) that should identify the +# project for which the documentation is generated. This name is used in the +# title of most generated pages and in a few other places. +# The default value is: My Project. PROJECT_NAME = libetonyek -# 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. +# 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 = -# Using the PROJECT_BRIEF tag one can provide an optional one line description for a project that appears at the top of each page and should give viewer a quick idea about the purpose of the project. Keep the description short. +# Using the PROJECT_BRIEF tag one can provide an optional one line description +# for a project that appears at the top of each page and should give viewer a +# quick idea about the purpose of the project. Keep the description short. PROJECT_BRIEF = -# With the PROJECT_LOGO tag one can specify an logo or icon that is -# included in the documentation. The maximum height of the logo should not -# exceed 55 pixels and the maximum width should not exceed 200 pixels. -# Doxygen will copy the logo to the output directory. +# With the PROJECT_LOGO tag one can specify a logo or an icon that is included +# in the documentation. The maximum height of the logo should not exceed 55 +# pixels and the maximum width should not exceed 200 pixels. Doxygen will copy +# the logo to the output directory. PROJECT_LOGO = -# 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. +# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path +# into which the generated documentation will be written. 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 = ./ -# 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. +# 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 causes +# performance problems for the file system. +# The default value is: NO. CREATE_SUBDIRS = NO +# If the ALLOW_UNICODE_NAMES tag is set to YES, doxygen will allow non-ASCII +# characters to appear in the names of generated files. If set to NO, non-ASCII +# characters will be escaped, for example _xE3_x81_x84 will be used for Unicode +# U+3044. +# The default value is: NO. + +ALLOW_UNICODE_NAMES = 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, Esperanto, 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-Cyrillic, Slovak, -# Slovene, Spanish, Swedish, Ukrainian, and Vietnamese. +# Possible values are: Afrikaans, Arabic, Armenian, Brazilian, Catalan, Chinese, +# Chinese-Traditional, Croatian, Czech, Danish, Dutch, English (United States), +# Esperanto, Farsi (Persian), Finnish, French, German, Greek, Hungarian, +# Indonesian, Italian, Japanese, Japanese-en (Japanese with English messages), +# Korean, Korean-en (Korean with English messages), Latvian, Lithuanian, +# Macedonian, Norwegian, Persian (Farsi), Polish, Portuguese, Romanian, Russian, +# Serbian, Serbian-Cyrillic, Slovak, Slovene, Spanish, Swedish, Turkish, +# Ukrainian and Vietnamese. +# The default value is: English. 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. +# If the BRIEF_MEMBER_DESC tag is set to YES, 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. +# The default value is: YES. 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 +# If the REPEAT_BRIEF tag is set to YES, 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. +# The default value is: YES. 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" +# 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 and the. ABBREVIATE_BRIEF = # 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 +# doxygen will generate a detailed section even if there is only a brief # description. +# The default value is: NO. ALWAYS_DETAILED_SEC = NO @@ -109,539 +131,711 @@ # 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. +# The default value is: NO. 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. +# If the FULL_PATH_NAMES tag is set to YES, 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 +# The default value is: YES. FULL_PATH_NAMES = NO -# 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. +# 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. +# +# Note that you can specify absolute paths here, but also relative paths, which +# will be relative from the directory where doxygen is started. +# This tag requires that the tag FULL_PATH_NAMES is set to YES. 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. +# 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 list of 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 if your file system -# doesn't support long names like on DOS, Mac, or CD-ROM. +# 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. +# The default value is: NO. 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.) +# 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-style will behave just like regular Qt- +# style comments (thus requiring an explicit @brief command for a brief +# description.) +# The default value is: NO. JAVADOC_AUTOBRIEF = YES -# 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.) +# 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 Qt-style will behave just like regular Qt-style comments (thus +# requiring an explicit \brief command for a brief description.) +# The default value is: NO. 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. +# 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 behavior. 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 behavior instead. +# +# Note that setting this tag to YES also means that rational rose comments are +# not recognized any more. +# The default value is: NO. MULTILINE_CPP_IS_BRIEF = NO -# 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. +# If the INHERIT_DOCS tag is set to YES then an undocumented member inherits the +# documentation from any documented member that it re-implements. +# The default value is: YES. 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. +# 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. +# The default value is: NO. 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. +# 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. +# Minimum value: 1, maximum value: 16, default value: 4. TAB_SIZE = 8 -# 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. +# This tag can be used to specify a number of aliases that act 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. +# This tag can be used to specify a number of word-keyword mappings (TCL only). +# A mapping has the form "name=value". For example adding "class=itcl::class" +# will allow you to use the command class in the itcl::class meaning. + +TCL_SUBST = + +# 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. +# The default value is: NO. 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. +# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java or +# Python sources only. Doxygen will then generate output that is more tailored +# for that language. For instance, namespaces will be presented as packages, +# qualified scopes will look different, etc. +# The default value is: NO. 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. +# sources. Doxygen will then generate output that is tailored for Fortran. +# The default value is: NO. 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. +# sources. Doxygen will then generate output that is tailored for VHDL. +# The default value is: NO. 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, CSharp, 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. Note that for custom extensions -# you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. +# 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 (fixed format Fortran: +# FortranFixed, free formatted Fortran: FortranFree, unknown formatted Fortran: +# Fortran. In the later case the parser tries to guess whether the code is fixed +# or free formatted code, this is the default for Fortran type files), VHDL. 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. +# +# Note: For files without extension you can use no_extension as a placeholder. +# +# Note that for custom extensions you also need to set FILE_PATTERNS otherwise +# the files are not read by doxygen. EXTENSION_MAPPING = +# If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments +# according to the Markdown format, which allows for more readable +# documentation. See http://daringfireball.net/projects/markdown/ for details. +# The output of markdown processing is further processed by doxygen, so you can +# mix doxygen, HTML, and XML commands with Markdown formatting. Disable only in +# case of backward compatibilities issues. +# The default value is: YES. + +MARKDOWN_SUPPORT = YES + +# When the TOC_INCLUDE_HEADINGS tag is set to a non-zero value, all headings up +# to that level are automatically included in the table of contents, even if +# they do not have an id attribute. +# Note: This feature currently applies only to Markdown headings. +# Minimum value: 0, maximum value: 99, default value: 0. +# This tag requires that the tag MARKDOWN_SUPPORT is set to YES. + +TOC_INCLUDE_HEADINGS = 0 + +# When enabled doxygen tries to link words that correspond to documented +# classes, or namespaces to their corresponding documentation. Such a link can +# be prevented in individual cases by putting a % sign in front of the word or +# globally by setting AUTOLINK_SUPPORT to NO. +# The default value is: YES. + +AUTOLINK_SUPPORT = YES + # 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 makes the inheritance and collaboration +# 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); +# versus func(std::string) {}). This also make the inheritance and collaboration # diagrams that involve STL classes more complete and accurate. +# The default value is: NO. BUILTIN_STL_SUPPORT = NO # If you use Microsoft's C++/CLI language, you should set this option to YES to # enable parsing support. +# The default value is: NO. 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. +# Set the SIP_SUPPORT tag to YES if your project consists of sip (see: +# http://www.riverbankcomputing.co.uk/software/sip/intro) 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. +# The default value is: NO. 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 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. +# For Microsoft's IDL there are propget and propput attributes to indicate +# getter and setter methods for a property. Setting this option to YES 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. +# The default value is: YES. 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 +# 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. +# The default value is: NO. 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. +# If one adds a struct or class to a group and this option is enabled, then also +# any nested class or struct is added to the same group. By default this option +# is disabled and one has to add nested compounds explicitly via \ingroup. +# The default value is: NO. + +GROUP_NESTED_COMPOUNDS = NO + +# Set the SUBGROUPING tag to YES 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. +# The default value is: YES. 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 +# When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and unions +# are shown inside the group in which they are included (e.g. using \ingroup) +# instead of on a separate page (for HTML and Man pages) or section (for LaTeX +# and RTF). +# +# Note that this feature does not work in combination with +# SEPARATE_MEMBER_PAGES. +# The default value is: NO. + +INLINE_GROUPED_CLASSES = NO + +# When the INLINE_SIMPLE_STRUCTS tag is set to YES, structs, classes, and unions +# with only public data fields or simple typedef fields will be shown inline in +# the documentation of the scope in which they are defined (i.e. file, +# namespace, or group documentation), provided this scope is documented. If set +# to NO, structs, classes, and unions are shown on a separate page (for HTML and +# Man pages) or section (for LaTeX and RTF). +# The default value is: NO. + +INLINE_SIMPLE_STRUCTS = NO + +# When TYPEDEF_HIDES_STRUCT tag 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 +# 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. +# The default value is: NO. 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 penalty. -# 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 roughly 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 +# The size of the symbol lookup cache can be set using LOOKUP_CACHE_SIZE. This +# cache is used to resolve symbols given their name and scope. Since this can be +# an expensive process and often the same symbol appears multiple times in the +# code, doxygen keeps a cache of pre-resolved symbols. If the cache is too small +# doxygen will become slower. If the cache is too large, memory is wasted. The +# cache size is given by this formula: 2^(16+LOOKUP_CACHE_SIZE). The valid range +# is 0..9, the default is 0, corresponding to a cache size of 2^16=65536 +# symbols. At the end of a run doxygen will report the cache usage and suggest +# the optimal cache size from a speed point of view. +# Minimum value: 0, maximum value: 9, default value: 0. -SYMBOL_CACHE_SIZE = 0 +LOOKUP_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 +# 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 respectively EXTRACT_STATIC tags are set to YES. +# Note: This will also disable the warnings about undocumented members that are +# normally produced when WARNINGS is set to YES. +# The default value is: NO. EXTRACT_ALL = YES -# If the EXTRACT_PRIVATE tag is set to YES all private members of a class -# will be included in the documentation. +# If the EXTRACT_PRIVATE tag is set to YES, all private members of a class will +# be included in the documentation. +# The default value is: NO. EXTRACT_PRIVATE = YES -# If the EXTRACT_STATIC tag is set to YES all static members of a file -# will be included in the documentation. +# If the EXTRACT_PACKAGE tag is set to YES, all members with package or internal +# scope will be included in the documentation. +# The default value is: NO. + +EXTRACT_PACKAGE = NO + +# If the EXTRACT_STATIC tag is set to YES, all static members of a file will be +# included in the documentation. +# The default value is: NO. 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. +# 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. Does not have any effect +# for Java sources. +# The default value is: YES. 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. +# This flag is only useful for Objective-C code. If 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, only methods in the interface are +# included. +# The default value is: NO. 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 namespaces are hidden. +# '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. +# The default value is: NO. 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. +# If the HIDE_UNDOC_MEMBERS tag is set to YES, doxygen will hide all +# undocumented members inside documented classes or files. If set to NO 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. +# The default value is: NO. 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. +# 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, these classes will be included in the various overviews. This option +# has no effect if EXTRACT_ALL is enabled. +# The default value is: NO. 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. +# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, doxygen will hide all friend +# (class|struct|union) declarations. If set to NO, these declarations will be +# included in the documentation. +# The default value is: NO. 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. +# 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, these +# blocks will be appended to the function's detailed documentation block. +# The default value is: NO. 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. +# The INTERNAL_DOCS tag determines if documentation that is typed after a +# \internal command is included. If the tag is set to NO then the documentation +# will be excluded. Set it to YES to include the internal documentation. +# The default value is: NO. 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 +# 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. +# The default value is: system dependent. 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. +# If the HIDE_SCOPE_NAMES tag is set to NO then doxygen will show members with +# their full class and namespace scopes in the documentation. If set to YES, the +# scope will be hidden. +# The default value is: NO. HIDE_SCOPE_NAMES = NO -# 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. +# If the HIDE_COMPOUND_REFERENCE tag is set to NO (default) then doxygen will +# append additional text to a page's title, such as Class Reference. If set to +# YES the compound reference will be hidden. +# The default value is: NO. + +HIDE_COMPOUND_REFERENCE= NO + +# If the SHOW_INCLUDE_FILES tag is set to YES then doxygen will put a list of +# the files that are included by a file in the documentation of that file. +# The default value is: YES. SHOW_INCLUDE_FILES = YES -# If the FORCE_LOCAL_INCLUDES tag is set to YES then Doxygen -# will list include files with double quotes in the documentation -# rather than with sharp brackets. +# If the SHOW_GROUPED_MEMB_INC tag is set to YES then Doxygen will add for each +# grouped member an include statement to the documentation, telling the reader +# which file to include in order to use the member. +# The default value is: NO. + +SHOW_GROUPED_MEMB_INC = NO + +# If the FORCE_LOCAL_INCLUDES tag is set to YES then doxygen will list include +# files with double quotes in the documentation rather than with sharp brackets. +# The default value is: NO. FORCE_LOCAL_INCLUDES = NO -# If the INLINE_INFO tag is set to YES (the default) then a tag [inline] -# is inserted in the documentation for inline members. +# If the INLINE_INFO tag is set to YES then a tag [inline] is inserted in the +# documentation for inline members. +# The default value is: YES. 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. +# If the SORT_MEMBER_DOCS tag is set to YES 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. +# The default value is: YES. 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. +# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the brief +# descriptions of file, namespace and class members alphabetically by member +# name. If set to NO, the members will appear in declaration order. Note that +# this will also influence the order of the classes in the class list. +# The default value is: NO. SORT_BRIEF_DOCS = NO -# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen -# will sort the (brief and detailed) documentation of class members so that -# constructors and destructors are listed first. If set to NO (the default) -# the constructors will appear in the respective orders defined by -# SORT_MEMBER_DOCS and SORT_BRIEF_DOCS. -# This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO -# and ignored for detailed docs if SORT_MEMBER_DOCS is set to NO. +# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen will sort the +# (brief and detailed) documentation of class members so that constructors and +# destructors are listed first. If set to NO the constructors will appear in the +# respective orders defined by SORT_BRIEF_DOCS and SORT_MEMBER_DOCS. +# Note: If SORT_BRIEF_DOCS is set to NO this option is ignored for sorting brief +# member documentation. +# Note: If SORT_MEMBER_DOCS is set to NO this option is ignored for sorting +# detailed member documentation. +# The default value is: NO. SORT_MEMBERS_CTORS_1ST = 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. +# 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 group names will +# appear in their defined order. +# The default value is: NO. 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. +# 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 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. +# Note: This option applies only to the class list, not to the alphabetical +# list. +# The default value is: NO. SORT_BY_SCOPE_NAME = NO -# If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to do proper type resolution of all parameters of a function it will reject a -# match between the prototype and the implementation of a member function even if there is only one candidate or it is obvious which candidate to choose by doing a simple string match. By disabling STRICT_PROTO_MATCHING doxygen -# will still accept a match between prototype and implementation in such cases. +# If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to do proper +# type resolution of all parameters of a function it will reject a match between +# the prototype and the implementation of a member function even if there is +# only one candidate or it is obvious which candidate to choose by doing a +# simple string match. By disabling STRICT_PROTO_MATCHING doxygen will still +# accept a match between prototype and implementation in such cases. +# The default value is: NO. STRICT_PROTO_MATCHING = 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. +# 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. +# The default value is: YES. 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. +# 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. +# The default value is: YES. 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. +# 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. +# The default value is: YES. 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. +# 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. +# The default value is: YES. GENERATE_DEPRECATEDLIST= YES -# The ENABLED_SECTIONS tag can be used to enable conditional -# documentation sections, marked by \if sectionname ... \endif. +# The ENABLED_SECTIONS tag can be used to enable conditional documentation +# sections, marked by \if ... \endif and \cond +# ... \endcond blocks. ENABLED_SECTIONS = -# The MAX_INITIALIZER_LINES tag determines the maximum number of lines -# the initial value of a variable or macro 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 macros in the -# documentation can be controlled using \showinitializer or \hideinitializer -# command in the documentation regardless of this setting. +# The MAX_INITIALIZER_LINES tag determines the maximum number of lines that the +# initial value of a variable or macro / define can have 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 value of individual variables and macros / defines can be +# controlled using \showinitializer or \hideinitializer command in the +# documentation regardless of this setting. +# Minimum value: 0, maximum value: 10000, default value: 30. 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 +# 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. +# The default value is: YES. SHOW_USED_FILES = YES -# 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. +# 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 value 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. +# 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 value 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. +# popen()) the command command input-file, where command is the value of the +# FILE_VERSION_FILTER tag, and input-file is the name of an input file provided +# by doxygen. Whatever the program writes to standard output is used as the file +# version. For an example see the documentation. 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. +# output files in an output format independent way. To 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. +# +# Note that if you run doxygen from a directory containing a file called +# DoxygenLayout.xml, doxygen will parse it automatically even if the LAYOUT_FILE +# tag is left empty. LAYOUT_FILE = +# The CITE_BIB_FILES tag can be used to specify one or more bib files containing +# the reference definitions. This must be a list of .bib files. The .bib +# extension is automatically appended if omitted. This requires the bibtex tool +# to be installed. See also http://en.wikipedia.org/wiki/BibTeX for more info. +# For LaTeX the style of the bibliography can be controlled using +# LATEX_BIB_STYLE. To use this feature you need bibtex and perl available in the +# search path. See also \cite for info how to create references. + +CITE_BIB_FILES = + #--------------------------------------------------------------------------- -# configuration options related to warning and progress messages +# 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. +# The QUIET tag can be used to turn on/off the messages that are generated to +# standard output by doxygen. If QUIET is set to YES this implies that the +# messages are off. +# The default value is: NO. 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. +# generated to standard error (stderr) by doxygen. If WARNINGS is set to YES +# this implies that the warnings are on. +# +# Tip: Turn warnings on while writing the documentation. +# The default value is: YES. 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. +# If the WARN_IF_UNDOCUMENTED tag 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. +# The default value is: YES. 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. +# If the WARN_IF_DOC_ERROR tag 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. +# The default value is: YES. WARN_IF_DOC_ERROR = YES -# The WARN_NO_PARAMDOC option can be enabled 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. +# This WARN_NO_PARAMDOC option can be enabled to get warnings for functions that +# are documented, but have no documentation for their parameters or return +# value. If set to NO, doxygen will only warn about wrong or incomplete +# parameter documentation, but not about the absence of documentation. +# The default value is: NO. 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) +# If the WARN_AS_ERROR tag is set to YES then doxygen will immediately stop when +# a warning is encountered. +# The default value is: NO. + +WARN_AS_ERROR = 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) +# The default value is: $file:$line: $text. 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. +# 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 standard +# error (stderr). WARN_LOGFILE = #--------------------------------------------------------------------------- -# configuration options related to the input files +# 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. +# The INPUT tag is 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. See also FILE_PATTERNS and EXTENSION_MAPPING +# Note: If this tag is empty the current directory is searched. INPUT = ../../src/lib # 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. +# that doxygen parses. Internally doxygen uses the UTF-8 encoding. Doxygen uses +# libiconv (or the iconv built into libc) for the transcoding. See the libiconv +# documentation (see: http://www.gnu.org/software/libiconv) for the list of +# possible encodings. +# The default value is: UTF-8. 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++ *.d *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh -# *.hxx *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.dox *.py -# *.f90 *.f *.for *.vhd *.vhdl +# FILE_PATTERNS tag to specify one or more wildcard patterns (like *.cpp and +# *.h) to filter out the source-files in the directories. +# +# Note that for custom extensions or not directly supported extensions you also +# need to set EXTENSION_MAPPING for the extension otherwise the files are not +# read by doxygen. +# +# If left blank the following patterns are tested:*.c, *.cc, *.cxx, *.cpp, +# *.c++, *.java, *.ii, *.ixx, *.ipp, *.i++, *.inl, *.idl, *.ddl, *.odl, *.h, +# *.hh, *.hxx, *.hpp, *.h++, *.cs, *.d, *.php, *.php4, *.php5, *.phtml, *.inc, +# *.m, *.markdown, *.md, *.mm, *.dox, *.py, *.pyw, *.f90, *.f95, *.f03, *.f08, +# *.f, *.for, *.tcl, *.vhd, *.vhdl, *.ucf and *.qsf. 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. +# The RECURSIVE tag can be used to specify whether or not subdirectories should +# be searched for input files as well. +# The default value is: NO. RECURSIVE = yes -# The EXCLUDE tag can be used to specify files and/or directories that should +# The EXCLUDE tag can be used to specify files and/or directories that should be # 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. +# +# Note that relative paths are relative to the directory from which doxygen is +# run. EXCLUDE = -# The EXCLUDE_SYMLINKS tag can be used select whether or not files or +# The EXCLUDE_SYMLINKS tag can be used to select whether or not files or # directories that are symbolic links (a Unix file system feature) are excluded # from the input. +# The default value is: NO. 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/* +# 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 = @@ -650,716 +844,1130 @@ # 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 +# +# Note that the wildcards are matched against the file with absolute path, so to +# exclude all test directories use the pattern */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). +# 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 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. +# searched for input files to be used with the \include or \dontinclude commands +# irrespective of the value of the RECURSIVE tag. +# The default value is: NO. EXAMPLE_RECURSIVE = YES -# 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). +# The IMAGE_PATH tag can be used to specify one or more files or directories +# that contain images that are to be 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. +# 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. +# +# Note that the filter must not add or remove lines; it is applied before the +# code is scanned, but not when the output code is generated. If lines are added +# or removed, the anchors will not be placed correctly. +# +# Note that for custom extensions or not directly supported extensions you also +# need to set EXTENSION_MAPPING for the extension otherwise the files are not +# properly processed by doxygen. 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 or if -# non of the patterns match the file name, INPUT_FILTER is applied. +# 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 information on how +# filters are used. If the FILTER_PATTERNS tag is empty or if none of the +# patterns match the file name, INPUT_FILTER is applied. +# +# Note that for custom extensions or not directly supported extensions you also +# need to set EXTENSION_MAPPING for the extension otherwise the files are not +# properly processed by doxygen. 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). +# INPUT_FILTER) will also be used to filter the input files that are used for +# producing the source files to browse (i.e. when SOURCE_BROWSER is set to YES). +# The default value is: NO. FILTER_SOURCE_FILES = NO # The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file -# pattern. A pattern will override the setting for FILTER_PATTERN (if any) -# and it is also possible to disable source filtering for a specific pattern -# using *.ext= (so without naming a filter). This option only has effect when -# FILTER_SOURCE_FILES is enabled. +# pattern. A pattern will override the setting for FILTER_PATTERN (if any) and +# it is also possible to disable source filtering for a specific pattern using +# *.ext= (so without naming a filter). +# This tag requires that the tag FILTER_SOURCE_FILES is set to YES. FILTER_SOURCE_PATTERNS = +# If the USE_MDFILE_AS_MAINPAGE tag refers to the name of a markdown file that +# is part of the input, its contents will be placed on the main page +# (index.html). This can be useful if you have a project on for instance GitHub +# and want to reuse the introduction page also for the doxygen output. + +USE_MDFILE_AS_MAINPAGE = + #--------------------------------------------------------------------------- -# configuration options related to source browsing +# 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. +# 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 that +# also VERBATIM_HEADERS is set to NO. +# The default value is: NO. SOURCE_BROWSER = NO -# Setting the INLINE_SOURCES tag to YES will include the body -# of functions and classes directly in the documentation. +# Setting the INLINE_SOURCES tag to YES will include the body of functions, +# classes and enums directly into the documentation. +# The default value is: NO. 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. +# Setting the STRIP_CODE_COMMENTS tag to YES will instruct doxygen to hide any +# special comment blocks from generated source code fragments. Normal C, C++ and +# Fortran comments will always remain visible. +# The default value is: YES. 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. +# If the REFERENCED_BY_RELATION tag is set to YES then for each documented +# function all documented functions referencing it will be listed. +# The default value is: NO. REFERENCED_BY_RELATION = YES -# 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. +# 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. +# The default value is: NO. 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. +# If the REFERENCES_LINK_SOURCE tag is set to YES 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. +# The default value is: YES. 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. +# If SOURCE_TOOLTIPS is enabled (the default) then hovering a hyperlink in the +# source code will show a tooltip with additional information such as prototype, +# brief description and links to the definition and documentation. Since this +# will make the HTML file larger and loading of large files a bit slower, you +# can opt to disable this feature. +# The default value is: YES. +# This tag requires that the tag SOURCE_BROWSER is set to YES. + +SOURCE_TOOLTIPS = 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. +# +# To use it do the following: +# - Install the latest version of global +# - Enable SOURCE_BROWSER and USE_HTAGS in the config file +# - Make sure the INPUT points to the root of the source tree +# - Run doxygen as normal +# +# Doxygen will invoke htags (and that will in turn invoke gtags), so these +# tools must be available from the command line (i.e. in the search path). +# +# The result: instead of the source browser generated by doxygen, the links to +# source code will now point to the output of htags. +# The default value is: NO. +# This tag requires that the tag SOURCE_BROWSER is set to YES. 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. +# If the VERBATIM_HEADERS tag is set the YES 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. +# See also: Section \class. +# The default value is: YES. VERBATIM_HEADERS = YES #--------------------------------------------------------------------------- -# configuration options related to the alphabetical class index +# 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. +# 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. +# The default value is: YES. 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]) +# The COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns in +# which the alphabetical index list will be split. +# Minimum value: 1, maximum value: 20, default value: 5. +# This tag requires that the tag ALPHABETICAL_INDEX is set to YES. COLS_IN_ALPHA_INDEX = 3 -# 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. +# 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 a prefix (or a list of prefixes) that should be ignored +# while generating the index headers. +# This tag requires that the tag ALPHABETICAL_INDEX is set to YES. IGNORE_PREFIX = #--------------------------------------------------------------------------- -# configuration options related to the HTML output +# Configuration options related to the HTML output #--------------------------------------------------------------------------- -# If the GENERATE_HTML tag is set to YES (the default) Doxygen will -# generate HTML output. +# If the GENERATE_HTML tag is set to YES, doxygen will generate HTML output +# The default value is: YES. 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. +# 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. +# The default directory is: html. +# This tag requires that the tag GENERATE_HTML is set to YES. 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. +# The HTML_FILE_EXTENSION tag can be used to specify the file extension for each +# generated HTML page (for example: .htm, .php, .asp). +# The default value is: .html. +# This tag requires that the tag GENERATE_HTML is set to YES. 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 +# The HTML_HEADER tag can be used to specify a user-defined HTML header file for +# each generated HTML page. If the tag is left blank doxygen will generate a # standard header. +# +# To get valid HTML the header file that includes any scripts and style sheets +# that doxygen needs, which is dependent on the configuration options used (e.g. +# the setting GENERATE_TREEVIEW). It is highly recommended to start with a +# default header using +# doxygen -w html new_header.html new_footer.html new_stylesheet.css +# YourConfigFile +# and then modify the file new_header.html. See also section "Doxygen usage" +# for information on how to generate the default header that doxygen normally +# uses. +# Note: The header is subject to change so you typically have to regenerate the +# default header when upgrading to a newer version of doxygen. For a description +# of the possible markers and block names see the documentation. +# This tag requires that the tag GENERATE_HTML is set to YES. HTML_HEADER = header.html.in -# 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. +# The HTML_FOOTER tag can be used to specify a user-defined HTML footer for each +# generated HTML page. If the tag is left blank doxygen will generate a standard +# footer. See HTML_HEADER for more information on how to generate a default +# footer and what special commands can be used inside the footer. See also +# section "Doxygen usage" for information on how to generate the default footer +# that doxygen normally uses. +# This tag requires that the tag GENERATE_HTML is set to YES. HTML_FOOTER = footer.html.in -# 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! +# 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 left blank doxygen will generate a default style sheet. +# See also section "Doxygen usage" for information on how to generate the style +# sheet that doxygen normally uses. +# Note: It is recommended to use HTML_EXTRA_STYLESHEET instead of this tag, as +# it is more robust and this tag (HTML_STYLESHEET) will in the future become +# obsolete. +# This tag requires that the tag GENERATE_HTML is set to YES. HTML_STYLESHEET = -# The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. -# Doxygen will adjust the colors in the stylesheet and background images -# according to this color. Hue is specified as an angle on a colorwheel, -# see http://en.wikipedia.org/wiki/Hue for more information. -# For instance the value 0 represents red, 60 is yellow, 120 is green, -# 180 is cyan, 240 is blue, 300 purple, and 360 is red again. -# The allowed range is 0 to 359. +# The HTML_EXTRA_STYLESHEET tag can be used to specify additional user-defined +# cascading style sheets that are included after the standard style sheets +# created by doxygen. Using this option one can overrule certain style aspects. +# This is preferred over using HTML_STYLESHEET since it does not replace the +# standard style sheet and is therefore more robust against future updates. +# Doxygen will copy the style sheet files to the output directory. +# Note: The order of the extra style sheet files is of importance (e.g. the last +# style sheet in the list overrules the setting of the previous ones in the +# list). For an example see the documentation. +# This tag requires that the tag GENERATE_HTML is set to YES. + +HTML_EXTRA_STYLESHEET = + +# The HTML_EXTRA_FILES tag can be used to specify one or more extra images or +# other source files which should be copied to the HTML output directory. Note +# that these files will be copied to the base HTML output directory. Use the +# $relpath^ marker in the HTML_HEADER and/or HTML_FOOTER files to load these +# files. In the HTML_STYLESHEET file, use the file name only. Also note that the +# files will be copied as-is; there are no commands or markers available. +# This tag requires that the tag GENERATE_HTML is set to YES. + +HTML_EXTRA_FILES = + +# The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. Doxygen +# will adjust the colors in the style sheet and background images according to +# this color. Hue is specified as an angle on a colorwheel, see +# http://en.wikipedia.org/wiki/Hue for more information. For instance the value +# 0 represents red, 60 is yellow, 120 is green, 180 is cyan, 240 is blue, 300 +# purple, and 360 is red again. +# Minimum value: 0, maximum value: 359, default value: 220. +# This tag requires that the tag GENERATE_HTML is set to YES. HTML_COLORSTYLE_HUE = 220 -# The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of -# the colors in the HTML output. For a value of 0 the output will use -# grayscales only. A value of 255 will produce the most vivid colors. +# The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of the colors +# in the HTML output. For a value of 0 the output will use grayscales only. A +# value of 255 will produce the most vivid colors. +# Minimum value: 0, maximum value: 255, default value: 100. +# This tag requires that the tag GENERATE_HTML is set to YES. HTML_COLORSTYLE_SAT = 100 -# The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to -# the luminance component of the colors in the HTML output. Values below -# 100 gradually make the output lighter, whereas values above 100 make -# the output darker. The value divided by 100 is the actual gamma applied, -# so 80 represents a gamma of 0.8, The value 220 represents a gamma of 2.2, -# and 100 does not change the gamma. +# The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to the +# luminance component of the colors in the HTML output. Values below 100 +# gradually make the output lighter, whereas values above 100 make the output +# darker. The value divided by 100 is the actual gamma applied, so 80 represents +# a gamma of 0.8, The value 220 represents a gamma of 2.2, and 100 does not +# change the gamma. +# Minimum value: 40, maximum value: 240, default value: 80. +# This tag requires that the tag GENERATE_HTML is set to YES. HTML_COLORSTYLE_GAMMA = 80 # If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML -# page will contain the date and time when the page was generated. Setting -# this to NO can help when comparing the output of multiple runs. +# page will contain the date and time when the page was generated. Setting this +# to YES can help to show when doxygen was last run and thus if the +# documentation is up to date. +# The default value is: NO. +# This tag requires that the tag GENERATE_HTML is set to YES. HTML_TIMESTAMP = NO -# 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). +# page has loaded. +# The default value is: NO. +# This tag requires that the tag GENERATE_HTML is set to YES. 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 +# With HTML_INDEX_NUM_ENTRIES one can control the preferred number of entries +# shown in the various tree structured indices initially; the user can expand +# and collapse entries dynamically later on. Doxygen will expand the tree to +# such a level that at most the specified number of entries are visible (unless +# a fully collapsed tree already exceeds this amount). So setting the number of +# entries 1 will produce a full collapsed tree by default. 0 is a special value +# representing an infinite number of entries and will result in a full expanded +# tree by default. +# Minimum value: 0, maximum value: 9999, default value: 100. +# This tag requires that the tag GENERATE_HTML is set to YES. + +HTML_INDEX_NUM_ENTRIES = 100 + +# 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 (see: http://developer.apple.com/tools/xcode/), 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. +# The default value is: NO. +# This tag requires that the tag GENERATE_HTML is set to YES. 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. +# This tag determines the name of the docset 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. +# The default value is: Doxygen generated docs. +# This tag requires that the tag GENERATE_DOCSET is set to YES. 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. +# 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. +# The default value is: org.doxygen.Project. +# This tag requires that the tag GENERATE_DOCSET is set to YES. DOCSET_BUNDLE_ID = org.doxygen.Project -# When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify +# The DOCSET_PUBLISHER_ID tag specifies a string that should uniquely identify # the documentation publisher. This should be a reverse domain-name style # string, e.g. com.mycompany.MyDocSet.documentation. +# The default value is: org.doxygen.Publisher. +# This tag requires that the tag GENERATE_DOCSET is set to YES. DOCSET_PUBLISHER_ID = org.doxygen.Publisher -# The GENERATE_PUBLISHER_NAME tag identifies the documentation publisher. +# The DOCSET_PUBLISHER_NAME tag identifies the documentation publisher. +# The default value is: Publisher. +# This tag requires that the tag GENERATE_DOCSET is set to YES. DOCSET_PUBLISHER_NAME = Publisher -# 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. +# If the GENERATE_HTMLHELP tag is set to YES then doxygen generates three +# additional HTML index files: index.hhp, index.hhc, and index.hhk. The +# index.hhp is a project file that can be read by Microsoft's HTML Help Workshop +# (see: http://www.microsoft.com/en-us/download/details.aspx?id=21138) on +# Windows. +# +# The HTML Help Workshop contains a compiler that can convert all HTML output +# generated by doxygen into a single compiled HTML file (.chm). Compiled HTML +# files are now used as the Windows 98 help format, and will replace the old +# Windows help format (.hlp) on all Windows platforms in the future. Compressed +# HTML files also contain an index, a table of contents, and you can search for +# words in the documentation. The HTML workshop also contains a viewer for +# compressed HTML files. +# The default value is: NO. +# This tag requires that the tag GENERATE_HTML is set to YES. 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 +# 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. +# This tag requires that the tag GENERATE_HTMLHELP is set to YES. 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. +# 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. +# The file has to be specified with full path. +# This tag requires that the tag GENERATE_HTMLHELP is set to YES. 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). +# 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). +# The default value is: NO. +# This tag requires that the tag GENERATE_HTMLHELP is set to YES. 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. +# The CHM_INDEX_ENCODING is used to encode HtmlHelp index (hhk), content (hhc) +# and project file content. +# This tag requires that the tag GENERATE_HTMLHELP is set to YES. 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. +# 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. Furthermore it +# enables the Previous and Next buttons. +# The default value is: NO. +# This tag requires that the tag GENERATE_HTMLHELP is set to YES. 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. +# The TOC_EXPAND flag can be set to YES to add extra items for group members to +# the table of contents of the HTML help documentation and to the tree view. +# The default value is: NO. +# This tag requires that the tag GENERATE_HTMLHELP is set to YES. 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. +# 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. +# The default value is: NO. +# This tag requires that the tag GENERATE_HTML is set to YES. 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. +# 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. +# This tag requires that the tag GENERATE_QHP is set to YES. 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 +# The QHP_NAMESPACE tag specifies the namespace to use when generating Qt Help +# Project output. For more information please see Qt Help Project / Namespace +# (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#namespace). +# The default value is: org.doxygen.Project. +# This tag requires that the tag GENERATE_QHP is set to YES. QHP_NAMESPACE = org.doxygen.Project -# 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 +# The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating Qt +# Help Project output. For more information please see Qt Help Project / Virtual +# Folders (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#virtual- +# folders). +# The default value is: doc. +# This tag requires that the tag GENERATE_QHP is set to YES. 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 +# If the QHP_CUST_FILTER_NAME tag is set, it specifies the name of a custom +# filter to add. For more information please see Qt Help Project / Custom +# Filters (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#custom- +# filters). +# This tag requires that the tag GENERATE_QHP is set to YES. 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. +# The QHP_CUST_FILTER_ATTRS tag specifies the list of the attributes of the +# custom filter to add. For more information please see Qt Help Project / Custom +# Filters (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#custom- +# filters). +# This tag requires that the tag GENERATE_QHP is set to YES. 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. +# project's filter section matches. Qt Help Project / Filter Attributes (see: +# http://qt-project.org/doc/qt-4.8/qthelpproject.html#filter-attributes). +# This tag requires that the tag GENERATE_QHP is set to YES. 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. +# 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. +# This tag requires that the tag GENERATE_QHP is set to YES. QHG_LOCATION = -# If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files -# will be generated, which together with the HTML files, form an Eclipse help -# plugin. To install this plugin and make it available under the help contents -# menu in Eclipse, the contents of the directory containing the HTML and XML -# files needs to be copied into the plugins directory of eclipse. The name of -# the directory within the plugins directory should be the same as -# the ECLIPSE_DOC_ID value. After copying Eclipse needs to be restarted before -# the help appears. +# If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files will be +# generated, together with the HTML files, they form an Eclipse help plugin. To +# install this plugin and make it available under the help contents menu in +# Eclipse, the contents of the directory containing the HTML and XML files needs +# to be copied into the plugins directory of eclipse. The name of the directory +# within the plugins directory should be the same as the ECLIPSE_DOC_ID value. +# After copying Eclipse needs to be restarted before the help appears. +# The default value is: NO. +# This tag requires that the tag GENERATE_HTML is set to YES. GENERATE_ECLIPSEHELP = NO -# A unique identifier for the eclipse help plugin. When installing the plugin -# the directory name containing the HTML and XML files should also have -# this name. +# A unique identifier for the Eclipse help plugin. When installing the plugin +# the directory name containing the HTML and XML files should also have this +# name. Each documentation set should have its own identifier. +# The default value is: org.doxygen.Project. +# This tag requires that the tag GENERATE_ECLIPSEHELP is set to YES. ECLIPSE_DOC_ID = org.doxygen.Project -# 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. +# If you want full control over the layout of the generated HTML pages it might +# be necessary to disable the index and replace it with your own. The +# DISABLE_INDEX tag can be used to turn on/off the condensed index (tabs) at top +# of each HTML page. A value of NO enables the index and the value YES disables +# it. Since the tabs in the index contain the same information as the navigation +# tree, you can set this option to YES if you also set GENERATE_TREEVIEW to YES. +# The default value is: NO. +# This tag requires that the tag GENERATE_HTML is set to YES. DISABLE_INDEX = NO -# This tag can be used to set the number of enum values (range [0,1..20]) -# that doxygen will group on one line in the generated HTML documentation. -# Note that a value of 0 will completely suppress the enum values from appearing in the overview section. - -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 YES, 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 (i.e. any modern browser). -# Windows users are probably better off using the HTML help feature. +# structure should be generated to display hierarchical information. If the tag +# value is set to YES, 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 +# (i.e. any modern browser). Windows users are probably better off using the +# HTML help feature. Via custom style sheets (see HTML_EXTRA_STYLESHEET) one can +# further fine-tune the look of the index. As an example, the default style +# sheet generated by doxygen has an example that shows how to put an image at +# the root of the tree instead of the PROJECT_NAME. Since the tree basically has +# the same information as the tab index, you could consider setting +# DISABLE_INDEX to YES when enabling this option. +# The default value is: NO. +# This tag requires that the tag GENERATE_HTML is set to YES. GENERATE_TREEVIEW = YES -# By enabling USE_INLINE_TREES, doxygen will generate the Groups, Directories, -# and Class Hierarchy pages using a tree view instead of an ordered list. +# The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values that +# doxygen will group on one line in the generated HTML documentation. +# +# Note that a value of 0 will completely suppress the enum values from appearing +# in the overview section. +# Minimum value: 0, maximum value: 20, default value: 4. +# This tag requires that the tag GENERATE_HTML is set to YES. -USE_INLINE_TREES = NO +ENUM_VALUES_PER_LINE = 4 -# 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. +# 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. +# Minimum value: 0, maximum value: 1500, default value: 250. +# This tag requires that the tag GENERATE_HTML is set to YES. TREEVIEW_WIDTH = 250 -# When the EXT_LINKS_IN_WINDOW option is set to YES doxygen will open -# links to external symbols imported via tag files in a separate window. +# If the EXT_LINKS_IN_WINDOW option is set to YES, doxygen will open links to +# external symbols imported via tag files in a separate window. +# The default value is: NO. +# This tag requires that the tag GENERATE_HTML is set to YES. EXT_LINKS_IN_WINDOW = NO -# 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. +# Use this tag to change the font size of LaTeX formulas included as images in +# the HTML documentation. 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. +# Minimum value: 8, maximum value: 50, default value: 10. +# This tag requires that the tag GENERATE_HTML is set to YES. FORMULA_FONTSIZE = 10 # Use the FORMULA_TRANPARENT tag to determine whether or not the images -# generated for formulas are transparent PNGs. Transparent PNGs are -# not supported properly for IE 6.0, but are supported on all modern browsers. -# Note that when changing this option you need to delete any form_*.png files -# in the HTML output before the changes have effect. +# generated for formulas are transparent PNGs. Transparent PNGs are not +# supported properly for IE 6.0, but are supported on all modern browsers. +# +# Note that when changing this option you need to delete any form_*.png files in +# the HTML output directory before the changes have effect. +# The default value is: YES. +# This tag requires that the tag GENERATE_HTML is set to YES. FORMULA_TRANSPARENT = YES -# Enable the USE_MATHJAX option to render LaTeX formulas using MathJax -# (see http://www.mathjax.org) which uses client side Javascript for the -# rendering instead of using prerendered bitmaps. Use this if you do not -# have LaTeX installed or if you want to formulas look prettier in the HTML -# output. When enabled you also need to install MathJax separately and -# configure the path to it using the MATHJAX_RELPATH option. +# Enable the USE_MATHJAX option to render LaTeX formulas using MathJax (see +# http://www.mathjax.org) which uses client side Javascript for the rendering +# instead of using pre-rendered bitmaps. Use this if you do not have LaTeX +# installed or if you want to formulas look prettier in the HTML output. When +# enabled you may also need to install MathJax separately and configure the path +# to it using the MATHJAX_RELPATH option. +# The default value is: NO. +# This tag requires that the tag GENERATE_HTML is set to YES. USE_MATHJAX = NO -# When MathJax is enabled you need to specify the location relative to the -# HTML output directory using the MATHJAX_RELPATH option. The destination -# directory should contain the MathJax.js script. For instance, if the mathjax -# directory is located at the same level as the HTML output directory, then -# MATHJAX_RELPATH should be ../mathjax. The default value points to the mathjax.org site, so you can quickly see the result without installing -# MathJax, but it is strongly recommended to install a local copy of MathJax -# before deployment. +# When MathJax is enabled you can set the default output format to be used for +# the MathJax output. See the MathJax site (see: +# http://docs.mathjax.org/en/latest/output.html) for more details. +# Possible values are: HTML-CSS (which is slower, but has the best +# compatibility), NativeMML (i.e. MathML) and SVG. +# The default value is: HTML-CSS. +# This tag requires that the tag USE_MATHJAX is set to YES. + +MATHJAX_FORMAT = HTML-CSS + +# When MathJax is enabled you need to specify the location relative to the HTML +# output directory using the MATHJAX_RELPATH option. The destination directory +# should contain the MathJax.js script. For instance, if the mathjax directory +# is located at the same level as the HTML output directory, then +# MATHJAX_RELPATH should be ../mathjax. The default value points to the MathJax +# Content Delivery Network so you can quickly see the result without installing +# MathJax. However, it is strongly recommended to install a local copy of +# MathJax from http://www.mathjax.org before deployment. +# The default value is: http://cdn.mathjax.org/mathjax/latest. +# This tag requires that the tag USE_MATHJAX is set to YES. MATHJAX_RELPATH = http://www.mathjax.org/mathjax -# When the SEARCHENGINE tag is enabled doxygen will generate a search box -# for the HTML output. The underlying search engine uses javascript -# and DHTML and should work on any modern browser. Note that when using -# HTML help (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets -# (GENERATE_DOCSET) there is already a search function so this one should -# typically be disabled. For large projects the javascript based search engine -# can be slow, then enabling SERVER_BASED_SEARCH may provide a better solution. +# The MATHJAX_EXTENSIONS tag can be used to specify one or more MathJax +# extension names that should be enabled during MathJax rendering. For example +# MATHJAX_EXTENSIONS = TeX/AMSmath TeX/AMSsymbols +# This tag requires that the tag USE_MATHJAX is set to YES. + +MATHJAX_EXTENSIONS = + +# The MATHJAX_CODEFILE tag can be used to specify a file with javascript pieces +# of code that will be used on startup of the MathJax code. See the MathJax site +# (see: http://docs.mathjax.org/en/latest/output.html) for more details. For an +# example see the documentation. +# This tag requires that the tag USE_MATHJAX is set to YES. + +MATHJAX_CODEFILE = + +# When the SEARCHENGINE tag is enabled doxygen will generate a search box for +# the HTML output. The underlying search engine uses javascript and DHTML and +# should work on any modern browser. Note that when using HTML help +# (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets (GENERATE_DOCSET) +# there is already a search function so this one should typically be disabled. +# For large projects the javascript based search engine can be slow, then +# enabling SERVER_BASED_SEARCH may provide a better solution. It is possible to +# search using the keyboard; to jump to the search box use + S +# (what the is depends on the OS and browser, but it is typically +# , /