Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
3.12+ 2018)
|
|
|
|
|
|
|
|
|
|
Install wayland session entry
|
|
In particular, this propogates dependency lib include dirs provided from a target
to be used as a system include path. This also propagates definitions provided by a target
in the same manner
[cmake] FindFlatbuffers change to INTERFACE IMPORTED target
[cmake] FindRapidJSON implement INTERFACE IMPORTED target
[cmake] FindFFMPEG move to targets for ffmpeg libs
[cmake] FindTagLib move to full TARGET usage
[cmake] Findlibandroidjni add IMPORTED TARGET
[cmake] FindNFS Change to using IMPORTED TARGET fully
[cmake] FindLibDVD* move to full TARGET use
[cmake] FindUUID change to target usage
[cmake] FindCrossGUID change to target usage
[cmake] FindFmt move to full TARGET usage
[cmake] FindSqlite3 move to full TARGET usage
[cmake] FindSpdlog move fully to modern TARGET usage
[cmake] FindTinyXML2 fixups
[cmake] FindPCRE convert to full TARGET usage
[cmake] fstrcmp TARGET usage
|
|
|
|
|
|
|
|
|
|
|
|
|
|
INSTALL_PREFIX is handled as part of the BUILD_DEPS macro
|
|
When building internal, we never build shared, so drop FFMPEG_CREATE_SHARED_LIBRARY
and the static definition isnt used anywhere
|
|
The ffmpeg::ffmpeg target doesnt have a single on disk artifact, so change to INTERFACE
in preparation for additional lib targets
|
|
|
|
For osx we converted from an old style .bin executable to the modern app style.
This change fixes script to actually function correctly. *Kodi* was too generic, therefore
tne preceding folder is added.
|
|
executable folder
This allows VS (a Multiconfig Generator) to build and create a full file structure
required to execute the main app target immediately from the build location that is
created in a folder path that is not known at cmake generation.
An example, is if you build Kodi as Debug, the executable will be placed in
{CMAKE_BINARY_DIR}/Debug/kodi.exe but if you change the Build Type to Release, it will
go in ${CMAKE_BINARY_DIR}/Release/kodi.exe. As you can change to any build type you wish after
cmake generation, we can not know the location at cmake generation time, so currently
all the required dlls/files/folders for a complete bundle are just placed in
${CMAKE_BINARY_DIR}/ and therefore you need to copy the kodi.exe from the folder it was built
into the parent folder to be able to execute it.
|
|
|
|
Instead of adding to export-files, add to libkodi as a dependency.
This will facilitate the optional use of export-files target
|
|
|
|
|
|
|
|
|
|
Debian bookworm ships a config file for tinyxml2, great. config type however is NONE
Add case to parse all config types, if its not DEBUG or RELEASE, just populate the
release lib variable
|
|
[webOS] Video decoder improvements
|
|
Migrate to TinyXML2 usage from TinyXML1
Implement tests for MediaSourceSettings
Mediasourcesettings update to coding guidelines
|
|
cmake: add FindTinyXML2 find module
cmake: enable building tinyxml2 for all platforms (ENABLE_INTERNAL_TINYXML2)
tests: Tests for XBMCTinyXML2 implementation
tests: Tests for XMLUtils for the tinyxml2 methods
utils: implement TinyXML2 methods for XMLUtils
Currently tinyxml2 and 1 can coexist peacefully. This will allow a staged replacement
and to hopefully update and implement tests appropriately.
|
|
|
|
|
|
This ensures compatibility with the new toolchain which includes Pulseaudio but in order to support Pulseaudio also some auxiliary libraries from the toolchain have to be bundled. To keep compatibility with the old and new toolchain update simply forcefully disable Pulseaudio so the default is still ALSA.
|
|
|
|
[playlist] add b4s playlist recognition to music and tests
|
|
|
|
|
|
Add b4s filetype recognition to music player. Add tests to test LoadData of b4s file
|
|
[cmake] TexturePacker: don't force static libraries
|
|
This is needed to allow building on a linux host that only has shared libraries (not a depends build)
Signed-off-by: Lukas Rusak <lorusak@gmail.com>
|
|
Update FindJsonSchemaBuilder.cmake to build in tree for all platforms.
JsonSchemaBuilder doesnt have versioning, but its a single file build, so just build always
unless WITH_JSONSCHEMABUILDER is provided
|