summaryrefslogtreecommitdiff
path: root/bin/gbuild-to-ide
AgeCommit message (Collapse)Author
2024-06-30vs-ide-integration: set correct solution / project platformMike Kaganski
This allows the IDE to show active #ifdef conditions, type sizes, alignment, memory layout, selected overloads, and so on. Change-Id: Idd1211df3b3745658f1996a494929b07cf7aa573 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/169772 Tested-by: Jenkins Reviewed-by: Mike Kaganski <mike.kaganski@collabora.com>
2024-02-25Unescape double quotes escaped by another double quote in definesMike Kaganski
Otherwise, e.g. SRCDIR is defined as ""C:/lo/core"", which is not a proper string literal. Change-Id: Id7b503ea21735892b504dbc861f66c250db01e94 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/163902 Tested-by: Jenkins Reviewed-by: Mike Kaganski <mike.kaganski@collabora.com>
2024-01-31qtcreator: Fix generating .pro files for externalsMichael Weghorn
Since commit 3460799175e6c5795aa07c784e16d10ba9081d49 Date: Thu Jan 25 23:41:52 2024 +0600 Clear gb_GbuildToJson_DENYLISTEDMODULES, allow these modules , externals are taken into account in the generation of IDE integrations, causing errors like this when running `make qtcreator-ide-integration` to generate the *.pro files for the QtCreator IDE integration: cd /home/michi/development/git/libreoffice && bin/gbuild-to-ide --ide qtcreator --make make ERROR : creating pro file=/home/michi/development/git/libreoffice/clucene/clucene.pro [Errno 2] No such file or directory: '/home/michi/development/git/libreoffice/clucene/clucene.pro' Traceback (most recent call last): File "/home/michi/development/git/libreoffice/bin/gbuild-to-ide", line 1787, in emit with open(qt_pro_file, mode) as fpro: ^^^^^^^^^^^^^^^^^^^^^^^ FileNotFoundError: [Errno 2] No such file or directory: '/home/michi/development/git/libreoffice/clucene/clucene.pro' Fix this by creating the .pro files in a directory that has the same relative path to the $(BUILDDIR) as the corresponding .mk files have in the $(SRCDIR) rather than in $(BUILDDIR)/$(LIBNAME)/. While both are the same for LO's internal modules, the latter directory does not exist for externals, since they're located underneath a top-level directory called "external". For the simple case of an in-tree build, this now e.g. creates a file `external/clucene/clucene.pro` instead of failing to create a `clucene/clucene.pro` because there's no top-level "clucene" directory. An alternative approach might to just ignore the externals, as this commit implemented it for the codelite integration: commit 41c8e0957369b7b53a3b9cf4b4cf1e49a982a414 Date: Sat Jan 27 21:54:10 2024 +0200 fix codelite-ide-integration externals seems to be part of the list of modules now, but I don't know how to deal with that, so just ignore them. (In that case, they wouldn't be part of the project, speeding up update of the clang code model after changes, but then not providing features like code navigation and autocompletion etc.) Change-Id: Idb04af5f7445955e5dbf9ec3fd8626bbcb09ab11 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/162837 Tested-by: Jenkins Reviewed-by: Michael Weghorn <m.weghorn@posteo.de>
2024-01-28fix codelite-ide-integrationNoel Grandin
externals seems to be part of the list of modules now, but I don't know how to deal with that, so just ignore them. Change-Id: Ic42d0b27562247b12cf9393659298cda56d1572c Reviewed-on: https://gerrit.libreoffice.org/c/core/+/162648 Tested-by: Jenkins Reviewed-by: Noel Grandin <noel.grandin@collabora.co.uk>
2024-01-26Clear gb_GbuildToJson_DENYLISTEDMODULES, allow these modulesMike Kaganski
Filter "empty" targets in Visual Studio solutions: it makes little sense to add generated files to projects (they aren't intended for editing in IDE); so most external libraries, which only have "generated" sources, and aren't part of core anyway, would have zero source files in their projects - thus excluded. Handle C++/CLI files; use their specific CXXCLRFLAGS (set them to the source files explicitly, overriding CXXFLAGS set on the project level). While here, do the same with CFLAGS and C files. Do not add H(XX) files (with names identical to C(XX) files) to the VS projects. This adds a tiny subset of all headers, which is inconsistent. Change-Id: I6bd932277287d3444bb547b93f2867d226072d60 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/162582 Tested-by: Jenkins Reviewed-by: Mike Kaganski <mike.kaganski@collabora.com>
2024-01-25Deduplicate, refactor and simplify GbuildLinkTarget initializationMike Kaganski
Change-Id: I0c2d9823454ff84af2967c20a383b334e4933967 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/162550 Tested-by: Jenkins Reviewed-by: Mike Kaganski <mike.kaganski@collabora.com>
2024-01-25add static libraries to gbuildtojsonMike Kaganski
... and to vs-ide-integration solution. Change-Id: I5085e6a61df4bc03cfe595a1e6b99196f6f73643 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/162524 Tested-by: Jenkins Reviewed-by: Mike Kaganski <mike.kaganski@collabora.com>
2024-01-19Rename natstepfilter file, to make it not hidden on LinuxMike Kaganski
It turns out, that this also works, despite all the documentation refers to it as '.natstepfilter'. Change-Id: I17ab0662a3de0e0f7db72e31f5e7ed0f00823447 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/162311 Reviewed-by: Christian Lohmaier <lohmaier+LibreOffice@googlemail.com> Tested-by: Jenkins
2024-01-19Add a natstepfilter file to Visual Studio solutionMike Kaganski
Allows to avoid stepping into some functions, like smart pointer's operator->(), when debugging. Change-Id: Ia930ad6b0c94c9caefad8ac026252fced1265fb4 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/162304 Tested-by: Jenkins Reviewed-by: Mike Kaganski <mike.kaganski@collabora.com>
2023-11-02VS IDE integration: enable Python pretty printers when debugging a WSL buildMike Kaganski
See https://learn.microsoft.com/en-us/cpp/linux/deploy-run-and-debug-your-linux-project#debug-with-attach-to-process Change-Id: I16d50ebe5f087518de1953ea1f9aad4180714cc7 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/158789 Tested-by: Jenkins Reviewed-by: Mike Kaganski <mike.kaganski@collabora.com>
2023-11-01VS IDE integration: Use LocalDebuggerCommand for startup executableMike Kaganski
Before that, NMakeOutput was abused for that. Now it will point to the correct link target. Change-Id: I9c3fd57948cc24a99f54a1c23ca5e0351d25a0dc Reviewed-on: https://gerrit.libreoffice.org/c/core/+/158748 Tested-by: Jenkins Reviewed-by: Mike Kaganski <mike.kaganski@collabora.com>
2023-10-31qtcreator: Add Obj-C++ files to projectMichael Weghorn
Extend gbuild-to-ide to also take into account Objective-C++ files that are set with the `OBJCXXOBJECTS` key in the json files. Extend the Qt Creator IDE integration target (`make qtcreator-ide-integration`) to make use of that information to find the corresponding headers as well, and set sources and headers in the `OBJECTIVE_SOURCES` [1] and `OBJECTIVE_HEADERS` [2] qmake veriables. This way, those files are part of the project and the Clang Code Model works as expected, which makes features like code completion and showing issues work correctly for such files (like e.g. vcl/osx/a11ywrapper.mm) as well. [1] https://doc.qt.io/qt-6/qmake-variable-reference.html#objective-sources [2] https://doc.qt.io/qt-6/qmake-variable-reference.html#objective-headers Change-Id: I2c1cf5bdfdc64300ec3eb77e42de1ae2cd4223f4 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/158665 Tested-by: Jenkins Reviewed-by: Michael Weghorn <m.weghorn@posteo.de>
2023-10-31bin/gbuild-to-ide: Drop trailing whitespaceMichael Weghorn
Change-Id: I3142080721db11f75631accd3a5e403027a63110 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/158664 Tested-by: Jenkins Reviewed-by: Michael Weghorn <m.weghorn@posteo.de>
2023-10-31qtcreator: Set correct soffice path on macOSMichael Weghorn
The soffice path is different on macOS than it is on Linux or Windows. Let gbuild-to-ide take that into account when generating the QtCreator IDE integration (`make qtcreator-ide-integration`), so the autogenerated run/debug target works. Change-Id: Ibdd4cf32bddadfe67608b06b7b3ce58c2a9dd518 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/158653 Tested-by: Jenkins Reviewed-by: Michael Weghorn <m.weghorn@posteo.de>
2023-10-16qtcreator: Specify C++ std version using CONFIG qmake varMichael Weghorn
Extract the C++ standard version to use that is specified by a `-std=<version>` or `-std:<version>` compiler flag, and set that via "CONFIG += <version>" in the .pro files used by Qt Creator. This makes the Clang Code Model use the correct mode and no longer complain about `char8_t` after the switch to C++20 in my Windows development setup in Qt Creator: > accessibletabbarpagelist.hxx:22:10: In included file: use of undeclared identifier 'char8_t' > stringutils.hxx:252:31: error occurred here The previous way of specifying this via `QMAKE_CXXFLAGS` as introduced in commit 92c03d9bf644b0f10de52ce0da09f97056e46247 Author: Michael Weghorn <m.weghorn@posteo.de> Date: Fri Jun 7 21:44:03 2019 +0200 qtcreator: Take over '-std=...' from CXXFLAGS appears to not (no longer?) work at least with Qt Creator 11.0.3 on Windows. On the contrary however, setting only `CONFIG` and not `QMAKE_CXXFLAGS` causes the exact same problem in my Linux setup. Therefore, set both qmake variables. Note that there is a specific set of accepted values for the the `CONFIG` variable in .pro files [1], but at least "c++20" and "c++latest" are accepted and have the expected meaning, so that should be fine for now. [1] https://doc.qt.io/qt-6/qmake-variable-reference.html#config Change-Id: Idc75b74300c7bdd0f6193fcfc1758b536728b887 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/158053 Tested-by: Jenkins Reviewed-by: Michael Weghorn <m.weghorn@posteo.de>
2022-12-05create compile_commands.json in builddirChristian Lohmaier
assuming that nothing breaks for existing users of the compile_commands.json file, since they assume BUILDDIR=SRCDIR, so nothing will change in those cases. For building in a different directory than the source, the compile_commands.json file is the only thing that regularly clobbers my otherwise pristine SRCROOT Change-Id: I344afa0bc7bb3eaa1eb888cd3558d3602090af5f Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143571 Tested-by: Jenkins Reviewed-by: Christian Lohmaier <lohmaier+LibreOffice@googlemail.com>
2021-12-06Retire build-nocheckThorsten Behrens
Build target was kept for backward compat in 'rework the default make target', so lets retire it after 1.5 years. Use 'make build' instead (which is since the default target anyway). Change-Id: I93d5237dce2abf2536a4d847d79d33d5b6d6cec9 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/126362 Tested-by: Jenkins Reviewed-by: Thorsten Behrens <thorsten.behrens@allotropia.de>
2021-11-02vs-ide-integration: make projects' GUIDs stableMike Kaganski
Use uuid.uuid5 with a custom URL to generate stable GUIDs. This avoids glitches in IDE when re-opening the solution after its re-generation makes some previously opened files to show duplicate entries in IDE's tabbed UI. Also drop the UniqueIdentifier elements from .vcxproj.filters files, which are optional and only used in VS automation [1], so are useless with randomly-generated GUIDs. [1] https://docs.microsoft.com/en-us/cpp/build/reference/vcxproj-filters-files Change-Id: I91dae730286b3187a6ceffcb9ae3afc2b479f4d9 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/124594 Tested-by: Jenkins Reviewed-by: Mike Kaganski <mike.kaganski@collabora.com>
2021-11-02vs-ide-integration: create folders for Executables/Libraries/TestsMike Kaganski
This makes the solution more manageable - one can collapse unneeded categories. And put LibreOffice.natvis to Utility folder, to move it to bottom. Change-Id: I869faaf5756c65e6812b58627acd03bf816dea2c Reviewed-on: https://gerrit.libreoffice.org/c/core/+/124588 Tested-by: Jenkins Reviewed-by: Mike Kaganski <mike.kaganski@collabora.com>
2021-10-08Centralize VS-to-toolset mapping in configureMike Kaganski
This allows to define the mapping once, and avoid modification in multiple places each time a new VS version support is added Change-Id: I93de4c9d78c3f67a0a2e157007e9d13b6f557937 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/123163 Tested-by: Jenkins Reviewed-by: Mike Kaganski <mike.kaganski@collabora.com>
2021-10-08Simplify VS IDE integration generationMike Kaganski
Do not require the IDE version in vs*-ide-integration. Instead, use VCVER environment variable, that is set in configure, to obtain the toolset for the VCPROJ files. When introducing support for new VS version, the 'VisualStudioIntegrationGenerator.retrieve_toolset' method needs to be updated synchronously to list the toolset. This simplifies the make command to make vs-ide-integration TODO: also set the toolset in configure, to simplify the code here, and also in places like external/python3/ExternalProject_python3.mk (see commit c156a8c708f74dd31e1ef024edc578c3915619cb). Change-Id: I95960029a933be2cab96898eee6be6ca6bc5794a Reviewed-on: https://gerrit.libreoffice.org/c/core/+/123162 Tested-by: Jenkins Reviewed-by: Mike Kaganski <mike.kaganski@collabora.com>
2021-10-08Drop vs2017-ide-integration; add vs2022-ide-integrationMike Kaganski
VS2017 is not supported since 24973523ba59087185d434396fd614e73d72107f. Change-Id: I1a2af1eb8c9216eaed87d5454def2176728f719b Reviewed-on: https://gerrit.libreoffice.org/c/core/+/123161 Tested-by: Mike Kaganski <mike.kaganski@collabora.com> Reviewed-by: Mike Kaganski <mike.kaganski@collabora.com>
2021-02-26qtcreator: Create *.pro and *.pro.shared files in builddir, not srcdirMichael Weghorn
With the previous modifications to Qt Creator IDE integration, this makes 'make qtcreator-ide-integration' work when run from a separate build dir, and allows to use multiple build dirs for the same source dir in parallel, each with its own set of Qt Creator files referring to the specific build in their build and run settings. Change-Id: I5d85d0d280be5e5edca15760bcccfc793e1e4b2f Reviewed-on: https://gerrit.libreoffice.org/c/core/+/111553 Tested-by: Jenkins Reviewed-by: Michael Weghorn <m.weghorn@posteo.de>
2021-02-26qtcreator: Use absolute paths in *.pro filesMichael Weghorn
... as a preparation to make this work for the srcdir != builddir case as well. Change-Id: I87507b9866f97cdbdf848c6b187b3b8f17262b6d Reviewed-on: https://gerrit.libreoffice.org/c/core/+/111552 Tested-by: Jenkins Reviewed-by: Michael Weghorn <m.weghorn@posteo.de>
2021-02-26qtcreator: Simplify adding of file extensionMichael Weghorn
Create a new method 'get_file_path' which basically does what 'get_header_extension' and 'get_source_extension' did, but already concatenates the extension to the input; call that one and rename other methods accordingly. While at it, let 'get_source_extension' search for files in srcdir instead of builddir, as another step in making generation of qtcreator-ide-integration work properly for the case where srcdir != builddir. Change-Id: I1e34bfdb726192b4af21e9003205fa551545ae31 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/111551 Tested-by: Jenkins Reviewed-by: Michael Weghorn <m.weghorn@posteo.de>
2021-02-26qtcreator: Don't explicitly delete old *.pro{,.shared} filesMichael Weghorn
They are overwritten when written with the new content anyway, since opened with file mode 'w+', i.e. they're truncated first. This also simplifies handling the case where srcdir != builddir, for which support will be added in a subsequent step. Change-Id: I1dd3386cdf0b97a6299357d6c12ed2d7b6365eae Reviewed-on: https://gerrit.libreoffice.org/c/core/+/111550 Tested-by: Jenkins Reviewed-by: Michael Weghorn <m.weghorn@posteo.de>
2021-02-26qtcreator: Translate comment: "et" -> "and"Michael Weghorn
Change-Id: I2fe51ab0cdfca5c94bd520ed7f9096bc7c8f6fec Reviewed-on: https://gerrit.libreoffice.org/c/core/+/111549 Tested-by: Jenkins Reviewed-by: Michael Weghorn <m.weghorn@posteo.de>
2021-02-26qtcreator: Move assignment to 'mode' out of try blockMichael Weghorn
The variable is used outside of the try block further down. While that works with how Python handles variable scopes (and there is no exception before the assignment happens), moving the variable outside makes the context/scope clearer. Change-Id: Iecfd0477ffb4515cf58736ee138fc8ca7273967f Reviewed-on: https://gerrit.libreoffice.org/c/core/+/111548 Tested-by: Jenkins Reviewed-by: Michael Weghorn <m.weghorn@posteo.de>
2021-02-24qtcreator: Create *.pro.shared files instead of *.pro.userMichael Weghorn
Generating *.pro.user files is not ideal; they're supposed to hold user-specific settings for a project, and thus also to persist manual changes made by the user after initial import of the project. Generate *.pro.shared files instead which are meant to be used to share project settings. [1] This just changes the file name of the generated file for now, but leaves the content the same. The result for the initial loading of the project from a '*.pro' file is basically still the same from a user perspective: A new kit 'Replacement for "Desktop"' is generated on the fly which contains the build and run settings specified in the corresponding '*.pro.shared' file. By using the '*.pro.shared' files, user-specific settings made after initial import will no longer be overwritten by running 'make qtcreator-ide-integration' again, since the '*.pro.user' files are left as they are. The '*.pro.shared' files generated here still contain information specific to the local setup (like file paths). For some more background on LO's Qt Creator IDE integration, s. dev mailing list thread "Added some information about Qt Creator IDE integration to the wiki" [2]. [1] https://doc.qt.io/qtcreator/creator-sharing-project-settings.html [2] https://lists.freedesktop.org/archives/libreoffice/2021-February/thread.html#86800 Change-Id: Ia187bcbffe5297a1cdf6bfeaaabf7867003195e0 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/111474 Tested-by: Jenkins Reviewed-by: Michael Weghorn <m.weghorn@posteo.de>
2021-02-07qtcreator: Show actual names for build configurationsMichael Weghorn
At least with current Qt Creator 4.14, no proper names were shown for the build configurations in the project's "Build" settings, but just integers. Using the config key 'ProjectExplorer.ProjectConfiguration.DisplayName' instead of 'ProjectExplorer.ProjectConfiguration.DefaultDisplayName' in the *.user.pro file makes this work as intended, and "01-Global Build" (and others) shows up as the name for the top-level 'lo.pro' project and "1-Build vcl" for 'vcl.pro', etc. Along with the two previous qtcreator-related commits, this should generally (re)implement an easy way to run unit tests etc. directly from the Qt Creator IDE without having to set that up manually, which cloph mentioned as missing in his FOSDEM talk today ("Using IDEs for LibreOffice development", [1]). To use this, select the corresponding build configuration by clicking on the "screen" icon on the bottom left, then build the project (Ctrl+B or left-click on the "hammer" icon on the bottom left). I didn't check whether the single targets are still up to date. [1] https://fosdem.org/2021/schedule/event/lo_ideforlodevelopment/ Change-Id: I9965829db319a8b26f5ad82d3ffa723a28da7910 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/110536 Tested-by: Jenkins Reviewed-by: Michael Weghorn <m.weghorn@posteo.de>
2021-02-07qtcreator: Drop some extra whitespace in .pro.user templateMichael Weghorn
Fix indentation and drop some extra empty lines that are automatically removed once the project is loaded in Qt Creator and then closed anyway. This will make it a little easier to compare what the initially generated file looks like compared to the one as it is written after (implicitly or explicitly) carrying out the configuration in Qt Creator after loading the project. Change-Id: I52173162efe635e6fb3e7f889c42ed67271c05b1 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/110535 Tested-by: Jenkins Reviewed-by: Michael Weghorn <m.weghorn@posteo.de>
2021-02-07qtcreator: Don't create useless run configurations for subdirsMichael Weghorn
Use the 'lib' instead of the 'app' template for the qmake files in the subdirectories, which avoids automatically creating a useless run configuration for each subdirectory pointing to a non-existent execuatable, like '<BUILDDIR>/accessibility/accessibility' etc. With this in place, I just get a single "Custom Executable" run configuration running 'instdir/program/soffice.bin' when opening the newly generated 'lo.pro' in Qt Creator 4.14. Change-Id: I69a7f1b56b02849b217bf66f110d9ee1f61125ea Reviewed-on: https://gerrit.libreoffice.org/c/core/+/110534 Tested-by: Jenkins Reviewed-by: Michael Weghorn <m.weghorn@posteo.de>
2020-09-17make vim-ide-integration: fix ResourceWarningMiklos Vajna
Exception ignored in: <_io.FileIO name='compile_commands.json' mode='wb' closefd=True> ResourceWarning: unclosed file <_io.TextIOWrapper name='compile_commands.json' mode='w' encoding='UTF-8'> Change-Id: I2ab4275a9b7897f5cd9e88b20a1eea4c68fe0d1f Reviewed-on: https://gerrit.libreoffice.org/c/core/+/102907 Reviewed-by: Miklos Vajna <vmiklos@collabora.com> Tested-by: Jenkins
2020-07-13Don't rely on Python's treatment of unrecognized escape sequencesMike Kaganski
According to [1]: > Changed in version 3.6: Unrecognized escape sequences produce a DeprecationWarning. > In a future Python version they will be a SyntaxWarning and eventually a SyntaxError. [1] https://docs.python.org/3/reference/lexical_analysis.html#string-and-bytes-literals Change-Id: Ia4f79f17ccb121f423f35b1e1306d5ae285e8762 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/98321 Tested-by: Jenkins Reviewed-by: Noel Grandin <noel.grandin@collabora.co.uk> Reviewed-by: Mike Kaganski <mike.kaganski@collabora.com>
2020-07-08vs-ide-integration: unescape values coming from DEFSMike Kaganski
... so `TK_DLL_NAME=\"tklo.dll\"` becomes `TK_DLL_NAME="tklo.dll"` Change-Id: I0e14ded85be387a342e1979aa3f120727178351d Reviewed-on: https://gerrit.libreoffice.org/c/core/+/98319 Tested-by: Jenkins Reviewed-by: Mike Kaganski <mike.kaganski@collabora.com>
2020-01-27VisualStudioIntegrationGenerator: put solution/projects to build dirMike Kaganski
.. instead of source dir. This allows to have ide integration files in proper directory when using out-of-the-tree build directory. Change-Id: I0d3be02b3ee27e499d9d223b0a521e4688885a1c Reviewed-on: https://gerrit.libreoffice.org/c/core/+/87502 Tested-by: Jenkins Reviewed-by: Mike Kaganski <mike.kaganski@collabora.com>
2020-01-22vs-ide-integration: Also add .c filesMike Kaganski
Change-Id: Icb4e879025278291270d908bb53178250c8e7007 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/87192 Tested-by: Jenkins Reviewed-by: Mike Kaganski <mike.kaganski@collabora.com>
2019-10-12qtcreator: Sort SUBDIRS in lo.pro alphabeticallyMichael Weghorn
... in particular to have a deterministic order and see more easily what relevant effects changes to the gbuild-to-ide script have while testing those. Change-Id: I4583a8ca5a779d1d1e8aa6db7bb0295abd6154ee Reviewed-on: https://gerrit.libreoffice.org/80653 Tested-by: Jenkins Reviewed-by: Michael Weghorn <m.weghorn@posteo.de>
2019-10-11qtcreator-ide-integration: Take unit tests into accountMichael Weghorn
This makes code-completion, clang checks, navigation etc. work in files related to those as well. Change-Id: Ie0b7d75f2ed953228d74ae070056327bff7ff2a2 Reviewed-on: https://gerrit.libreoffice.org/80652 Tested-by: Jenkins Reviewed-by: Michael Weghorn <m.weghorn@posteo.de>
2019-07-15qtcreator: Recursively include module's header filesMichael Weghorn
Recursivley walk the include directories located inside the current module's directory, since includes are basically paths relative to the include directories and can refer to files in subdirectories of the include path, like e.g. #include <extended/AccessibleBrowseBoxBase.hxx> in 'accessibility/source/extended/AccessibleBrowseBoxBase.cxx'. This way, such header files are added to the .pro files and are thus e.g. shown in Qt Creator's project view and can be found by using 'a <FILEANME>' in the Locator. Change-Id: Id74f971b2ffee82203f74a4d444c41166c671920 Reviewed-on: https://gerrit.libreoffice.org/75628 Tested-by: Jenkins Reviewed-by: Michael Weghorn <m.weghorn@posteo.de>
2019-07-05qtcreator: Make paths work with cygwinMichael Weghorn
Absolute paths in files created by GbuildToJson in Cygwin environment are Windows paths (like "C:/....'), while relative paths in the Python program executed in Cygwin are treated as Unix paths ('/cygdrive/c/....') which caused wrong relative paths to be generated by the call to 'os.relpath'. It would walk up to the root of the Windows path and then walk down the tree in the Unix file system path again. This converts the paths to absolute Windows paths first to avoid this issue. Change-Id: I2e3e6926e312d64aa18067933a5903ac7ad5d31a Reviewed-on: https://gerrit.libreoffice.org/75114 Tested-by: Jenkins Reviewed-by: Michael Weghorn <m.weghorn@posteo.de>
2019-06-17Add vs2019-ide-integrationMike Kaganski
Change-Id: I14b7ebb3521f9a23fcf4c3ff907408327f189f29 Reviewed-on: https://gerrit.libreoffice.org/74138 Tested-by: Jenkins Reviewed-by: Mike Kaganski <mike.kaganski@collabora.com>
2019-06-08qtcreator: Take over '-std=...' from CXXFLAGSMichael Weghorn
If the '-std=' compiler flag is set in CXXFLAGS, take that over into the .pro files used by Qt Creator. This makes ClangCodeModel use the correct std version, and e.g. know about 'std::string_view' if '-std=gnu++2a' (or anything else indicating C++17 or higher is supported) is used and thus avoids unnecessary errors/warnings from being displayed. Use a list, so other flags can easily be added later. (It currently doesn't seem reasonable to me to just pass all cxxflags though, since .pro files are currently only generated per top-level module, while C++ flags can differ between different targets in the same module). Change-Id: Id3f3e2b9ba77e5220a17fd4796937c816979959a Reviewed-on: https://gerrit.libreoffice.org/73677 Tested-by: Jenkins Reviewed-by: Michael Weghorn <m.weghorn@posteo.de>
2019-02-14VisualStudioIntegrationGenerator: put CXXFLAGS to AdditionalOptionsMike Kaganski
Adding AdditionalOptions to nmake project settings allows IntelliSense to know about used compiler switches; specifically, passing std switch (currently -std:c++17) defines _MSVC_LANG macro [1] to proper value to avoid false IntelliSense errors (e.g., for string_view). [1] https://docs.microsoft.com/en-us/cpp/preprocessor/predefined-macros Change-Id: I90309e6bf2a87257a0c81b1406e678af962eb587 Reviewed-on: https://gerrit.libreoffice.org/67805 Tested-by: Jenkins Reviewed-by: Mike Kaganski <mike.kaganski@collabora.com>
2019-01-25add basic support for generating CodeLite IDE filesNoel Grandin
Change-Id: I70613baada4f82e5e56f9a21547733c3a6907b53 Reviewed-on: https://gerrit.libreoffice.org/66908 Tested-by: Jenkins Reviewed-by: Noel Grandin <noel.grandin@collabora.co.uk>
2018-12-13qtcreator: Take system includes into accountMichael Weghorn
Take system includes ('-isystem') into account when generating the '*.pro' files for Qt Creator using the 'qtcreator-ide-integration' make target. Without this, Qt Creator is unable to find the corresponding included files. This also makes Qt Creator's ClangCodeModel able to properly process files and display actual problems, rather than always showing a multitude of errors due to missing includes while parsing the source/header files. Change-Id: Ie513341e1074ceab9304ae9df73fac9a79329db8 Reviewed-on: https://gerrit.libreoffice.org/65129 Tested-by: Jenkins Reviewed-by: Michael Weghorn <m.weghorn@posteo.de>
2018-12-03Fix typoAndrea Gelmini
Change-Id: I69e4d471c806159d6748016a79f041c01b40b888 Reviewed-on: https://gerrit.libreoffice.org/64430 Tested-by: Jenkins Reviewed-by: Jens Carl <j.carl43@gmx.de>
2018-08-30Upgrade to vs2017-ide-integration, since we don't support VS2015 in masterMike Kaganski
This allows to avoid the "(Visual Studio 2015)" labels next to project names in Solution Explorer; and also avoid multiple warnilgs like project-name.vcxproj : warning : The build tools for Visual Studio 2015 (v140) cannot be found. Install Visual Studio 2015 (v140) to build using the Visual Studio 2015 (v140) build tools. in IDE's Output pane in case VS2015 is absent locally. Change-Id: I53b68ac810cbf2a31667c35dd549310e7209e010 Reviewed-on: https://gerrit.libreoffice.org/59797 Reviewed-by: Mike Kaganski <mike.kaganski@collabora.com> Tested-by: Mike Kaganski <mike.kaganski@collabora.com>
2018-08-29vim-ide-integration: remove no longer needed workaroundMiklos Vajna
Fixes the problem that e.g. this code: OUString str; str += ""; is marked as a compile error, when clang would still work with c++11, but the tree is configured for gnu++17. Change-Id: Id60c0cf4b8c693b534f16ba813cf01a4bad7e560 Reviewed-on: https://gerrit.libreoffice.org/59746 Reviewed-by: Miklos Vajna <vmiklos@collabora.co.uk> Tested-by: Jenkins
2018-07-09fix compile_commands.json when generated with modern gccMarkus Mohrhard
Change-Id: I4a17cfb567f5ebec8bb416b9aa4d58763ff36c36
generated by cgit (git 2.34.1) at 2025-01-10 16:39:09 +0000