Leverage usage of runtimes with cmake
Tie a build directory to a runtime, so too weird things don't happen
Include runtimes in kdevelop UI
Details
Details
- Reviewers
- None
- Group Reviewers
KDevelop - Commits
- R32:abdc8783a7fc: Adapt changes on kdevpatform
Diff Detail
Diff Detail
- Repository
- R32 KDevelop
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
Comment Actions
- Always set the builddir runtime
- Have includes translated for the IDE
- Android runtime
- Fix test
- Fix cmake tests
- Store the build directory on a per-runtime basis
Comment Actions
- Always set the builddir runtime
- Have includes translated for the IDE
- Android runtime
- Fix test
- Fix cmake tests
- Store the build directory on a per-runtime basis
- Convert source directory and build directory into the runtime's
- Also reparse projects when reloading
- Use user-specific tmp directories
Comment Actions
- Always set the builddir runtime
- Have includes translated for the IDE
- Android runtime
- Fix test
- Fix cmake tests
- Store the build directory on a per-runtime basis
- Convert source directory and build directory into the runtime's
- Also reparse projects when reloading
- Use user-specific tmp directories
- Don't translate local includes
- Adapt to changes in kdevplatform runtime approach
- Adapt to changes in kdevplatform
Comment Actions
- Always set the builddir runtime
- Have includes translated for the IDE
- Android runtime
- Fix test
- Fix cmake tests
- Store the build directory on a per-runtime basis
- Convert source directory and build directory into the runtime's
- Also reparse projects when reloading
- Use user-specific tmp directories
- Don't translate local includes
- Adapt to changes in kdevplatform runtime approach
- Adapt to changes in kdevplatform
- Reparse project after reloading its root
- Revert changes in definesandincludes
- Process compiler includes so that it can be used by the host
- Don't expect the host to convert the paths