CMake issueshttps://gitlab.kitware.com/cmake/cmake/-/issues2017-09-09T09:11:33-04:00https://gitlab.kitware.com/cmake/cmake/-/issues/17224CodeLite project file generator doesn't generate entries for source files in ...2017-09-09T09:11:33-04:00Andreas DueringCodeLite project file generator doesn't generate entries for source files in object librariesIssue tested with cmake 3.7 and cmake 3.9 under Debian, i686 architecture.
I'm not sure whether this is a bug, or intended.
If I generate CodeLite project files using cmake (both Unix Makefiles and Ninja are affected), source files in ...Issue tested with cmake 3.7 and cmake 3.9 under Debian, i686 architecture.
I'm not sure whether this is a bug, or intended.
If I generate CodeLite project files using cmake (both Unix Makefiles and Ninja are affected), source files in object libraries are not added to the project. Instead, the object files are added.
Example CMakeLists.txt:
```
cmake_minimum_required(VERSION 3.1.0)
project(ObjLibGen)
add_library(ObjLib OBJECT lib.c)
add_executable(exe main.c $<TARGET_OBJECTS:ObjLib>)
```
With a minimum lib.c:
```
void foo()
{
}
```
and main.c
```
int main()
{
return 0;
}
```
This leads to the appended project file being generated: [ObjLibGen.project](/uploads/7199caaba07c6e18b898c5575e99a2d3/ObjLibGen.project)
The workspace files just references the project file.https://gitlab.kitware.com/cmake/cmake/-/issues/16671Codelite projects can't be debugged/launched from Codelite2017-10-13T13:17:55-04:00Timo WiesemannCodelite projects can't be debugged/launched from CodeliteWhen generating a "Codelite - Unix Makefiles" project, I can build everything.
But I cannot launch/debug a project from within Codelite.
It can't find the executable.
In each sub-project's settings the Output File is set to **./$(Proje...When generating a "Codelite - Unix Makefiles" project, I can build everything.
But I cannot launch/debug a project from within Codelite.
It can't find the executable.
In each sub-project's settings the Output File is set to **./$(ProjectName)**, which seems to be **${CMAKE_BINARY_DIR}/${PROJECT_NAME}** (see image).
In my project the binaries are *not* build in the root of **${CMAKE_BINARY_DIR}**.
Stepping through the cmake source I found that in *cmExtraCodeLiteGenerator.cxx* only **EXECUTABLE_OUTPUT_PATH** is queried for the binary output path,
which was always empty for the projects I tried - so it defaulted.
In my project I set them via **CMAKE_RUNTIME_OUTPUT_DIRECTORY**. If I change the code to query that variable first, the output filepath is set correctly.
That would help in my situation, where my binaries are named exactly like the project names.
It won't suffice for i.e the cmake source, where the project is named "CMake" but the executable is named "cmake".
OS: Lubuntu 16.04 LTS CMake version: 3.7.2, clang 3.8.0
![cmake-3.7.2_codelite_generator](/uploads/f3ecb55115e6308c256a94356b590bae/cmake-3.7.2_codelite_generator.png)https://gitlab.kitware.com/cmake/cmake/-/issues/16627CodeLite projects don't work2017-10-13T13:17:55-04:00LybertaCodeLite projects don't workI'm generating CodeLite projects from the following CMakeLists.txt:
[CMakeLists.txt](/uploads/17912be4008e173282a47b4c6a69ca08/CMakeLists.txt)
When generated, I can't build them in CodeLite. It sort of enters the infinite loop and ...I'm generating CodeLite projects from the following CMakeLists.txt:
[CMakeLists.txt](/uploads/17912be4008e173282a47b4c6a69ca08/CMakeLists.txt)
When generated, I can't build them in CodeLite. It sort of enters the infinite loop and if you choose Build and rebuild several times I eventually get:
Command line is empty. Build aborted.
In Build tab.
The repository is FOSS and you can get the source code here: https://gitlab.com/ftz/general
I've reported this to CodeLite developer, but he said that he doesn't support projects that were generated by other programs. I've attached project files which were generated.
[BuildFailed.zip](/uploads/1b97d5815dcc15e853d037588824bb6a/BuildFailed.zip)
OS: Debian Testing
CMake version: 3.7.2